SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a number of lists scattered throughout my site collection that have recently stopped indexing for Search, and there are errors in the crawl log for these lists of "Error in the Site Data Web Service. (The given key was not present in the dictionary.)" After the error the lists are no longer present in the index. The lists in question are in different subsites, don't have unique permissions and don't seem to have anything of note in common. The site collection does indeed have a top-level site and none of the posts on this error in any forum that I've found seem to apply here.

Running MOSS SP2 and we've had no configuration changes that I'm aware of. Ideas?

share|improve this question

closed as too localized by SPDoctor Nov 7 '12 at 14:02

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Have you tried to recreate your Search Service Application? Or do an Index reset? – Mike Jul 24 '12 at 15:48
Yes to the index reset, not yet on recreating the service. Interestingly, if I copy one of the offending lists (custom list with only 4 columns, nothing special) to another site the copy doesn't index either. – SharePointEric Jul 26 '12 at 12:34
I would try to recreate your search service application. Something funny is going on. – Mike Jul 26 '12 at 13:39
up vote 0 down vote accepted

Just closing this old question. The issue turned out to be that we had a third party solution (KwizCom Rating and Tagging) implemented and when our admins ported the index jobs to a new server they failed to install the KwizCom assemblies on the new server. This was the root cause of the index failures and when we installed the assemblies to the index server all was well.

share|improve this answer
Thanks for updating - do you mind if we close this as "too localized"? – SPDoctor Nov 5 '12 at 17:41
Please feel free to close, thanks! – SharePointEric Nov 6 '12 at 18:34

Not the answer you're looking for? Browse other questions tagged or ask your own question.