Configuration wizard failed “An update conflict has occurred, and you must re-try this action.”
While running the psconfig got the following error:
An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was thrown. Additional exception information: An update conflict has occurred, and you must re-try this action. The object SPUpgradeSession Name=Upgrade-20120310-130057-953 was updated by XXXX\svcSP_Farm, in the PSCONFIG (5168) process, on machine APP01. View the tracing log for more information about the conflict.
Cause
This issue occurs because a lock exists on the SPFarm object. Therefore, the SharePoint Products and Technologies Configuration Wizard cannot update the databases.
Fix:
Cleared the SharePoint Services configuration cache.
For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
939308 (https://support.microsoft.com/kb/939308/ ) Error message when you try to modify or to delete an alternate access mapping in Windows SharePoint Services 3.0: "An update conflict has occurred, and you must re-try this action"
You can also Ignore this lock by running the following command which will skip the lock step and proceed with the upgrade:
stsadm -o setproperty -pn command-line-upgrade-running -pv No
Cheers
Bala
Comments
Anonymous
November 17, 2013
It worked. Thanks for the solutionAnonymous
April 11, 2014
Worked for me..Anonymous
December 01, 2014
It worked for me. Thanks lot for the solutionAnonymous
January 08, 2015
Cool it worked, pefect. I wanted to know how do we figure out the problem and fix these issues ?Anonymous
April 08, 2015
For me, turns out I needed to restart my powershell session after a failed psconfig command. Seemed to release some resources that were locked. Also, a reboot of the server might helpAnonymous
May 27, 2015
Great brief instructions. Thanks a lot.Anonymous
June 23, 2015
awesome...this step saved my day...Anonymous
October 08, 2015
As for me, "PSConfig.exe -cmd upgrade -inplace b2b -force -wait" gives error, but "PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources" works well.