PSConfig Wizard Configuration Failed: An Update Conflict has occurred, and you must re-try this action. An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was thrown

During Service pack 3 patching on MOSS 2007, SharePoint Products and Technologies Configuration Wizard ended with Error: Configuration Failed
An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was thrown“, An Update Conflict has occurred, and you must re-try this action.

PSConfig Wizard Configuration Failed: An Update Conflict has occurred. An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was thrown

Checked the Update Log file:
There is a log event with “An update conflict has occurred, and you must re-try this action. The object SPFarm Name=<Config-DB-Name> is being updated by <Farm-Admin-Account>, in the STSADM process, on machine <Server-Name>.  View the tracing log for more information about the conflict.”
An Update Conflict has occurred, and you must re-try this action

Solution:

  • Clear config Cache as per Microsoft KB: http://support.microsoft.com/kb/939308/ and run the PSconfig wizard again!
  • Try Runing: stsadm -o setproperty -propertyname command-line-upgrade-running -propertyvalue no  and then PSConfig -cmd upgrade -inplace b2b -wait -force

Salaudeen Rajack

Salaudeen Rajack is a SharePoint Architect with Two decades of SharePoint Experience. He loves sharing his knowledge and experiences with the SharePoint community, through his real-world articles!

3 thoughts on “PSConfig Wizard Configuration Failed: An Update Conflict has occurred, and you must re-try this action. An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was thrown

  • July 18, 2013 at 4:28 AM

    cannot specify network service unless the server role is single server

    Reply
  • March 14, 2013 at 3:49 PM

    Just execute this stsadm command first “stsadm -o setproperty -pn command-line-upgrade-running -pv Yes”

    and then run psconfig again.

    Reply
  • September 28, 2012 at 4:07 PM

    Thanks a lot, this saved my day! 😀

    Reply

Leave a Reply