SharePoint - Application Server Administration job failed for service instance Microsoft.Office.Server.

Asked By lena keshvari on 12-Nov-12 05:10 AM
I'm getting these errors continuously on one of our servers;

Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (8e6e53ce-710c-404e-a3c8-4b45cb4e2ca0).


Techinal Support Details:
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
   at System.Management.ManagementObjectCollection.get_Count()
   at Microsoft.Office.Server.Search.Administration.SearchAdminUtils.GetIPAddress(ManagementObjectSearcher ipSearcher, Boolean preferLast)
   at Microsoft.Office.Server.Search.Administration.SearchAdminUtils.PreferStaticIPAddress()
   at Microsoft.Office.Server.Search.Administration.SearchDataAccessServiceInstance.Synchronize(Boolean bCalledFromSSI)
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

Can anyone shed some light on this error (Event ID 6482) and how I can resolve this.

Thank you.

lena keshvari replied to lena keshvari on 14-Dec-12 04:27 AM
Hi All,

Finally I resolved my own issue, here it is for thosse of you who are having problems with this error

Clear the Config Cache

SharePoint maintains a disk cache based configuration on every server that contains the topology information and timer job definitions in “C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\<guid>\”.

Because old .xml files can get stuck here we may need to kick start the timer by clearing it.

The procedure is straight forward and needs to be carried out for every server:

  1. Stop the Administration and Timer service
  2. Delete all XML files in the directory (not the folder itself)
  3. Open “Cache.ini” and write the number 1 instead of the existing number (you might want to make a note of it)
  4. Start the services again
  5. Wait for a minute or two and see if the folder starts to fill up with xml files. It is likely that it will contain less than before clearing it.
  6. Check the cache.ini file. If it’s accessible and the number is considerably greater than 1 your cache has been properly initialized and chances are that your problems are now fixed. It didn’t fix my problem, so you may need to read on… (if you didn’t have the “888k” log entry mentioned above you probably have it now)

Note: Do not delete the Config Cache Folder!

The above procedure is grabbed from

Lena Keshvari