Archive

Archive for January, 2016

Search Service Application Exceptions – SharePoint 2013

January 27, 2016 Leave a comment

One of our clients requested a support for fixing issues in Sharepoint 2013 search service Application, while I was reviewing servers Event viewer and Log files I found the following events

In Event Viewer , I found the following events :

 

  • The Execute method of job definition Microsoft.Office.Server.Search.Administration.QueryClassificationDictionaryUpdateTimerJobDefinition (ID e3da691e-7b38-424f-8a36-1f0ef37e92d6) threw an exception. More information is included below.

The search application ‘5575749e-6c95-4763-a9bb-eadde5569928’ on server SPS-D01 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 (f1f27b7f-aa64-44c4-bdf2-2a01bfb8b23a).

 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)

 

in SharePoint log files , I found the following exceptions,

  • failed to get default collection for application **** Search Service System.Runtime.InteropServices.COMException (0x80070015): The search application ‘ on server SPS-D01 did not finish loading. View the event logs on the affected server for more information.     at Microsoft.Office.Server.Search.Administration.SearchApi.RunOnServer[T](CodeToRun`1 remoteCode, CodeToRun`1 localCode, Boolean useCurrentSecurityContext, Int32 versionIn)     at Microsoft.Office.Server.Search.Administration.SearchApi..ctor(SearchServiceApplication application)     at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.get_SearchApi()     at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize() StackTrace:  at Microsoft.Offi..

 

  • Critical: The synchronization operation of the search component: 5575749e-6c95-4763-a9bb-eadde5569928 associated to the search application: Search Service on server: SPS-D01 has failed. The component version is not compatible with the search database: SP_INT_Search_SVC_CrawlStore on server: sqld01. 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.. 6942599d-2f5b-80db-9ac6-b4cdbce18e31

 

 

The cause

If you review above exception, you will understand that one of the search components version is not compatible with the search database, this is could happen when you apply windows update on servers , when I asked him , if you applied any windows update , he answered by yes we applied windows update yesterday

 

The resolution,

I just re-run configuration wizard on servers one by one

 

Advertisements
Categories: Search, SharePoint 2013