Like This ...

OWSTIMER Issue in Restore

Nasty Restore Problem (OWSTIMER Issue/SPUpdatedConcurrencyException/SPDatabaseServiceInstance)

"An update conflict has occurred, and you must re-try this action. The object SPSearchDatabase Name=WSS_Search_epm2007demo Parent=SPDatabaseServiceInstance is being updated by EPM2007DEMO\FarmAdmin, in the OWSTIMER process, on machine EPM2007DEMO. View the tracing log for more information about the conflict."

"Object WSS_Search_epm2007demo failed in event OnPostRestore. For more information, see the error log located in the backup directory. SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SPSearchDatabase Name=WSS_Search_epm2007demo Parent=SPDatabaseServiceInstance is being updated by EPM2007DEMO\FarmAdmin, in the OWSTIMER process, on machine EPM2007DEMO. View the tracing log for more information about the conflict."

1. Start SharePoint 3.0 Central Administration (you might have to pause the Windows SharePoint Timer service before you can actually get there -especially if you’re using a VPC – for whatever reason, OWSTIMER.EXE can easily soak up whatever CPU cycles you have…)
2. Go to Operations
3. Under Logging and Reporting, choose Diagnostic Logging.
4. Under Event Throttling, choose All as the category (this may be unnecessary, as it could be the default, but judging by the amount oflogging, it probably isn’t)
5. Under Trace Log, set “Number of log files” to something reasonable – say, 5. You can leave “Number of minutes…” to be 30, unless you want those 5 files to be smaller in size. By default number of minutes is 30.
--OR--
1. In you backup folder open spbackup.xml
2. Search for Microsoft.SharePoint.Search.Administration.SPSearchDatabase
3. Under node look for
Key="STATE.xml">0000000A.bak

NOTE: is an actual GUID, not the string “
4. Take not of the file contained in CDATA (i.e. 0000000A.bak).
The file name can change from backup to backup
5. In your backup folder open 0000000A.bak using a standard text editor
6. Locate node
7. Change value to a date in the future tomorrow could be a good date)
8. Save the text file.
9. Perform the restore operation as you would usually do.
--OR--
An update conflict has occurred, and you must re-try this action.
http://support.microsoft.com/kb/939308

blog comments powered by Disqus