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

On a single-server farm we had the SharePoint 2007 Service Pack 3 installed without our knowledge, which seems to have affected the search and managed metadata properties negatively.

We have a number of custom metadata properties that are mapped to document and list-specific columns. We have run the SharePoint Configuration Guide post-install and run a full crawl, but still the search returns NULL (blank) for the needed metadata properties.

If we go to check them in the list, the mapping is still there and it even says "More than 1000 item" in the index, so it seems to be indexing them, but the results show otherwise.

Does anyone know what could be causing this and how to fix it?

share|improve this question

Why dont you reset the index and perform a full crawl.

share|improve this answer

We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.

We tried that, no go. It starts at "0 items" and goes up to "More than 1000 items" as before, but if I try to search for it, none of our custom metadata properties return anything. – Christian P. Jul 1 '12 at 10:58

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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