0

I have a SharePoint 2013 farm and on my applications server the content processing component is degraded and my search crawl will not complete.

Any ideas how I can fix this?

enter image description here

enter image description here

0

I would start by making sure the file system that contains your index is sound. You also have an end point failure which may be that the CPC is not provisioned correctly. Start with a reboot and evaluate the components. Turn logging up to verbose for Search and you will get a TON of information on that is going on dumped to the ULS logs.

I suspect it's a drive failure though.

  • Thanks! In the end the problem was that the drive that the index component was pointing to was offline. Now I'm getting a different error: – Rob P Feb 10 '17 at 16:15
  • The content processing pipeline failed to process the item. ( The type initializer for 'Microsoft.Office.Server.Search.LocStringIdLookupTable' threw an exception 02/09/2017 14:48:00.88 NodeRunnerContent1-0d991a01-1ad (0x629C) 0x782C Search Search Platform Services aiy4z Unexpected AssemblyReflector : Failed to load dependency assembly in load context and in load from context. Assembly: BihConsumerInterop System.IO.FileNotFoundException: Unable to find the specified file. – Rob P Feb 10 '17 at 16:15
  • Glad you soved it, can I get an answer for my reply? – Matthew McDermott Feb 11 '17 at 12:51

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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