none
An update conflict has occurred, and you must re-try this action.

    Question

  • We are running MOSS 2007 Enterprise and I just applied WSS and MOSS SP2 to our environment.  Both updates completed successfully but I am getting an error when running the SharePoint Configuration Wizard to complete the update:

    An update conflict has occurred, and you must re-try this action. The object SPServer Name=ServerName Parent=SPFarm Name=PORTAL_CONFIG is being updated by Domain\Account, in the OWSTIMER process, on machine ServerName

    What can I do??

    Saturday, October 16, 2010 2:00 AM

Answers

  • Hi,

    Your behavior/symptoms are very similar to the one describe at number 4 in this article http://blogs.msdn.com/b/pmanchan/archive/2009/09/01/build-to-build-b2b-upgrade-of-the-sharepoint-environment-part-2.aspx

    The Configuration Wizard Fails at step 4 with the following message:

    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 DiagnosticsService Parent=SPFarm
    Name=<config DB> is being updated by Domain\User, in the w3wp process, on machine <machine name>. View the tracing log for more information about the conflict.

    Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object DiagnosticsService Parent=SPFarm Name=<config DB> is being updated by Domain\User, in the w3wp process, on machine <machine name>. View the tracing log for more information about the conflict.
     

    Resolution:
    ===========
    Clear the config cache. Refer KB 939308 for the steps for clearing the cache.ini

    Re-run the following command to perform the upgrade:

    psconfig -cmd upgrade -inplace -b2b -force -wait

    Hope it helps you, Mario


    Mon Blog/My Blog (in french) LinkedIn
    • Marked as answer by Sephiroth0327 Saturday, October 16, 2010 2:33 AM
    Saturday, October 16, 2010 2:13 AM

All replies

  • Hi,

    Your behavior/symptoms are very similar to the one describe at number 4 in this article http://blogs.msdn.com/b/pmanchan/archive/2009/09/01/build-to-build-b2b-upgrade-of-the-sharepoint-environment-part-2.aspx

    The Configuration Wizard Fails at step 4 with the following message:

    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 DiagnosticsService Parent=SPFarm
    Name=<config DB> is being updated by Domain\User, in the w3wp process, on machine <machine name>. View the tracing log for more information about the conflict.

    Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object DiagnosticsService Parent=SPFarm Name=<config DB> is being updated by Domain\User, in the w3wp process, on machine <machine name>. View the tracing log for more information about the conflict.
     

    Resolution:
    ===========
    Clear the config cache. Refer KB 939308 for the steps for clearing the cache.ini

    Re-run the following command to perform the upgrade:

    psconfig -cmd upgrade -inplace -b2b -force -wait

    Hope it helps you, Mario


    Mon Blog/My Blog (in french) LinkedIn
    • Marked as answer by Sephiroth0327 Saturday, October 16, 2010 2:33 AM
    Saturday, October 16, 2010 2:13 AM
  • You're a life saver!!!!  That worked perfectly. 
    Saturday, October 16, 2010 2:32 AM
  • Just curious, why do we want to run psconfig instead of the GUI version of the config wizard?
    Saturday, October 16, 2010 4:37 AM
  • In your situation, you could run the config wizard or psconfig and the result will be the same. Why ? Because this command is automatically run when you run the SharePoint Products Configuration Wizard if the product has to be upgraded.

     


    Mon Blog/My Blog (in french) LinkedIn
    Saturday, October 16, 2010 2:16 PM
  • Thank you so much for solution, which a couple of years after you suggested it, saved me :)
    Saturday, October 13, 2012 1:06 AM