none
Update was not applied due to a conflict RRS feed

  • Question

  • We are using Project Server 2010 with regularly scheduled updates including the newest CU.

    One of our status managers logged into their Approval Center --> History --> Status Updates screen this morning and saw this:

    She took this screen shot of the errors and sent it to me.  When I went to her computer, I clicked on Approval Center --> History --> Status Updates and there were four jobs listed that were published successfully from a different schedule.  NONE of these errored out tasks were there anymore.  The only evidence we have of these tasks errors is from this screen shot she took when she originally logged in.

    We've looked at the first few tasks listed and the updates have NOT been applied to the schedule, and if that is the case with all of them, that would be a huge loss of updates given the status of the vertical scroll bar in that screen shot.

    No errors show in the queue for yesterday or today to indicate these updates didn't go through and unfortunately, emails were turned off so none of the update messages were emailed.

    Anyone seen this before or have any ideas as to how I can track down the updates that were not applied?

    Thanks,


    DJ Johnson

    Thursday, November 1, 2012 2:32 PM

Answers

  • Hey DJ,

    Unfortunately, I have seen this before. The last time I saw this, it was due to a SQL deadlock issue where the update was selected as the victim and cancelled. In my case, the underlying cause was due to the DBA not maintaining the databases per best practice and statistics getting out of date. http://technet.microsoft.com/en-us/library/cc973097.aspx Once the stats were out of date, the level of locking in the transaction escalated and the deadlocks began.

    The worse thing about this issue is that there is no retry. I'm not sure how to reapply them since it was accepted but not applied. This may warrant a discussion with Microsoft Support.

    Treb Gatte | @tgatte | http://AboutMSProject.com

    Friday, November 2, 2012 6:51 AM
    Moderator

All replies

  • Hey DJ,

    Unfortunately, I have seen this before. The last time I saw this, it was due to a SQL deadlock issue where the update was selected as the victim and cancelled. In my case, the underlying cause was due to the DBA not maintaining the databases per best practice and statistics getting out of date. http://technet.microsoft.com/en-us/library/cc973097.aspx Once the stats were out of date, the level of locking in the transaction escalated and the deadlocks began.

    The worse thing about this issue is that there is no retry. I'm not sure how to reapply them since it was accepted but not applied. This may warrant a discussion with Microsoft Support.

    Treb Gatte | @tgatte | http://AboutMSProject.com

    Friday, November 2, 2012 6:51 AM
    Moderator
  • Thanks Treb... and good to hear from you.

    Gary, hope you guys made it through the storm ok!


    DJ Johnson

    Friday, November 2, 2012 1:03 PM