Hi Roland!
For some reason, I get the same error today, but I can view other postings. Thanks to Antonio for his posting...maybe this will help you. I am working on my initial install which is version 4.3, but maybe the dll's are an issue there as well, I will have to check.
To sum up what that other forum stated...there seems to be 2 fixes...one temporary and the other perm. Now I didn't make these up, so please don't hold me to them...
Also, I have only used the temp fix so far and it seems to be ok for me, I have not tried out the perm fix yet.
Temp fix:
In your module, check to see if your End Date is set to 12/31/1999 by default. If so, remove this date. Click on Search Admin under the Host menu, re-index content and update. This should now find your descriptions you've set in your module entries (I beleive search does not work on titles...so you need to add descriptions). Problem with this method is if you edit the module, the date may get auto populated again, so you would have to keep checking the modules.
Perm Fix:
Edit Stored Procedure dbo.GetSearchModules
current logic (which is wrong)
and (T.EndDate < GETDATE() or T.EndDate IS NULL)
and (T.StartDate > GETDATE() or T.StartDate IS NULL)
and (M.StartDate > GETDATE() or M.StartDate IS NULL)
and (M.EndDate < GETDATE() or M.EndDate IS NULL)
correct logic to replace above:
and (T.EndDate > GETDATE() or T.EndDate IS NULL)
and (T.StartDate <= GETDATE() or T.StartDate IS NULL)
and (M.StartDate <= GETDATE() or M.StartDate IS NULL)
and (M.EndDate > GETDATE() or M.EndDate IS NULL)
In the notes, it said this fix was only tested on 4.0.2 and 4.0.3 not on 4.3. but it seems to work for me (temporary anyway).
There was also a fix noted and credited to a posting from Arctain on fixing search case to allow insensitive and also allow partial searches...
Another stored procedure change. Dbo.GetSearchResults
look for phrase AND (sw.Word = @Word) and comment it out.
Replace that line with this: AND (sw.Word like '%' + @Word + '%').
You will have to clear your portals cache to load the modified sp. (note, looks like this was only tested on version 3, but someone posted and used the fix in version 4.0.2 and worked fine.
Hope that helps...not sure why we can't get into that posting anymore. I haven't had luck finding any similar fixes except for Antonio's response above.
Good Luck,
Jen