I am very pleased to announce the release of the February 2014 Cumulative Update (CU) for Project, Project Server and SharePoint for 2010. 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 December CU will contain all previous CU releases (at least back to the applicable baseline Service Pack (SP1 for 2010). There aren’t any Project or Project Server 2013 patches this February due to the impending release of SP1 this quarter.
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 February CUs from the following articles:
Server Rollup Package(Recommended):
Description of the Project Server 2010 cumulative update package (Project server-package): February 11, 2014
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): February 11, 2014
Description of the Project Server 2010 hotfix package (Pjsrvwfe-x-none.msp; Pjsrvmui-<Language-Code>.msp): February 11, 2014
The Project Server databases will be updated to version 14.0.7115.5000
Project 2010 Client Package:
Description of the Project 2010 hotfix package (Project-x-none.msp): February 11, 2014
The client version number is 14.0.7117.5002, 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
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.
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.
"Assume that you have an MPP file that is created by using the Project server Save for Sharing feature and you are now saving it back to the server. In this case, the status manager property on each task and the project owner may change unexpectedly to
be the person who is saving the Save for Sharing MPP file to the server." I thought this was expected behavior. Nice to know it's so annoying it's actually a bug!
It was expected behavior Elli - until we decide it wasn't :).
After installing CU 2014-02 for Project Server 2010. we can no longer use the Ctrl key when editing rich text fields, in particular the bodies of issues in issue lists. Ctrl-C/V for copy/paste, Ctrl-left/rigth for word skipping navigation, Alt-Gr for some special characters. It worked correctly before and stopped working on the CU 2014-02 machines, tested in IE8 (as officially supported version) as well as the ever prevalent IE11 in IE7-mode and IE11 native.Does anyone experience this and found a workaround?
My site is experiencing the same issue. Users are no longer able to use ctrl V in rich text fields. Has microsoft come out with a patch for this yet?
We are experiencing the same issue. Is there any fix yet?
No fix in the near pipeline for the Ctrl-V issue Kiran, Adrian and Jonathan - sorry. The Paste option from the ribbon does work however. If you have a Premier support contract and wish to file a hotfix request you can, but the fix may still take some time - and has no guarantee of being accepted for fixing (although as we broke it in a regression it does put it higher up the list).Sorry for the inconvenience - Brian.
We use IE11 in combination with Project Server 2010 (still at the august 2012 release). What we see now since the introduction of IE11 is that it has become impossible to add tasks to existing projectplans due to an "unexpected argument" error. Alle emulation modes except "7" and "9" fail. But emulating IE9 in IE11 seems to fix this. I'm assuming this is a problem in IE11 emulations, and not an error on server side. Am I correct ?Anyone else with strange behaviour in de Planning PDP of projects when working in PWA ?
We are seeing an issue that I believe may be related to this. We are on SP2 with the CU2014-02 for SharePoint 2010 Enterprise. We, too, have lost the Ctrl-C/Ctrl-V capabilities of rich text fields in forms.We are seeing other problems since installing the February 2014 CU in list forms with rich text fields. These include frequent unexplained timeouts, and issues with receiving sporadic and unpredictable IE errors, without merit, stating "This page is accessing information that is not under its control. This poses a security risk. Do you want to continue?" We aren't reaching out to external content; and, the messages only occasionally appear, unlike what would be expected if we were.Just wondering if this is perhaps attributable to the February 2014 CU, or whether we have some other phantom issue buried somewhere.Also, has the CTRL-C/CTRL-V issue been fixed in the April 2014 CU?Thanks,Joseph Irvine
After I installed SharePoint 2010 CU as of April 2014, I've no longer use CTRL-V, any ideas?
Please support me also.
Sarra, check this forum post for some details on the CTRL-V issue.