Application Server Administration job failed for service instance; SearchServiceInstance

Hi, I am running SharePoint 2013 Foundation on Windows 2008 R2 and trying to fix Timer Job error. 

Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (99f231d4-7bfb-40a5-bc6c-e5acdf6224cd).

Reason: I/O error occurred.

Technical Support Details:
System.IO.IOException: I/O error occurred. at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize() at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob

Search App Instance info:

Id            : 67474dbe-8a57-4500-b049-e8381fdeb17a
ServerName    : xxx-xxx-xx-x
IndexLocation : C:\Program Files\Windows SharePoint Services\15.0\Data\Applications
State         : Ready
DesiredState  : Ready

IndexLocation : C:\Program Files\Windows SharePoint Services\15.0\Data\Applications
Initialized   : True
Name          : 53adf2ba-a5da-44b2-b78e-56a07353d6bb
ServerName    : xxx-xxx-xx-x
ServerId      : 006cf6ee-0c2e-4876-b607-de29a0efa44a
Server        : SearchServiceInstance

I've checked the Content Index file directory exists and is writable by the SPSearch account yet I continue to get this error in the Application Event log every minute. 

December 12th, 2014 6:30pm

Hi Mike,

There is a timer job called Config Refresh that updates the cache on SharePoint servers in the farm.Like any other cache, config cache becomes stale over time.

This issue occurs if the contents of the file system cache on the front-end servers if they are newer than the contents of the Sharepoint configuration database. After you perform a system recovery, you may have to manually clear the file system cache on the local server.

Therefore, clearing the cache is needed to get all the SharePoint servers up to date on the latest farm information.

Refer these links for more details

Here is a detailed article for your reference:

Free Windows Admin Tool Kit Click here and download it now
December 15th, 2014 2:13am

Thanks for the suggestions but clearing the cache had no effect, well it did have one effect where previously one site collection had search working now it does not.  This is the second time I've cleared the cache and while it is quickly rebuilt it has not configured search.  The synchronization job fails due to "Reason: I/O error occurred."

Has anyone encountered this particular I/O error?  Is the error related to writing to disk or to the database? 

December 15th, 2014 7:28pm


Please check this URL that share all the steps

Free Windows Admin Tool Kit Click here and download it now
December 16th, 2014 8:46am

I tried cleaning the config cache on both the web server and the database server but am still getting the same error. I did notice that the error in the links you included were regarding a different error reason. I have the same issue the original poster had: Reason: I/O error occurred and again, clearing the cache did not work. Any ideas on what else could be causing the issue?
January 14th, 2015 10:31pm


We are also facing same error as Reason: I/O error . Did you manage to fi this , It would be great if you could share your findings

Free Windows Admin Tool Kit Click here and download it now
September 3rd, 2015 12:58am

In our instance (SP2013) the error was occurring because the SharePoint Administrator Service (SPAdminV4) was running under the Farm Administrator account. Due to the account not being Local admin we reverted the service to using the Local account and the error stopped. Do this on each SharePoint Server and restart the services.

SharePoint 2010 Administration Service

The SharePoint 2010 Administration Service is a Windows service installed by SharePoint. The service's name is SPAdminV4 and its primary executable is WSSADMIN.EXE in the 14\BIN directory. The task of the SharePoint Administration service is remarkably simple: it handles a specific subset of operations (exposed as methods of the SPAdministrationOperation object) which require local administrator rights on a server. The Timer Service uses an IPC (Inter-Process Communication) channel to call upon the Administration Service to execute these operations.

September 13th, 2015 11:32pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics