Tuesday, 23 August 2011

Crawl Component stuck at 'Recovering' status

Various blogs suggest to delete entirely the search service and start afresh. This a fairly drastic approach and not always practical with a production environment. Our fix was to create a new crawl component on the same server within Central Administration, this took 10 minutes to process but when it came back both the new and existing crawl components where online.


Crawl component stuck on ‘Recovering’








Two crawl components on same server.









Delete the new crawl component.


3 comments:

  1. Worked for me - added additional crawl component and deleted it afterwards :-)

    ReplyDelete
  2. Worked great for me also. Fixing the crawl component also fixed my crawl that was stuck in a "stopping" state indefinably.

    ReplyDelete