Project Online and Office 365
For Project Server 2013 we issued a public update in March, which is a required patch going forward for loading all future Cumulative Updates, such as the April CU. However, there was an issue with the Project Server part of the patch which would lead to an error when running the SharePoint Configuration Wizard. The error in the upgrade logs would be something like the following, with an EventID of ajxnf:
WARNING Project Web Instance 'SharePoint - 80:PWA' can only be upgraded once its database 'ProjectWebApp' has been upgraded ERROR Cannot upgrade [ProjectSite Name=f959de76-c4e9-4fa7-91a5-d9d9e287714b]. 38c20f9c-fdcc-b07a-f785-09836d46c179
WARNING Project Web Instance 'SharePoint - 80:PWA' can only be upgraded once its database 'ProjectWebApp' has been upgraded
ERROR Cannot upgrade [ProjectSite Name=f959de76-c4e9-4fa7-91a5-d9d9e287714b]. 38c20f9c-fdcc-b07a-f785-09836d46c179
and the error at the end of the configuration wizard, or in the PSCDiagnostics logs would be something like:
ERR Task upgrade has failed with a PostSetupConfigurationTaskException An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information: Failed to upgrade SharePoint Products.
ERR Task upgrade has failed with a PostSetupConfigurationTaskException
An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information: Failed to upgrade SharePoint Products.
This would be repeated for each PWA site in your farm. The fix for this issue is in the April Cumulative Update for Project Server 2013. The roll-up package including the SharePoint fixes for April has been delayed (at the time of writing expected w/c 4/22) – but if you are in this state currently and want to complete the configuration wizard then loading the individual Project Server 2013 April CU is certainly an option – see http://support.microsoft.com/kb/2760261.
If you have yet to install the March Public Update then I would suggest delaying until the full roll-up patch including SharePoint Server 2013 is released and then you can load the March PU, then the April CU and finally run the configuration wizard, which will avoid the failure noted above.
As always, please open a support incident if you need any assistance with any of the above steps.
I am pleased to announce the release of the April 2013 Cumulative Update (CU) for Project, Project Server and SharePoint for 2007, 2010 and 2013. Also for February this is earlier in the month (apart from the delayed shipments – see below), and since December 2012 we are planning to ship the Office Cumulative updates on the 2nd Tuesday (“Patch Tuesday”) of the even months. 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.
An important point for Project Server 2013 is the requirement to load the March 2013 Public Update. 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 CU – so a good practice would be to load the March PU, then the April CU and then run the configuration wizard. I will be adding a separate posting and link back which gives more details on the failure.
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
*** Update 5/17 - see http://support.microsoft.com/kb/2737990 for the rollup package *** There is a slight delay on the SharePoint/Project Server package – more details as soon as I have them, but expectation is for the week of 4/22. Due to the issue with the March PU and running the Configuration Wizard, you could consider loading the individual Project Server patch which does not include the SharePoint updates - http://support.microsoft.com/kb/2760261 if you need to get the configuration of the March PU completed. If you haven’t yet loaded the March PU then I would suggest waiting for the roll-up package for the April June CU.
Project 2013 Client Package:
Description of the Project 2013 hotfix package (Project-x-none.msp): April 9, 2013
We are working on the specific CU installation options 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.
Server Rollup Package(Recommended):
Description of the Project Server 2010 cumulative update package (Project server-package): April 9, 2013
Individual Project Server Package:
Only required if you do not install the Server Rollup.
Description of the Project Server 2010 hotfix package (Pjsrvwfe-x-none.msp): April 9, 2013
I’ll update with the DB version shortly. *** Update 9/24/2013 - The DB will show 14.0.6136.5000 ***
Project 2010 Client Package:
Description of the Project 2010 hotfix package (Project-x-none.msp): April 9, 2013
The client version number is 14.0.6137.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
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.
For those accustomed to Project Server 2007 Cumulative Updates, you should note that the MOSS Server Rollup Package does not contain the Project Server patches. As in Project Server 2007, the Server Rollup Packages are much larger but they will greatly simplify your Project Server patch deployment.
Installation of the client patch is straightforward and is the same as it was in Project 2007. 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.
No fixes this month for Project or Project Server 2007 – but listing the WSS and SharePoint patches for reference. 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.
*** Update 4/12 - Sorry - there is an update for Project Server 2007 - but no separate CU, it is included in the MOSS server-package listed below. Thanks Adrian for correcting me. ***
You can read about the fixes included in the April CU from the following articles:
Server Rollup Packages: Listing the WSS and SharePoint roll-up packages, but as there are no fixes for Project Server these do not include them.
Description of the Windows SharePoint Services 3.0 cumulative update server hotfix package (WSS server-package): April 9, 2013
Description of the SharePoint Server 2007 cumulative update server hotfix package (MOSS server-package): April 9, 2013
*** Update 4/12 - The MOSS server package includes a fix for Project Server 2007 - The Next and Previous buttons on the review timesheet detail page work in reverse. For example, when you click the Next button, the previous page is displayed. ***
Deploy cumulative updates (Project Server 2007)
Server Pack 3 for Project and Project Server 2007 has been released. While not required for the August CU, we strongly recommend that you install it as it contains a number of patches to improve performance and reliability. The following blog goes into more detail about SP3.
Office 2007 and SharePoint 2007 Service Pack 3 Availability
SP3 may be optional, however, Service Pack 2 for both WSS and Office Servers 2007 are required for this Cumulative Update. The KB articles below provide information on how to download and install SP2 if you have not already done so.
Description of Windows SharePoint Services 3.0 SP2 and of Windows SharePoint Services 3.0 Language Pack SP2
Description of 2007 Microsoft Office servers Service Pack 2 and of 2007 Microsoft Office servers Language Pack Service Pack 2
The Server CU is released in two different versions. The first version is in Individual Packages specific to a particular product like WSS and Project Server. These are smaller downloads but they do not include language packs or patches for other products so patches for those products would have to be downloaded and installed separately.
The second version is the Server Rollup Packages. This is a set of two rollup packages which contains all the fixes for WSS, Project Server and MOSS. These packages should be used when MOSS is part of the deployment and/or you have language packs installed. The Server Rollup Packages are much larger but they will greatly simplify MOSS patch deployment.
Client Installation: (For reference – there were no fixes released for Project 2007 client in this cycle)
In order to install this hotfix, you will need to have Microsoft Project 2007 SP2 installed on the client.
Description of Office Project 2007 Service Pack 2 (SP2) and of Office Project Language Pack 2007 Service Pack 2 (SP2)
Once we know that SP2 is installed, you will install the hotfix by performing the following steps:
1. Download the hotfix from either the KB Article.
3. Run the extracted .exe file to apply the patch to your Project Professional/Standard SP1 client.
Feel free to open a support incident at http://support.microsoft.com if you run into any issues with the installation and we will be happy to help!
Thanks to Jorge Ray (sorry Ray!) for this great blog post - http://blogs.technet.com/b/raymond_ris/archive/2013/04/04/cannot-open-or-create-word-documents-in-sharepoint-2013-with-office-2010-and-project-2013.aspx explaining how, after loading Project 2013 this can make your SharePoint libraries default to the 2013 versions of the protocol handlers. You might get a Url such as ms-word:nft|u|http://o15psvr:8080/Shared Documents/Forms/template.dotx|s|http://o15psvr:8080/Shared Documents for Word or ms-excel:ofv|u|http://sharePointDocumentlibraryURL for Excel.
The fix is easy – go take a look at Ray’s blog.