After the last disaster recovery i started to receive this error from the Web Front End.
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Timer
Event ID: 6398
The Execute method of job definition
dfe5d15e-4a9e-4d4e-8e58-26ca0d11e2fa) threw an exception. More
information is included below.
An update conflict has occurred, and you must re-try this action. The
object SPSearchDataAccessServiceInstance Parent=SPServer Name=VC-SPCR0
is being updated by QUINCY\spconfigacct, in the OWSTIMER process, on
machine VC-SPCR0. View the tracing log for more information about the
For more information, see Help and Support Center at
This error was populating the Event Log every 5 minutes. Then I found this solution
I found that this issue is caused by a disaster recovery. The file-system cache on the front end is newer than the contents of the configuration database. After a disaster recovery, it may be necessary to manually clear the file system cache on the local machine.
1. Clear the file system cache on all servers in the farm running the timer service manually. To do this, stop the timer service, delete (or move) the contents of the folder at
%ALLUSERSPROFILE% \Application Data\Microsoft\SharePoint\Config\<someGuid>
2. Then, simply restart the timer service. The cache will be rebuilt and the issue should disappear. This should be done on every machine in the farm running the timer service
Hope this helps!
Microsoft Online Community Support
So what did I do?
- Stopped/Disabled the Timer jobs that run in minutes on the Central Admin Server VC-SPCR0 Deleted the <guid> from every server in the farm at this location C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config
- Then I restarted all the Timer jobs I disabled.