Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance

Event Type:    Error
Event Source:    Office SharePoint Server
Event Category:    Office Server Shared Services
Event ID:    6482
Date:        2/12/2013
Time:        4:39:40 PM
User:        N/A
Computer:    "SERVER NAME"
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (75d4a317-f4ef-4afb-a3c6-c907afccceba).

Reason: Cannot open database "SharedServices_DB" requested by the login. The login failed.
Login failed for user 'CORP\SERVERNAME$'.

Techinal Support Details:
System.Data.SqlClient.SqlException: Cannot open database "SharedServices_DB" requested by the login. The login failed.
Login failed for user 'CORP\SERVERNAME$'.
   at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.Office.Server.Data.SqlSession.OpenConnection()
   at Microsoft.Office.Server.Data.SqlSession.ExecuteNonQuery(SqlCommand command)
   at Microsoft.Office.Server.Administration.SharedObjectStore.Initialize()
   at Microsoft.Office.Server.Administration.SharedObjectStore.GetObject[T]()
   at Microsoft.Office.Server.Administration.SharedResourceProvider.Microsoft.Office.Server.Administration.ISharedObjectStore.GetObject[T]()
   at Microsoft.Office.Server.Administration.SharedApplicationCollection`1.GetValue(SharedResourceProvider sharedResourceProvider)
   at Microsoft.Office.Server.Administration.SharedApplicationCollection`1.get_Item(SharedResourceProvider sharedResourceProvider)
   at Microsoft.Office.Server.ServerContext.GetApplication[S,T](String name)
   at Microsoft.Office.Server.Search.Administration.SearchContext..ctor(ServerContext serverContext, Boolean cached)
   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)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

---
Solution:

Below is the step by step provided by Microsoft in this KB Article for doing this:

1. Stop the Windows SharePoint Services Timer service (Found in Windows Services)
2. Navigate to the cache folder
   In Windows Server 2008, the configuration cache is in the following location:
   Drive:\ProgramData\Microsoft\SharePoint\Config
   In Windows Server 2003, the configuration cache is in the following location:
   Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config
   Locate the folder that has the file "Cache.ini"
   (Note: The Application Data 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. Note 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 Windows SharePoint Services Timer service
9. 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.
10. 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.

- See more at: http://www.social-point.com/sharepoint-2010-event-id-6482-application-server-administration-job-failed-for-service-instance-microsoft-office-server-search-administration-searchserviceinstance#sthash.d9rBKjLc.dpuf

Below is the step by step provided by Microsoft in this KB Article for doing this:

    Stop the Windows SharePoint Services Timer service (Found in Windows Services)
    Navigate to the cache folder
    In Windows Server 2008, the configuration cache is in the following location:
    Drive:\ProgramData\Microsoft\SharePoint\Config
    In Windows Server 2003, the configuration cache is in the following location:
    Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config
    Locate the folder that has the file "Cache.ini"
    (Note: The Application Data folder may be hidden. To view the hidden folder, change the folder options as required)
    Back up the Cache.ini file.
    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.
    Note 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.
    Double-click the Cache.ini file.
    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.
    Start the Windows SharePoint Services 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.

Below is the step by step provided by Microsoft in this KB Article for doing this:

1. Stop the Windows SharePoint Services Timer service (Found in Windows Services)
2. Navigate to the cache folder
   In Windows Server 2008, the configuration cache is in the following location:
   Drive:\ProgramData\Microsoft\SharePoint\Config
   In Windows Server 2003, the configuration cache is in the following location:
   Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config
   Locate the folder that has the file "Cache.ini"
   (Note: The Application Data 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. Note 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 Windows SharePoint Services Timer service
9. 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.
10. 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.

- See more at: http://www.social-point.com/sharepoint-2010-event-id-6482-application-server-administration-job-failed-for-service-instance-microsoft-office-server-search-administration-searchserviceinstance#sthash.d9rBKjLc.dpuf

Below is the step by step provided by Microsoft in this KB Article for doing this:

1. Stop the Windows SharePoint Services Timer service (Found in Windows Services)
2. Navigate to the cache folder
   In Windows Server 2008, the configuration cache is in the following location:
   Drive:\ProgramData\Microsoft\SharePoint\Config
   In Windows Server 2003, the configuration cache is in the following location:
   Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config
   Locate the folder that has the file "Cache.ini"
   (Note: The Application Data 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. Note 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 Windows SharePoint Services Timer service
9. 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.
10. 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.

- See more at: http://www.social-point.com/sharepoint-2010-event-id-6482-application-server-administration-job-failed-for-service-instance-microsoft-office-server-search-administration-searchserviceinstance#sthash.d9rBKjLc.dpuf