Share via

Search propagation communication error - Event 92 (SharePoint Server 2010)

  • Article

 

Applies to: SharePoint Server 2010

Alert Name:   Search propagation communication error

Event ID:   92

Summary:   As the crawler searches content to create an index, it creates index files to use for retrieving search results. These files are created by the crawl component in its storage area, and then propagated to the appropriate query components.

Symptoms:   When Microsoft SharePoint Server 2010 is crawling content, and the crawl component cannot propagate to the query server, SharePoint Server 2010 displays the following symptoms:

  • The crawl does not progress and appears to stall.

  • The crawl logs show no new crawled documents.

  • Users might not be able to view applications in their browsers, or the service may otherwise be unavailable

  • This event appears in the event log: Event ID: 92 Description: A Crawl Component for search application ‘<data>’ could not communicate with the query server ‘<data>’.

Cause:   One or more of the following might be the cause:

  • The crawl component might have stale, or expired, credentials.

  • Network issues might prevent the communication.

  • The query server might be unresponsive.

Resolution:   Authorization failure

  • Make sure that search service credentials are up to date by rebooting the servers that had the problem.

Resolution:   Correct Network connection issue

  • Verify the network connection between the server that hosts the crawl component and the query server. If the network connection is working, examine the query component on the query server and make sure that the share exists and is writable from the crawler.

Resolution:   Create a new query component

  • If a file cannot be copied from the crawl component to the query server after rebooting servers, create a new query component in the same query group:

    1. On the SharePoint Central Administration Web site, click General Application Settings and in the Search section click Farm-wide Search Dashboard.

    2. On the Farm-wide Search Dashboard page, modify the search application that generated the event: Add a new query component in the same query group as the affected query component, and then remove the affected query component.

    3. In the topology, the index migrates from the affected query component to the new query component.