Search query critical error - Event 60 (SharePoint Server 2010)
Published: May 12, 2010
Alert Name: Search query critical error
Event ID: 60
Summary: In scenarios where a query component has no mirror and lacks high-availability, or all query components in a query group fail, it is possible that query results will not be served for a portion of the index.
Symptoms: Microsoft SharePoint Server 2010 experiences the following symptoms when serving queries:
-
Query latency increases or queries fail.
-
This event appears in the event log: Event ID: 60 Description: Cannot take the last query component out of rotation. Check previous event logs to determine cause. Propagation may be necessary. <data>
Note: The event details identifies the query component as <GUID>-<Query Component number>, for example “baebc6d3-4a2e-4584-9ff7-ad8866debe92-query-30”. To identify the query component, use the second part, “query-30”.
Cause: A query component has been taken out of rotation due to the reason present in the previous search event's error message.
Resolution: Restart the search service
-
Stop and restart the Microsoft Search Server 2010 service (OSearch).
-
Open a Command Prompt window and type net stop osearch14 to stop the search service. Type net start osearch14 to restart the search service.
If failure persists, add a new query component as a mirror in the same query group as the failed query component.
Resolution: Add a new query component
-
On the SharePoint Central Administration Web site, click General Application Settings and in the Search section click Farm-wide Search Dashboard.
-
In the Search Service Applications section, from the drop-down list select the search application that generated the event, and then click Modify Topology.
-
On the Topology for Search Service Application page, click the failed query component in the topology list, and then select Add Mirror from the component’s drop-list.
-
In the Add mirror query component dialog box, select the query server and associated metadata database for the new query component, and then click OK.
-
Click Apply Topology Changes. The changes are processed for the search application and the index is copied from the failed query component to the new query component.
-
Click the failed query component and click Delete.
-
The topology removes the index from the failed query component and deletes the component.
Change History
| Date | Description |
|---|---|
| May 12, 2010 | Initial publication |
