SharePoint 2010: Application Server Admin Job Failed for Service Instance

After running the PowerShell script to complete the configuration of the Super User and Super Reader account, and rebooting the server, you may see the following error in the Windows Application log on your SharePoint 2010 servers:

Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (38410267-e262-4418-b67d-36516a88bb4b)

Reason: Object ede471fa-669d-444b-8f26-90e4dead5302-query-0 not found.

Here’s a screen capture of the error in the Application log:


The file system cache on the SharePointer server on which the timer service is running needs to be cleared. Here are the steps as directed by Microsoft to resolve the above error:

  1. Stop the SharePoint 2010 Timer service
  2. Navigate to the cache folder
    In Windows Server 2008, the configuration cache is in found here:
    Then locate the GUID folder that has the cache.ini file
    (Note: The ProgramData folder may be hidden. To view the hidden folder, change the folder options as required)
  3. Back up the cache.ini file.
  4. Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt.
  5. When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.
  6. Double-click the cache.ini file.
  7. On the Edit menu, click Select All. On the Edit menu, click Delete. Type 1, and then click Save on the File menu. On the File menu, click Exit.
  8. Start the SharePoint 2010 Timer service
    Note:  The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
  9. Make sure that the cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the cache.ini file is not 1.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s