Hello,

I faced a problem on my farm near 2 weeks ago - full crawl never stops. It is crawling items (according to the crawl log) and search is working on the most of sites.

Before this issue search worked on the farm without any problems during 6 months.

I tried to:

 - reset index

 - restart all server

 - delete and create search application from scratch 

All these steps did not help.

My architecture:

I have 4 WFEs (Query component on each), and 2 dedicated servers for search (each server has all components, except Query), all DBs are on SQL 2012 in high availability groups.

SharePoint version - 15.0.4649.1000

When full crawl hangs, I see these errors in the ULS log:

Transaction failed in plugin RHTG Url sts4://testsite.company.com.mccain.com/siteurl=/siteid={d0772206-ae3a-4954-842e-a5d91581e1a7}/weburl=Products/webid={247379fb-c911-4718-9c72-40ca284fd99f}/listid={9518987c-6aee-4b70-826d-8ba44e024a2a}/folderurl=/itemid=3 Error 0x80040d79  [gthrtrx.cxx:950]  search\native\gather\gthrsvc\gthrtrx.cxx


Transaction failed in plugin RHTG Url sts4://testsite.company.com.mccain.com/siteurl=/siteid={d0772206-ae3a-4954-842e-a5d91581e1a7}/weburl=Products/webid={247379fb-c911-4718-9c72-40ca284fd99f}/listid={9518987c-6aee-4b70-826d-8ba44e024a2a}/folderurl=/itemid=3 Error 0x80040d79. This will generate a retry  [gthrtrx.cxx:958]  search\native\gather\gthrsvc\gthrtrx.cxx

processing status change (1) NSC_FLUSH, (deaa571a-3bae-43e6-a6de-857d5e2375b5-crawl-0, Portal_Content) thread id 0x3f44  [statthrd.cxx:97]  search\native\gather\server\statthrd.cxx

CGthrPrj::AdviseStatusChange : advising status change NSC_FLUSH (Portal_Content deaa571a-3bae-43e6-a6de-857d5e2375b5-crawl-0 )  [cgatherprj.cxx:1648]  search\native\gather\gthrsvc\cgatherprj.cxx

CPluginCollection::AdviseStatusChange : advising status change NSC_FLUSH (Portal_Content deaa571a-3bae-43e6-a6de-857d5e2375b5-crawl-0 )  [plugin.cxx:712]  search\native\gather\gthrsvc\plugin.cxx

CPluginCollection::AdviseStatusChange : advising status change NSC_FLUSH (Portal_Content deaa571a-3bae-43e6-a6de-857d5e2375b5-crawl-0 )  [plugin.cxx:712]  search\native\gather\gthrsvc\plugin.cxx

Received signal: NSC_FLUSH                                                      [contentpiobj.cxx:297]  search\native\gather\plugins\contentpi\contentpiobj.cxx

CRobotThread::Thread failed to move file for docID 6153, URL sts4://testsite.company.com.mccain.com/siteurl=/siteid={d0772206-ae3a-4954-842e-a5d91581e1a7}/weburl=Products/webid={247379fb-c911-4718-9c72-40ca284fd99f}/listid={9518987c-6aee-4b70-826d-8ba44e024a2a}/folderurl=/itemid=3, Error 0x80070005. The transaction will be retried.  [robotthrd.cxx:4822]  search\native\gather\gthrsvc\robotthrd.cxx

advising status change NSC_FLUSH (deaa571a-3bae-43e6-a6de-857d5e2375b5-crawl-0 Portal_Content crawl -1)  [gatherobj.cxx:4877]  search\native\gather\server\gatherobj.cxx

Hi,

It seems that the crawler is struck and not crawling any thing.I would recommend you to stop the crawler and run again.

Restart SharePoint Server search 15

Restart SharePoint Timer Service

Restart IIS

For more detailed information, refer to the following article:

https://johnmhester.wordpress.com/2014/02/27/unable-to-stop-crawl-andor-index-reset-sharepoint-2013-search/

If the issue exists, I would suggest you that refer to the following article to recreate the search service application: 

http://blog.bugrapostaci.com/2015/02/18/clean-up-search-service-application-in-sharepoint-2013/

Best Regards,

Lisa Chen 

Hi Lisa,

As I wrote in my 1st post I tried to restart all servers in the farm, tried to recreate search (deleted service application, all DBs) - this did not help.

Also I found that sometimes site can be crawled successfully (full crawl), another time search hangs on the same site. Errors in the ULS logs are the same as in my first post.

Thanks.

• Edited by Oleh Tserkovnyuk 18 hours 8 minutes ago

Hi Lisa,

As I wrote in my 1st post I tried to restart all servers in the farm, tried to recreate search (deleted service application, all DBs) - this did not help.

Also I found that sometimes site can be crawled successfully (full crawl), another time search hangs on the same site. Errors in the ULS logs are the same as in my first post.

Thanks.

• Edited by Oleh Tserkovnyuk Friday, July 10, 2015 1:29 PM

what is the status of your search components? If you refresh them are you having the same status

$SSA = Get-SPEnterpriseSearchServiceApplication
$SSA.RefreshComponents()

Normally if the crawl never stops it is an issue with the crawl or admin component

Check also content processing activity

 Central Admin > Manage Service Applications > SSA > Crawl Health Reports > Content Processing Activity

In order to collect additional info put the following logs in verbose mode when the issue is present 

i. Crawler:Common 
ii. Crawler:Content 
iii. Crawler:FilterDaemon
iv. Crawler:Gatherer Plugin 
v. Crawler:Gatherer Service