I am very pleased to announce the first of the new ‘odd month’ Cumulative Update releases – the July 2014 Cumulative Update (CU) for Project, Project Server and SharePoint 2013. Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed. In most of the KB articles the term hotfix is used interchangeably with 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 CU contains all previous CU releases (at least back to the applicable baseline of the March PU in the case of Project Server 2013). The July CU for Project and Project Server 2013 also include fixes that were included in SP1.
An important point for Project Server 2013, as was the case also for the April 2013 through June 2014 CU, is the requirement to load the March 2013 Public Update – or, Service Pack 1.
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 the March PU or SP1, then the July 2014 CU and then run the configuration wizard (if you didn’t already load the April 2013 through June 2014 CU).
Project and Project Server 2013
An overview of all the Office 2013 releases for July 014 can be found here – http://support.microsoft.com/kb/2978164 – Office 2013 cumulative update for July 2014
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 July CUs from the following articles:
Project Server 2013 Server Rollup Package:
July 8, 2014 Cumulative Update for Project Server 2013 package
This is the full package including SharePoint 2013 fixes. As for the recent full package CUs it comes in three parts. You need to download all three parts and execute them (in any order), which will just unzip the contents – which should all be placed in the same folder. Once extracted execute the ubersrvprj.exe to actually do the installation on your farm. The other two files are cabinet files that are used during the installation. The folder contents will look like this – I also have the extracted client patches for x86 and x64 in the same directory, and the individual Project Server patch.
*** Update 7/16 – Thanks to Hans for pointing out that one of the cab files is also incorrectly labelled as 2010 on the download site – I'll try and get this corrected – but the file itself is fine (and 2013). ***
Project Server 2013 Individual Project Package – (cumulative, but only the Project Server fixes):
Hotfix KB2882995 for Project Server 2013 July 8, 2014 (Projectserverwfe-x-none.msp; Projectservermui-<Language-Code>.msp)
The dbo.Versions table should update to 15.0.4629.1000 after applying the July 2014 CU. This same version number can be used to control the connecting client to the July 2014 level, but only if you are loading the July CU to the server and client.
Project 2013 Client Package:
Hotfix KB2882986 for Project 2013 July 8, 2014 (Project-x-none.msp)
The client version number will be 15.0.4629.1000 if you want to restrict the client version that can connect to the server. See Project Server 2013- Controlling the version of connecting clients–and PWA edits- for more details – but this version is good for both the client and server – don’t set if you have only updated the client as the server scheduling will then not work.
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.
Also note that Click to Run installations will be automatically patched, usually within a month. Installations in Enterprise Environments that have been modified will be deployed based on the schedule determined by your Administrator.