I’m seeing a recurring error on my Appserver that
The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID 9f90e7e1-9935-45db-b701-eebc7a8cf960) threw an exception.
The search application ‘1523cd82-7a0a-41b4-8826-49a0c2acac42’ on server SP2013APPPROD1 did not finish loading. View the event logs on the affected server for more information.
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (12fbf02d-3460-45c8-9da0-407ef84b5b51).
Reason: The device is not ready.
Technical Support Details:
System.IO.FileNotFoundException: The device is not ready.
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
This on a SharePoint 2013 on Premise production farm. How do I resolve this issue?
Just a follow up to this. I was finally able to resolve the issues. Ran updates from Windows/SharePoint. rebooted servers. Checked patch status. Two of my machines were showing they need Language Pack updates. So I ran those. Rebooted servers. Check patch status again. 3rd machine showing it needed Language Pack updates. So I ran those. rebooted. Install said it was successful, but patch status said it wasn’t. Repeated this process 3 times. This morning there more available important updates on all 3 servers… ran them all servers. Rebooted servers again. Once all finally came back up after the last reboot, all servers were showing appropriately patched. Then I was able to run the Config Wizard. All content databases, search and other services databases are compatible and my farm is running nicely.
No real answers, just documentation of what all I did, in case I ever have to do it again.
Went further back in the events log and found this:
The synchronization operation of the search component: 1523cd82-7a0a-41b4-8826-49a0c2acac42 associated to the search application: Search Service Application on server: *servername* has failed. The component version is not compatible with the search database: Search_Service_Application_CrawlStoreDB_a2ae40f397ba4923ae9198efd8818e3c on server: *servername*. The possible cause for this failure is The database schema version is less than the minimum backwards compatibility schema version that is supported for this component. To resolve this problem upgrade this database..
I know how to upgrade the content databases via powershell… but how do I upgrade the Search Service Application databases??
