Slow Save Times Project Server 2010 SP2 RRS feed

  • Question

  • We are operating Project Server 2010 with SP2.  We have at least two users that are having very long save times.  Other people are unable to replicate the long save times for the same files.  When observing the queue, the file will quickly go to 89% and then stay there for 17 minutes, or longer.  This even happens when there is no competition on the Server.

    The one thing that these two individuals have in common is that they are the only users at their respective sites.  It begs the question as to whether their sites are blocking packets.  Are there diagnostics that can be run as to why the saves are hanging?

    Thursday, January 16, 2014 7:00 PM

All replies

  • Hi Chris,

    I would say that you did 90% of the job, identifying that users that are experiencing this behavior are both located on the same site. It is more than probably the root cause.

    Then it is more a network issue than a project issue, which should be manage with the network/infrastructure team, together with the farm admin.

    Hope this helps.

    Guillaume Rouyre - MBA, MCP, MCTS

    Thursday, January 16, 2014 7:06 PM
  • Hi Chris,

    If this problem is occurring for only 2 users the nit may be because of network packets/speed.

    You can test it via publish the same project from any other site if you face same issue then it would be project specific otherwise it would be network specific. If it is project specific then you have to drill down for root cause.

    I have seen this issue for some of my client where for some site performance is good and for few sites its very poor. Performance also depends on geographical location of SERVERs(data center) some times.  


    Thursday, January 16, 2014 7:51 PM
  • The User in question is the only user at this one particular site.  Our Server is currently 2010 in BCM (though that will be changing tomorrow morning).  The User has access to a 2010 Client (w/ SP1) and a 2007 client.  His saves with the 2007 client have been fine, but he is getting the long save times with the 2010 client.  We can't blame BCM because when he connects to our test Server, which is out of BCM, his 2010 client still has long save times.  Is there some kind of firewall setting that would delay 2010 packets but not 2007 packets?

    I feel bad for the guy; he will be losing his 2007 client Monday morning and his save times are going to stink.

    Friday, January 17, 2014 1:01 PM
  • we have a guy that is in the next building over from our building that is seeing his file take 21 minutes to save.
    Friday, January 17, 2014 2:59 PM
  • Do you have the correct SQL maintenance plans set up to optimise the Project Server databases? Do you have other optimisations set? See:



    Paul Mather | Twitter | | CPS

    Friday, January 17, 2014 3:52 PM
  • What does the project schedule look like?

    Does he have task with over 10 resources assigned to task.  Does he have tasks with 30 or more users on the task?

    Is the project schedule large in size.  Have many tasks does the schedule have?  Is it over 1000 or 10,000.

    Have you tried saving the project schedule closer to the server? 

    Is it faster if the ADMIN saves the project?

    Compared to the other project schedules, do you see anything unusual with this one?

    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Blog contains my field notes and SQL queries

    Tuesday, January 21, 2014 12:31 AM