1

I have single server farm SP2013 migrated from 2010 and the crawler is set up to perform a incremental crawl every 15minutes and a full crawl every friday evending.

Some times it hangs up for days and it never finishes:

enter image description here

What could the probelm be? I know that in order to improve the crawl performance the search service should have a dedicated/own server and set up a continuous crawl, but this is not possible for the moment. Obviously, by stopping and restart the SearchService it runs again ...for some weeks.

And what does Successes, Warnings and Errors exactly mean?

Edit: I had to stop the crawl again, since it did not finish but the successes, warnings and errors do not increment. After a while it restarted a full crawl by itself and I fear the scenario will repeat. For the weekend I'll try to reset the index and start the it again...hoping it works.

Update: I resetted the index and started a full crawl during weekend, it did not finish.

enter image description here

  • There are various reasons your crawled sources might return warnings and/or errors. These include unassociated content databases, partially deleted IIS sites and too often ran crawling amongst others. Have a look at your Crawl Log page at the SSA and use the links to Warnings and Errors to see what lines have been returned as such. – moe Oct 4 '16 at 7:23
-1

This is probably due to provisioning issues. Delete the Search Service Application from the Central Administration and re provision it.

Central Administration -> Manage Service Applications

  • 2
    I'd definitely recommend NOT to straight away delete the SSA without first having a look at the related outputs such as logs. – moe Oct 4 '16 at 7:19
  • True, but I answered about deleting it because I had faced a similar issue earlier, and this worked for me. – Rohith Nair Oct 4 '16 at 7:23
  • Well, when I restart the searchservice it runs fine again, but only for some weeks...I don't think that deleting and re provision the Search Service Application is the right way. – Emaborsa Oct 4 '16 at 7:32
  • Try restarting the timer job and the IIS websites then. – Rohith Nair Oct 4 '16 at 7:34
  • @Emaborsa that suggests the crawling starts to overlap. There's probably some content which delays the crawling (remember that crawling is done at a cost of performance and vice versa). My shot at first would be to extend the interval between your incremental crawls. – moe Oct 4 '16 at 7:36

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.