none
Is Deadlock problem resolved in Project Server 2010? RRS feed

  • Question

  • I am using Project Server 2007 sp3 and is failing my implementation because of huge problem of Deadlock in Publishing Project and Creating Project Workspace jobs in the queue.

    I am prepared to migrate to Project Server 2010 only if Microsoft has taken care of this issue in 2010 version.

    Can anyone specifically inform me if Microsoft has resolved this issue in Project Server 2010?

    Thanks!

    Wednesday, September 19, 2012 8:29 PM

All replies

  • Hi there,

    Sorry to hear about your SQL deadlock issues. We have completed many Project Server 2007 and 2010 deployments and not come across any issues with SQL deadlocks so I am not sure why your are. Are you using OOB functionality or do you have any custom solutions / event handlers etc? Do you have the SQL maintenance plans set up? It might be worth opening a support case with MS to get a resolution.

    Thanks

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Wednesday, September 19, 2012 9:16 PM
    Moderator
  •  

    Hi,

    Today Brian Smith has published new blog regarding project server queue performance. I think will be worth to review

    http://blogs.msdn.com/b/brismith/archive/2012/09/19/when-your-project-server-queue-slows-down.aspx


    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Please click Mark As Answer; if a post solves your problem or Vote As Helpful; if a post has been useful to you.This can be beneficial to other community members reading the thread.

    Wednesday, September 19, 2012 9:45 PM
    Moderator
  • Hi,

    Sorry for late response as I was looking into the links provided by Hrishi.

    Yes we are running custom code that loads/updates projects in our PWA but we have not touched event handlers.

    Our custom code does not insert the data directly to the tables and uses the class library provided by Microsoft. We run these custom application in parallel as we need to load/update hundreds of projects every hour. The application are developed in a way that if one application is working on project X the any other Application will not work on it.

    I have attached a couple of deadlock diagrams which may help you identify where the problem can exist. I would be grateful if someone can help me.

    The name of HOBT ID '72057594051952640' is ProjectServer_Draft.dbo.MSP_QUEUE_PROJECT_GROUP (index_id = 1)

    The name of HOBT ID '72057594052083712' is ProjectServer_Draft.dbo.MSP_QUEUE_PROJECT_GROUP (index_id = 3)

    The name of HOBT ID '72057594051952640' is ProjectServer_Draft.dbo.MSP_QUEUE_PROJECT_GROUP (index_id = 1)

    The name of HOBT ID '72057594052018176' is ProjectServer_Draft.dbo.MSP_QUEUE_PROJECT_GROUP (index_id = 2)

    Thanks!

    Monday, October 1, 2012 1:57 AM
  • Is there any Microsoft guy who can suggest something to resolve this problem?
    Wednesday, October 3, 2012 6:19 PM
  • Hi there,

    If this is a pressing issue for you, I strongly recommend that you open a support case with Microsoft for a speedy resolution.

    Many thanks

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Wednesday, October 3, 2012 7:16 PM
    Moderator
  •  

    But this issue is not related to out of the box functionality of project. Issues described here are related to customization. I don’t think MS can help you on that. But you can confirm their response by opening support case.


    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Please click Mark As Answer; if a post solves your problem or Vote As Helpful; if a post has been useful to you.This can be beneficial to other community members reading the thread.

    Thursday, October 4, 2012 2:44 AM
    Moderator
  • As far as I know you can get support from MS for supported custom development if required either via support or consulting services.

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Thursday, October 4, 2012 7:00 PM
    Moderator
  • Microsoft project server databases are highly relay on synchronization. It is recommended planning more maintenance activity regularly to overcome these issues. We have experienced this issue before and resolved by introducing DB maintenances plan like (DB Indexing, Remove bulk shadow table records, DB defragmentation,ect..).These plans also help to increase the performance of this application.

    Thanks!

    For Remove bulk shadow table records:

    http://support.microsoft.com/kb/2598007

    http://support.microsoft.com/kb/2596531

    Wednesday, November 7, 2012 12:10 PM
  • FYI, the deadlock problem is going to be resolved in the Project Server 2010 Cumulative Updates of October.
    Monday, July 29, 2013 8:13 PM