As my LinkedIn profile will kindly tell you, I’m working on a SharePoint deployment for Vocera to replace our current aged and disorganised ECM (Enterprise Content Management) system. I was very confused one day to discover during my proof of concept and design stages that the indexing and crawling in SharePoint stopped working. I originally […]
As my LinkedIn profile will kindly tell you, I’m working on a SharePoint deployment for Vocera to replace our current aged and disorganised ECM (Enterprise Content Management) system.
I was very confused one day to discover during my proof of concept and design stages that the indexing and crawling in SharePoint stopped working. I originally blamed this on myself for moving from an internal model to a external model by making some changed to the Shared Services Provider (SSP), however I discovered today this is untrue.
This most helpful Microsoft TechNet Social forum page explains how the cause is a .NET Framework 3.5 Family update that makes changes to the authentication model and providers in SharePoint.
Follow the instructions in the post from Sandeep Lad to resolve your issues.