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 (http://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 (8)

  1. Shilpee Mittal says:

    It worked. Thanks for the solution

  2. vijay says:

    Worked for me..

  3. ravindra says:

    It worked for me. Thanks lot for the solution

  4. Pradeep Sharma says:

    Cool it worked, pefect. I wanted to know how do we figure out the problem and fix these issues ?

  5. GlennDoo says:

    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 help

  6. Mohsen says:

    Great brief instructions. Thanks a lot.

  7. saraku81 says:

    awesome…this step saved my day…

  8. Vladilen Karassev says:

    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.

Skip to main content