Project Server 2010: Updated June Cumulative Update has been released


I’ve updated the Project Server CU posting for June 2013 over at http://blogs.technet.com/b/projectsupport/archive/2013/06/14/microsoft-project-server-2007-2010-and-2013-june-2013-cu-announcement.aspx but thought it also worth a shout out here.  The recommendation is also that anyone who installed the earlier patch in the few days it was available should now install these updated patches.  They have new KB numbers too.  These updates address the issues found with Project Server and timesheet submission as we as some SharePoint issues that caused the withdrawal of the roll-up package and other SharePoint fixes.

Description of the Project Server 2010 cumulative update package (Project server-package): July 10, 2013

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

Individual Project Server Package (Cumulative – but only the Project Server patches):

Only required if you do not install the Server Rollup.

Description of the Project Server 2010 hotfix package (Pjsrvwfe-x-none.msp): July 10, 2013

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

Comments (4)

  1. Jim Blain says:

    In the description of Project Server Cumulative update (support.microsoft.com/…/2817538) one fix is described as "Unnecessary user account synchronization occurs and you experience performance issues in Project Web App. For example, you cannot log on the server."

    What constitutes "unnecessary" synchronization? Our nightly synchronization process kicks off a large number of "delete single user" and "Add single user" activities that individually can take 40-90 seconds to complete and therefor fill up the queue for nearly 4 hours. Does this hotfix/cumulative update address that?

    Thanks.

  2. BriSmith says:

    It sounds likely that it will Jim.  One example is that the case of a name being different (Brian v brian) would trigger a sync.

    Best regards,

    Brian.

  3. Jean-Baptiste says:

    Hello,

    The TimeSheet problem still occurs with KB 2817530 installation.

  4. BriSmith says:

    Hi Jean-Baptiste, could you elaborate?  We often fix things that have fairly generic error messages – but the fix will be very specific.  Sounds like you are hitting a different issue that we have not yet addressed – best to open a support incident so we can dig deeper.

    Best regards,

    Brian.