locked
System.OutOfMemoryException-in-Timesheet-Approval RRS feed

  • Question

  • Hi All,

    I have a project server 2007 sp2 and dec 09 CU setup.

    Here one of my Administartor+RM facing an issue "System.OutOfMemoryException-in-Timesheet-Approval page."

    I think that user is the only resource who is facing this issue because being myself as admin I have checked the same page but i didn't get any error there.

    I got, it generally comes when you have mutiple timesheet to approve or review. So if this is the cause then how can I resolve this.

    If there is something else can cause this issue then what is the reason for it and what are resolution steps for it. Kiindly let me know the same?

     


    Sachin Vashishth MCTS
    Wednesday, June 1, 2011 6:24 AM

Answers

  • Hey Sachin,

    If you don't restart the Project Server queue services on a regular basis, It will apparently has a memory leak and eventually consumes so much memory that the service stops responding. I have seen this so many times so this leads me to believe that there is some sort of unmanaged memory leak. Assuming that unmanaged memory leak is the issue, If we restart the queue service, It will help us to manage it well. But We might not be able to find the root cause why it keeps holding the huge memory as we don't have the code to look into.

    I would suggest if you can follow Christophe's nice blog to do it as a bat file:

    http://blogs.msdn.com/b/chrisfie/archive/2007/04/05/how-to-restart-the-project-server-queue-service-with-one-click.aspx

    Ref: http://technet.microsoft.com/en-us/library/cc298438(office.12).aspx

    You can also see the recommendation that you set the maximum number of processor threads settings based on the number of available processors (or cores). For example, if the Project Server application server uses a single dual-core processor, configuring the settings for two threads per queue is a good starting point. If your application server uses a quad dual-core processor, you might be able to use eight threads per queue. You can adjust these settings accordingly based not only on the volume of transactions, but also the average size of the transactions (for example, publishing 10-line projects versus 1000-line projects).



    Does that help? Thanks, Amit Khare |EPM Consultant| Blog: http://amitkhare82.blogspot.com http://www.linkedin.com/in/amitkhare82
    Wednesday, June 1, 2011 11:24 AM
  • Sachin,

    I wrote that original reply Amit references, we found that there was a memory leak in the PS2007 Queue Service that caused it to consume memory on the App Server. After a while it became unresponsive and needed to be restarted, at which point the queue process dropped down to the 50 meg memory mark which is the norm.

    I would suggest restarting the queue might be a way to address the issue, either manually or in a regular scripted fashion.


    Alex Burton
    www.epmsource.com | Twitter
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page
    Thursday, June 2, 2011 2:14 AM

All replies

  • Hello Sachin,

    I have faced the similar issue so many times mostly on the day when all Timesheets approvers used to hit the system on a specific day.A s a best practice, I used to verify the queue services memory utilization & restart the services/IIS.

     

    "The queue service has a memory leak which we never did isolate. Stopping and restarting the queue free'd up memory allowing it to complete. Have a look at the queue on you farm and see how much memory it is using, it should be around the 50meg mark, but sometimes got up to the 250meg mark on this farm."

    Explanation is below:

    http://social.technet.microsoft.com/Forums/en/projserv2010setup/thread/ca53eae5-19dd-4957-b5cc-6eb9639422f5

    Does that help?

     

    Thanks,

    Amit


    Thanks, Amit Khare |EPM Consultant| Blog: http://amitkhare82.blogspot.com http://www.linkedin.com/in/amitkhare82
    Wednesday, June 1, 2011 6:43 AM
  • Thanks Amit,

     

    Indeed above post is helpful in many case, but still I have to wait for Queue/IIS restart to check whether this suggestion will resolve my query or not.

    Can you help me to understand what does following line explains "The queue service has a memory leak which we never did isolate. "

     

    What is memory leak and what do you understand by Isolation here?


    Sachin Vashishth MCTS
    Wednesday, June 1, 2011 10:53 AM
  • Hey Sachin,

    If you don't restart the Project Server queue services on a regular basis, It will apparently has a memory leak and eventually consumes so much memory that the service stops responding. I have seen this so many times so this leads me to believe that there is some sort of unmanaged memory leak. Assuming that unmanaged memory leak is the issue, If we restart the queue service, It will help us to manage it well. But We might not be able to find the root cause why it keeps holding the huge memory as we don't have the code to look into.

    I would suggest if you can follow Christophe's nice blog to do it as a bat file:

    http://blogs.msdn.com/b/chrisfie/archive/2007/04/05/how-to-restart-the-project-server-queue-service-with-one-click.aspx

    Ref: http://technet.microsoft.com/en-us/library/cc298438(office.12).aspx

    You can also see the recommendation that you set the maximum number of processor threads settings based on the number of available processors (or cores). For example, if the Project Server application server uses a single dual-core processor, configuring the settings for two threads per queue is a good starting point. If your application server uses a quad dual-core processor, you might be able to use eight threads per queue. You can adjust these settings accordingly based not only on the volume of transactions, but also the average size of the transactions (for example, publishing 10-line projects versus 1000-line projects).



    Does that help? Thanks, Amit Khare |EPM Consultant| Blog: http://amitkhare82.blogspot.com http://www.linkedin.com/in/amitkhare82
    Wednesday, June 1, 2011 11:24 AM
  • Sachin,

    I wrote that original reply Amit references, we found that there was a memory leak in the PS2007 Queue Service that caused it to consume memory on the App Server. After a while it became unresponsive and needed to be restarted, at which point the queue process dropped down to the 50 meg memory mark which is the norm.

    I would suggest restarting the queue might be a way to address the issue, either manually or in a regular scripted fashion.


    Alex Burton
    www.epmsource.com | Twitter
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page
    Thursday, June 2, 2011 2:14 AM
  • Thanks Alexander for te explanation.

     

    One last question is there any way so that we can avoid this issue in future.

    And Queue maintenance suggested plan?


    Sachin Vashishth MCTS
    Thursday, June 2, 2011 7:38 AM
  • Hi,

    Restarting the queue on a regular basis should help. Other than that you could try and isolate the issue, or raise a support ticket directly with Microsoft to investigate.

    Of course, you could upgrade to 2010, which doesn't seem to exhibit the same behaviour :)

     


    Alex Burton
    www.epmsource.com | Twitter
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page
    Thursday, June 2, 2011 7:47 AM
  • Thanks Alexander,

    Will suggest my server team for weekly queue restarts and will work toward the up-gradation to PS 2010


    Sachin Vashishth MCTS
    Thursday, June 2, 2011 8:15 AM