Project Server 2010 and 2013 August 2015 PU Announcement

Yesterday saw the release of the August 2015 Public Update (PU) for Project, Project Server and SharePoint for 2013, and Project Server and SharePoint 2010.  We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Windows Update (Unless there is a security element or a fix deemed essential).  These are still all cumulative and include fixes released in all previous updates since the last baseline (SP1 for 2013 and SP2 for 2010).

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below.  SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs!  This also means RTM is no longer supported!  See too which describes an issue you might see if you don't have the 'right' SP1.  Slipstream would work with the original SP1 – but the updates require the re-released SP1.  Since the May PU this shouldn’t be an issue – but including here just in case.

Another important point to add here is that there was an issue early last year running the SharePoint Configuration Wizard on a server with Project Server 2013 installed – this is fixed by applying the April 2013 or later– so a good practice would be to load SP1, then the August 2015 PU and then run the configuration wizard (if you didn’t already load the April 2013 through June 2014 CU).

This release for the 2010 products, like all 2010 patches since the November CU, has a hard requirement on Service Pack 2 – see notes below, (Support for Microsoft Office 2010 Service Pack 1 ended on 10/14/14).  Don’t forget language packs SP2 if you have any language packs loaded!  In most of the KB articles the term hotfix is used in place of Cumulative Update.  They tend to be interchangeable terms – a Cumulative Update is just a hotfix built to a schedule.  I should also point out that the individual Project Server packages are only ‘individual’ in the sense that they do not include the SharePoint patches – they are still cumulative and the July PU will contain all previous CU releases (at least back to the applicable baseline).  Also worth noting that mainstream support for Project and Project Server 2010 ends this October 13th 2015 – see

Also a reminder – an SP1 patched 2010 system (with no SP2) is no longer supported – see the Lifecycle site for more information -

Project and Project Server 2013

An overview of all the Office 2013 releases for August 2015 can be found here – - August 11, 2015, update for Office

This include a number of fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production.

The article below provides information on how to deploy the Project Server Cumulative Update.

You can read about the fixes included in the Project and Project Server August PUs from the following articles:

Project Server 2013 Server Rollup Package

As mentioned above – this rollup package will only be available via the Download Center – not Windows Update.

August 11, 2015, cumulative update for Project Server 2013 (KB3055005) 

Project Server 2013 Individual Project Package – (cumulative, but only the Project Server fixes):

August 11, 2015, update for Project Server 2013 (KB3055018)

The dbo.Versions table should show 15.0.4743.1000 after applying the August 2015 PU.  The version number 15.0.4745.1001 can be used to control the connecting client to the August 2015 level, but only if you are loading the November CU or more recent to the server.  This version control no longer blocks server side scheduling engine since the November CU, but as this fix is server side you cannot use a higher value until you have this server patch or a more recent one.

SP1 for Project Server 2013 can be hound here -

Project 2013 Client Package:

August 11, 2015, update for Project 2013 (KB3055022)

The client version number will be 15.0.4745.1000 (I see 15.0.4745.1001 on my click to run Project Pro for Office 365).  The server scheduling engine is no longer blocked by version control since the November CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.4745.1000 value to control connection of the August 2015 PU patched client..  If you are running a server CU earlier than November 2014 CU then follow the suggested version number for the server patch level you are running.  See Project Server 2013- Controlling the version of connecting clients–and PWA edits- for more details.  As mentioned above – the version number entered no longer controls the server side scheduling engine – so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

We are working on the specific CU installation documentation for 2013, but the process hasn’t changed from 2010 – so if you are familiar with 2010 patching or read the 2010 instructions below you should be good to go.

SP1 for Project Professional 2013 can be found here -

Also note that Click to Run installations will be automatically patched (mine updated today to the same version as above).  Installations in Enterprise Environments that have been modified will be deployed based on the schedule determined by your Administrator.  See

Project and Project Server 2010

An overview of all the Office 2010 releases for August 2015 can be found here – - August 11, 2015, update for Office

This include a number of fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production.

The article below provides information on how to deploy the Project Server Cumulative Update.

You can read about the fixes included in the Project and Project Server August PUs from the following articles:

Project Server 2010

Project Server 2010 Individual package (cumulative – but just the Project Server 2010 fixes)

August 11, 2015, update for Project Server 2010 (KB3055046)

Project Server roll-up package

August 11, 2015, cumulative update for Project Server 2010 (KB3055038)

The Project Server database version does NOT get updated in August, so will show the same as June - 14.0.7151.5000 - after applying this or the package hotfix above, and running the configuration wizard.

Project 2010 Client Package:

August 11, 2015, update for Project 2010 (KB3055050)

The client version will be updated to 14.0.7154.5000.

More information on deploying the Cumulative Update:

The article below provides information on how to deploy the Project Server Cumulative Update.

Updates for Project Server 2010

As Project Server 2010 is now based on SharePoint Server 2010 we strongly recommend that you install the Project Server 2010 Server Rollup Package (when available) as there are a large number of individual server packages for SharePoint Server. The Project Server 2010 Server Rollup Package contains all the patches released in this Cumulative Update for SharePoint Foundation Server 2010, SharePoint Server 2010 and Project Server 2010.

As mentioned above, the November 2014 Cumulative Update and above requires your client and server to already be at the Service Pack 1 (SP2) level – if you get a message saying the patch does not apply to your system then this may be the reason – the message may be “expected version of the product was not found”

SP2 for the Project Server 2010 can be found at Service Pack 2 for Microsoft SharePoint and Project Server 2010 (KB2687452) – and a description at SP2 at Description of Project Server 2010 SP2.  If you have language packs installed then these will also need to be patched to SP2 or the message above will be seen – SP2 for the server language packs can be found at Download the Microsoft Office Servers 2010 Language Pack Service Pack 2 package now and a description at

SP2 for the Project Professional 2010 client can be found at for the 32-bit and for the 64-bit and a description at

Client Installation:

The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

1. Download the hotfix from the link in the KB Article.

2. Extract the patch package by running the .exe file that you downloaded.

3. Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

Or, from February 2015 onwards use Windows Update to download and install the patches.

Comments (14)

  1. anonymouscommenter says:

    Hi Brian After installing the June CU, we are facing a scenario wherein sending approval for a task even for a day sends the approval for the whole month even if nothing has been changed. Is this a known issue in project server 2013 or there has been some
    configurational changes that might have caused this behavior. Please reply on the thread that I have created on TechNet:

  2. anonymouscommenter says:

    Hi Brian,
    not sure if this is related to this update or something completely different, but recently, we had 2 cases were the OLAP Cube Role ProjectServerViewOlapDataRole in our PWA was suddenly empty, void of members. As result, all reports could not refresh data any
    We had to repopulate the role each time. Is that a know issue or undocumented feature? Patch level is/was very recent, May-August 2015.

  3. anonymouscommenter says:

    Hi Brian,
    in the description of the August 2015 PU there is a statement
    "You cannot use the QueueUpdateProject2 method in a PSI application to update values of custom fields."
    Is this used also when a plan is edited in PWA?
    We found that the values of a calculated Project custom field (calculated from task custom fields) is 0 after the plan had been updated in PWA with July 2015 PU. Publishing the plan with August 2015 PU does not seem to fix that, but after publishing it once
    with Project Prof (August 2015 PU) also PWA publishing seems to work with that plan again.

  4. anonymouscommenter says:

    update: Issue still exists. The calculated project custom field looses its value (published and reporting) when any change is done in PWA. A summarypublish seems to be enough to break it.

  5. anonymouscommenter says:

    …. and seemingly no fix in September CU 🙁

  6. anonymouscommenter says:

    Have any of you meet such an issue with the ‘Project description’ field after the CU of August is installed ?
    Many thanks for you help
    Best Regards

    1. Mark D says:

      Did the description problem get fixed? We seem to have this issue in Project Server 2010.

      1. Mark D says:

        Solved my own question — it’s in the January 2016 update:

  7. anonymouscommenter says:

    …. and also no fix for the project custom field issue in October CU 🙁

  8. We have the bug logged Christoph – no ETA yet – I’m hoping we might get it into December, but we will see.
    Sorry for the inconvenience here.
    Best regards,

  9. Dr Sylvester Benson says:


  10. anonymouscommenter says:

    Hi Brian,
    thanks for the feedback.
    I have something "new". In 2013 since July (and 2010 since May) if you save a baseline for selected tasks only with rollup there will be no data written into the tMSP_EpmTaskbaselineByDay table for the project summary task 🙁
    Also a known issue yet? And any hope for a 2010 fix?

  11. anonymouscommenter says:

    Anne, yes I am problems with the update operation of Project Description field

Skip to main content