I am very pleased to announce the release of the June 2014 Cumulative Update (CU) for Project, Project Server and SharePoint for 2010 and 2013. Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed. Remember that this release for the 2010 products, like all CUs since the August 2012 Cumulative Update, has a hard requirement on Service Pack 1 – see notes below. 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 June CU will contain all previous CU releases (at least back to the applicable baseline Service Pack (SP1 for 2010 and March PU in the case of Project Server 2013). The June 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 April 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 June 2014 CU and then run the configuration wizard (if you didn’t already load the April 2013 through April 2014 CU).
The June 2014 for Microsoft Project and Project Server 2010, can be installed with Microsoft Project and Project Server 2010 SP2 – and overcomes the issues seen with the August 2013 CU under certain conditions where the database upgrader would fail.
Don’t forget we have a June 2014 Cumulative Update webcast next week – June 24th at 9am PST, and I will be joined by Maelle Kalboussi, Suzanne Sylliaasen and Solomon Woldesenbet - http://ignite.office.com/webcasts/support-webcast-service-packs-cumulative-updates
Project and Project Server 2013
An overview of all the Office 2013 releases for June 2014 can be found here - http://support.microsoft.com/kb/2970262 - Office 2013 cumulative update for June 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 April CUs from the following articles:
Project Server 2013 Server Rollup Package:
June 10, 2014 Cumulative Update for Project Server 2013
This is the full package including SharePoint 2013 fixes. 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.
There are a couple of individual packages this month – either read the descriptions to see which has the fixes you are interested in – or apply both – or (recommended) apply the full package above which includes both of these and the SharePoint fixes.
Hotfix 2880489 for Project Server 2013 June 10, 2014 (Projectserverwfe-x-none.msp)
Hotfix 2837680 for Project Server 2013 June 10, 2014 (Projectserverwfe-x-none.msp; Projectservermui-<Language-Code>.msp)
The dbo.Versions table should show 15.0.4615.1000 after applying the June 2014 CU. This same version number can be used to control the connecting client to the June 2014 level, but only if you are loading the June CU to the server and client.
Hotfix 2880493 for Project 2013 June 10, 2014 (Project-x-none.msp)
The client version number will be 15.0.4615.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.
An overview of all the Office 2010 releases for June 2014 can be found here - http://support.microsoft.com/kb/2970263 - Office 2010 cumulative update for June 2014
Server Rollup Package(Recommended):
June 10, 2014 Cumulative Update for Project Server 2010
No database updates – the database will stay or get updated to the April level – 14.0.7121.5000
Project 2010 Client Package:
Hotfix 2880537 for Project 2010 June 10, 2014 (Project-x-none.msp)
The client version number is 14.0.7125.5000, in case you want to limit the connection of certain patched release to Project Server 2010.
More information on deploying the 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 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, and at http://blogs.msdn.com/b/brismith/archive/2012/07/18/project-server-2010-from-august-2012-cumulative-update-onwards-you-will-also-need-to-load-sp1.aspx – the August Cumulative Update requires your client and server to already be at the Service Pack 1 (SP1) level – if you get a message saying the patch does not apply to your system then this may be the reason.
SP1 for the Project Server 2010 can be found at http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=26636 or SP2 from http://www.microsoft.com/en-us/download/details.aspx?id=39657
SP1 for the Project Professional 2010 client can be found at http://www.microsoft.com/en-us/download/details.aspx?id=26635 for the 32-bit and http://www.microsoft.com/en-us/download/details.aspx?id=26627 for the 64-bit or SP2 can be found at Service Pack 2 for Microsoft Project 2010 (KB2687457) 32-Bit Edition and Service Pack 2 for Microsoft Project 2010 (KB2687457) 64-Bit Edition.
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.
there seems to be no issue fixed in the Project Server 2010 package? Does it just contain the SharePoint fixes?
We don't always include all of the fixes in the KB list Christoph - I'm not directly involved in that part of the process so not sure what the criteria is for including them. There was just one 2010 fix that I am aware of - Time phased values shown in
Project Professional do not appear correctly in the PWA resource availability page - and this was in the client - so looks like you are probably right... No actual Project Server 2010 fixes (but there will be the previous fixes - for people who load June but
didn't have April for example).
PSA: Crtl-C/V is still broken in PS 2010 Rich Text Fields in this update.
thanks for the info above.
Any known issues from Project Server 2013 update? With the moment we updated a server (had April CU before) all status updates began failing with internal error.
ignore my last comment. The reason was that one:
Hi Brian, quick questions, I just reviewed our Production Server and we have only the Project Server 2010 SP1, and we want to update to the last version. So the next step will be to install the Server Rollup Package June 10, 2014 CU for PS2010 (mnetioned
above), is this correct?
Thanks for your comments...
Someone managed to solve this problem, about update status and actual work = ZERO? click in link ab
I'm just wondering if those client packages comes with WindowsUpdate or not?