Project Server 2013
Project Server 2010
I am very pleased to announce the release of the April 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 April 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 April 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, June, August and October CU, is the requirement to load the March 2013 Public Update – or, Service Pack 1. As you may have seen with other posts there is currently an issue with Project Server 2013 and SharePoint Server 2013 Service Pack 1 and it is not currently possible to download SP1. There will be a re-release of SP1 but I don’t currently have an ETA for the re-release. In my tests the April CU will load fine over the existing SP1, but the re-release can also re applied over any existing SP1 which will then ensure that other patches will not have any issues loading (I understand that the WAC patch will not load on SP1, and there are other patches currently being held back that also have issues – one of which is a localization patch for Project that has some key fixes – see below).
*** Update 4/22 SP1 re-release
Stefan's blog has the full download links for SP1 http://blogs.technet.com/b/stefan_gossner/archive/2014/04/22/sp1-for-sharepoint-2013-has-been-rereleased.aspx
And patch again to avoid the lost resources issue - unless you also load April CU. http://support.microsoft.com/kb/2933444
Another important point to add here is that there was an issue with running the SharePoint Configuration Wizard on a server with Project Server 2013 installed – this is fixed by applying the April or June CU – so a good practice would be to load the March PU, then the December CU and then run the configuration wizard (if you didn’t already load the April, June, August or October CU).
Finally, the April 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.
Project and Project Server 2013
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:
There is no server rollup package this month. For details of the other Office 2013 package that you might want to load if you are running other SharePoint workloads please see http://support.microsoft.com/kb/2953733 - Office 2013 cumulative update for April 2014
Description of the Project Server 2013 hotfix package (Projectserverwfe-x-none.msp): April 8, 2014
There are some further fixes that I know many of you are waiting for relating to timesheet view load issues, status updates for master projects, unprotected baseline issues and grouping in views – these are all part of a localization patch that has been delayed due to the SP1 issues – more information when I have it, or if you are expecting a fix and have a case open contact the support person you are dealing with.
The dbo.Versions table should show 15.0.4605.1000 after applying April CU. This is the same as the April CU client and this version can safely be used to control client access without affecting the server side scheduling.
Description of the Project 2013 hotfix package (Project-x-none.msp): April 8, 2014
The client version number will be 15.0.4605.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’tset 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 April 2014 can be found here - http://support.microsoft.com/kb/2953732 - Office 2010 cumulative update for April 2014
Server Rollup Package(Recommended):
There is no rollup package for Project Server 2010 released yet this month – for the other patches for SharePoint Server 2010 and SharePoint Foundation 2010 see the Office article above – and I will update when the rollup is released..
Individual Project Server Package (Cumulative – but only the Project Server patches):
Description of the Project Server 2010 hotfix package (Pjsrvwfe-x-none.msp): April 8, 2014
There are also some fixes in the localization pack (also applicable to base language such as English US)
Description of the Project Server 2010 hotfix package (Pjsrvmui-<Language-Code>.msp; Pjsrvwfe-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2878266 (This page doesn’t look to be active yet)
The Project Server databases will be updated to version 14.0.7121.5000
Project 2010 Client Package:
Description of the Project 2010 hotfix package (Project-x-none.msp): April 8, 2014
The client version number is 14.0.7121.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.
Hi Brian, Just a quick question, since for last few times Project Server CU are individual packages and not roll-up any more. similarly for PS2010 this time as well, though you have mentioned under section "Updates for Project Server 2010" that roll up are recommended but whats the alternative if roll up is not available just like this month?Should we install SharePoint server 2013/2010 individual packages first? in-case of Project Server CU being individual CU package?Thanks.
Hi Brian,Do you have any updated info on the Timesheet view error issue? You mentioned it's delayed. Do you know any details beyond that? We are definitely having multiple clients dealing with it . We're currently having to scan the ULS for the error (after it occurs) and then run a SQL Query for each one and manually recreate the offending timesheets. Are there any, more automated, workarounds?Thanks,Henry
Khurram - it was a size issue that we were avoiding - you can install one, then the other and then run the wizard to get the same result.Henry - no news just yet, but SP1 just re-released.
Brian, what about the re-release of PS 2013 SP1? Should i apply it and forget about this April CU?Cheers!
Quote PS 2013 Hotfix: "When you click the New Project button in Project Center, you are unable to see the enterprise project types in the order that you have specified in their definition."Can anyone verify this? I have installed SP1, SP1 re-release and this April Hotfix, but the order in the "New Project" list still never changes.
Hi Adrian,we have the same issue. Installed SP1 (one System the old Version first and now the re-release, the other System directly the re-release) and also April CU installed. The issue with the wrong ordering is still there - and also seems to be the issue with the views error in Project Center. What we found out is that the database still shows 15.0.4569.1000 and not 15.0.4605.1000 as Brian states in his article. But the database is shown as "up to date" and upgrade-spprojectdatabase does nothing.......
Brain,My environment had SP1, So Installed SP1 - Release + April 14 PS CU , my DB version still shows 15.0.4569.1000 and not 15.0.4605.1000. Also my requriement of installing April 2014 Cu was to fix the timesheet view load issues. Even after the April 2014 CU installation issue still prevails - Not sure if the April 2014 PS CU has this fix or not. Can you please confirm.?timesheet view load issues -PWA : Migrated from 2007 to 2010 to 2013. : Single Entry Mode EnabledOne of our user/PM/Admin deleted the default T/s view after migrating to 2013.Now when ever user clicks on timesheet- it shows error - The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view. It doesnt allow the user to change the view. Workaround: Disable Single Entry Mode and allow user to access timesheet and save it and enable SEM again. With 4000 users using PWA - workaround is unacceptable.Pls advise.Thanks,Mustaq
I mention above that the timesheet view fix is NOT included in the April CU that has been released Mustaq. I have heard about the DB version not appearing to get updated - we are looking into that.Best regards,Brian.
Just asking around Mustaq and we should be releasing the full package for April CU including the timesheet view issue and this will also resolve the upgrader issue too. If anyone has any doubt over the upgraded version I'd suggest they re-apply the KB fix for the lost resources - just to be sure - http://support.microsoft.com/kb/2933444.
Brian, Thanks for your response, Stefen's Blog says April 2013 CU released, Does it has the Full Pacakge for April CU includinging the Timesheet View issue & Lost Resource issue as part of the •KB 2880484 - SharePoint Server 2013 with Project Server April 2014 CU ?? or we will have to wait for another package specific to Project Server 2013?. All your information and support is highly appreciated :) :).Thanks,Mustaq
Brian, Thanks for your response, Stefen's Blog says April 2014 CU released, Does it has the Full Pacakge for April CU includinging the Timesheet View issue & Lost Resource issue as part of the •KB 2880484 - SharePoint Server 2013 with Project Server April 2014 CU ?? or we will have to wait for another package specific to Project Server 2013?. All your information and support is highly appreciated :) :).Thanks,Mustaq
Brian, Any reports of issues related to "rulesaddmod.aspx" not containing a definition for "BaselineStaticTask" after applying PS 2013 APR 2014 CU on a server with SP/PS 2013 SP1?We received a report today from a customer receive this error when attempting to update rules related to automatically accepting and publishing time from timesheets to project plans. This is accessed inn the approval center under manage rules. They stated this worked prior to applying SP1/CU update this weekend. They receive the following error when attempting to create a new rule or edit an existing one:error when access /_layouts/15/PWA/Rules/RulesAddMod.aspx, Error=c:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\PWA\RULES\RulesAddMod.aspx(746): error CS0117: 'Microsoft.Office.Project.Server.Library.Rules.FieldSource' does not contain a definition for 'BaselineStaticTask'If you have already heard of this then I'd like to know how to resolve, otherwise we can open up a case to work on it.
How about the licenses? Do we able to upgrade?
Is there a separate CU for SharePoint 2010 as well?