SharePoint 2010 Event ID 6482

SharePoint 2010 Event ID 6482 Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance
Background:
SharePoint 2010 Standard server.  Search was returning content, crawlers were filling the index.  No immediate customer impacting issue.
The Issue:
The event viewer had an error occurring every minute – Event ID 6482 which states:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (21e4447f-bac6-4a29-82db-165e074ac5db).
Reason: An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by domain\user, in the OWSTIMER (5040) process, on machine (server name).  View the tracing log for more information about the conflict.
Technical Support Details:  Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by domain\user, in the OWSTIMER (5040) process, on machine (server name).  View the tracing log for more information about the conflict.     at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()    at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)



Resolution:
The file system cache on all FE’s on which the timer service is running needs to be cleared.
:

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.