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

We are currently trying to troubleshoot a problem in Sharepoint 2007 where a custom column loses the "indexed column" setting. We are trying to track this down, but has been mostly a reactive approach.

We have not found any timer jobs that run when we believe this to be removed. We have not seen any scheduled tasks that run at or near the same time as we believe the index to be removed.

Any other ideas of where to look would be appreciated.


Our team has been digging deeper. It would seem that the original content type definition is being re-applied and causing the index to be turned off. Can someone provide any ideas for triggers that would cause the content type definition to be re-applied to a list (Site Collection Documents) that may not be a Timer Job?

share|improve this question
What column are you losing the index on? – James Love Oct 17 '11 at 20:09
Sorry this has taken so long to reply...I never saw a notification that there was a response. The field is a custom document ID field [GUID]. I have noticed with some monitoring scripts that this happens during a code deployment. – Jonathan Dec 20 '11 at 20:22

Your Answer


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

Browse other questions tagged or ask your own question.