When having two WFE servers configured so that one acts as Search Indexing server and the other acts as Search Query server, you get multiple errors in event log and the search does not work.
On the Indexing server, errors are:
10038: Query machine 'IndexingServer' has been taken out of rotation due to this error: The system cannot find the file specified. 0x80070002. It will be retried in N seconds. Component:
10039: Retry of query machine 'IndexingServer' has failed with error: The system cannot find the file specified. 0x80070002. It will be retried again in N seconds. Component:
10040: The last query machine has been taken out of rotation. Check previous event logs to determine cause. Propagation may be necessary. Component:
On Query Server the errors are:
6482: Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (
Reason: Object
Techinal Support Details:
System.Collections.Generic.KeyNotFoundException: Object
at Microsoft.Office.Server.Search.Administration.SearchApi.get_App()
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
10039: Retry of query machine 'QueryServer' has failed with error: The system cannot find the file specified. 0x80070002. It will be retried again in N seconds. Component:
Solution:
Make sure the permissions are set correctly. More exactly see that the Farm Search Service Account is in Administrators group and in WSS_ADMIN_WPG group on the Indexing and Query servers. After that stop and start the Office SharePoint Server Search service in Central Admin.
What is the "Indexing and Query servers' Administrators" group?
ReplyDeleteThanks for the comment. I rephrased the sentence, hopefully it is more clear now.
ReplyDeleteThank you for this article,
ReplyDeleteI've been struggling with that for a couple of days.
One question though, if you Stop then start the Office SharePoint Server Search in Central Admin, it will remove the service on that server, then the Search DB will be removed, am I correct? what if I restart the service from the Services.msc?
If you stop the "Office SharePoint Server Search" in Central Admin, it will permanently delete all content index files (as it says on the screen when you're about to stop the service). This means that the files in "Index Server Default File Location" on that server are removed.
ReplyDeleteHowever, the Search DB remains intact, so when you start the Search again, you will have the same number of items in the index (I just tested this). Also the index files were recreated.
Stopping and starting the service in Services.msc doesn't remove anything (files nor DB).
You can try if Services.msc service restart is enough, but I'd guess that part of the problem might be related to incorrect permissions in the index files. Only when they're recreated the correct permissions are set, so Central Admin service stop/start is required.
Thanks Jussi for confirming this. Since it's a production environment, I'm very careful with that.
ReplyDeleteBTW I've 2x-check the permissions and these were correctly set.
For me it happened after a lock on the search DB, that wouldn't let me open the DB properties (only on that one).
Many Thanks
Raphael
Thanks, i checked permissions and it works.
ReplyDelete