Search gatherer host unavailable - Event 114 (SharePoint Server 2010)
Applies to: SharePoint Server 2010
Alert Name: Search gatherer host unavailable
Event ID: 114
Summary: As part of a search crawl, the servers that contain the crawl components communicate with content servers to retrieve the items for the crawl. Network communication problems between crawl server and content server will inhibit this crawl.
Symptoms: When Microsoft SharePoint Server 2010 is crawling content from a specific content server and network communication problems exist, Microsoft SharePoint Server might display the following symptoms:
The crawl of the specific content server does not progress and appears to stall.
The crawl logs show no new crawled documents for the specific content server.
This event appears in the event log: Event ID: 114 Description: The server <data> is unavailable and could not be accessed. The server is probably disconnected from the network. Items from this server will be skipped by the crawl for the next 10 minutes <data>.
Cause: Network issues might be preventing the communication. Check that the content server is online and can connect to the crawl server.
Resolution: Check the status of the content server
On the SharePoint Central Administration Home page, click Application Management.
In the Service Applications section, click Mangage service applications.
On the Manage Service Applications page, click Search Service Application.
On the Search Administration page, in the System Status section, record the user account listed as the Default content access account.
On the left menu, in the Crawling section, click Content Sources.
On the Manage Content Sources page, click one of the content sources.
On the Edit Content Source page, in the Start Address section, record the URL from the textbox.
Open a Web browser as the user account you recorded in step 4 above and navigate to the URL you recorded in step 7 above. The page should load successfully.
If the content server is online and serves content to the crawl account, there is likely a network connection issue. For information to determine and repair the problem, see How to Troubleshoot Basic TCP/IP Problems (http://go.microsoft.com/fwlink/p/?LinkId=157440).