none
Project Server Queue very slow! RRS feed

  • Question

  • Over the past week my project server 2013 queue has slowed down massively. 

    A new project takes over 20 minutes to create...

    I've tried the following 

    https://www.mpug.com/articles/when-your-project-server-queue-slows-down/

    http://blog.programframework.com/projectserver/project-queue-stuck-waiting-to-be-processed/

    https://blogs.technet.microsoft.com/brookswhite/2014/01/13/project-server-2010-queue-is-very-slow/

    this is the only thing i can see in the event logs that might be causing an issue? 

    I cant find much info on this error.. only this 

    https://trueinfosys.wordpress.com/2016/06/23/workflow-manager-fail-with-trusted-provider-is-missing-error/

    My settings match what is recommended 

    Monday, August 14, 2017 10:46 AM

Answers

All replies

  • Have you looked at available memory on both the SharePoint Servers and SQL server?   Are other SQL servers sharing the SharePoint server?

    Sometimes a DNS server can be having issues, and BIOS is being used to resolve IP addresses.

    Has any changes occurred to Anti-Virus and Malware software?  

    Is the slowness occurring at random times or is it just getting slower and slower?

    Have you rebooted the SharePoint and SQL server?  


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Tuesday, August 15, 2017 2:17 AM
    Moderator
  • Hi Michael,

    thanks for the suggestion. 

    Memory and CPU both seem pretty low at around 10 and 50%.

    Yes I've rebooted both. 

    The slowness is all the time and seems to be getting worse. 

    I've noticed quite a few messages like "Slow Query Duration: 60746.5978367339" in the ULS

    Tuesday, August 15, 2017 1:35 PM
  • Hello,

    Looking in the first image you sent, it looks like you have lots of jobs trying to process, going by the position column it looks like over 6,000,000?! If you change the queue history to include the past week or 2, what does the queue page show?

    Paul


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

    Wednesday, August 16, 2017 6:17 AM
    Moderator
  • yep you're right. 

    I'm not sure if there is actually 6 million, but there are pages and pages. 

    Interestingly they are all 'Reporting' jobs, and dont seem to be processing. 

    This is all jobs that aren't processing

    This is all jobs 'waiting to be processed'

    I've restarted the project service both from central admin and services.msc. These jobs never seem to process. 

    But If I start a new project, the new reporting jobs do eventually complete (after 20 minutes or so).

    Get-SPProjectWebInstance shows 

    I've re-provisioned with Upgrade-SPProjectWebInstance, but there is no change to the queue

    Wednesday, August 16, 2017 9:11 AM
  • Hello,

    Did you check you Anti-Virus and Malware settings?   Did they exclude the SharePoint libraries?   Have you tried disabling or removing the Anti-Virus and Malware to see if it runs faster?   If it does, then this indicates that it is not configured properly.


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Tuesday, September 5, 2017 2:28 AM
    Moderator
  • Hello,

     

    The below article covers all the basic points which the possible cause of the queue job slowness might be:

    https://blogs.msdn.microsoft.com/chrisfie/2008/03/21/improving-queue-performance/

     

    1. Poor database maintenance – see http://technet.microsoft.com/en-us/library/cc973097.aspx for Project Server 2010 and http://technet.microsoft.com/en-us/library/cc973097(v=Office.12).aspx for the 2007 version

    2. Large Shadow Tables – see http://support.microsoft.com/kb/2596531

    3. Incorrectly configured queue settings – too many threads for the hardware you have – the 2007 reference is still one of the best descriptions of the Project Server queue - http://technet.microsoft.com/en-us/library/cc197395.aspx 

    Update *** 3a (Thanks for the reminder Hrishi!) - Clock differences between servers - if the queue job can be processed 'now' but 'now' appears to be in the future to other servers then the job may go to sleep.

    4. Just busy – the queue is there to spread the work out – sometimes this might take a while (long duration ‘admin’ type plans publishing…)

    5. Poor execution plans for the stored procedures that control the queue processing.

     

    https://blogs.msdn.microsoft.com/brismith/2012/09/19/when-your-project-server-queue-slows-down/

     

    Cheers!!! Happy Troubleshooting!!!

    Shiva Prasad B C, MCP, MCSA

    Whenever you see a reply and if you think is helpful, click "Vote as Helpful"! And whenever you see a reply being an answer to the question of the thread, click "Mark as Answer

    Tuesday, September 19, 2017 2:48 PM
    Moderator