msProjectExperts recommends extreme caution when preparing to install the Project Server 2013 March 2013 PU as a flaw in the release does not allow either the PWA instance(s) or the Project Server database(s) to upgrade. Specifically, if you follow the installation with PSConfig or Upgrade-SPFarm command to upgrade Project Server 2013 RTM, the upgrade is unsuccessful. You should delay running the SharePoint Configuration Wizard, PSConfig, or the Upgrade-SPFarm commands until you consecutively install the Project Server 2013 April 2013 CU or a later CU release. See
the TechNet blog for further details of this issue.
The first thing to note about this particular patch, Project Server 2013 Public Update, is the new baseline for applying any future updates to Project Server 2013. For those of you familiar with previous products this would be similar to the requirement to install SP1 prior to any releases post the Service Pack 1 release. There is also a Project Server 2013 Hotfix release date of April 9, 2013; this hotfix resolves an issue post installation that causes the March 2013 PU to fail during the upgrade.
If you need to fix a failure of the March 2013 PU, follow the instructions below for applying the Project Server 2013 Hotfix Package April 9, 2013.
Warning: If you are reading this prior to installing the Project Server 2013 March 2013 PU, Microsoft suggests that you wait until the release of the Project Server 2013 Server Rollup Package due the week of April 22, 2013.
Project Server 2013 March 2013 PU
Please read all of the documentation provided by Microsoft prior to installing the March Public Update, and remember to complete a full backup of your farm prior to installing any release in case you need to roll back to a previous state in your farm. Refer to this link for specific items this release fixes:
Information: Post applying the patch may detail errors in the upgrade logs possibly with the following:
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 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.
These messages repeat for each PWA site in your farm, and the fix for this issue is in the April Cumulative Update for Project Server 2013, which Microsoft expects to release April 22, 2013.
KB2760261 Hotfix Installation Steps
If you are reading this due to issues that arose after applying the March 2013 PU and your upgrade results in a failure, please read the additional documentation from Microsoft on repairing a patch failure prior to installing the Project Server 2013 hotfix package: April 9, 2013 . You will need to follow the below steps to repair your installation:
Navigate to the KB2760261 hotfix at http://support.microsoft.com/kb/2760261 on the application server running Project Server 2013 as shown in PU Fix 1, and click the Hotfix
Download Available button to download the hotfix.
PU Fix 1: Project Server 2013 hotfix package
Read and accept the terms and conditions and then click the Accept button to accept the terms of the agreement.
Complete the Hotfix Request form by selecting the checkbox next to the hotfix you want to download, enter the e-mail address in the Email field to request the download link from Microsoft, and complete the Confirm e-mail field by re-entering the e-mail address.
After completing the email address section, in the Enter the characters you see section as shown in PU Fix 2, enter the characters that display above the field. By entering the characters this confirms that a person is requesting the download and not a system sending an automatic response, then click the Request Hotfix button.
PU Fix 2: Hotfix Request form
When you receive the confirmation email, copy the download link within the e-mail text. Paste the link in the address bar in a new browser window on the server where you are applying the hotfix, then click the Enter key on your computer keyboard.
In the resulting Do you want to run or save 462098_intl_x64_zip.exe (71.4 MB) from hotfixv4.microsoft.com? dialog shown in PU Fix 3, click the Save pick list, select the Save as item, and then browse to a location where you want to save the file as shown in PU Fix 4.
PU Fix 3: Hotfix download dialog
PU Fix 4: Save As dialog
Once the download is complete click the Open folder button, or navigate to the save location to install the update later.
Right-click the file name and select the Run as Administrator item to install the file using the local machine administrator role.
In the Microsoft Self-Extractor dialog, click the Continue button to extract the files onto your system as shown in PU Fix 5.
PU Fix 5: Microsoft Self-Extractor dialog
Click the OK button to close the Microsoft
Self-Extractor dialog as shown in PU Fix 6.
PU Fix 6: All files were successfully unzipped
After extracting the .zip file, right-click the file name 462098_intl_x64_zip.exe and select the Run as Administrator item on the pick list.
In the Hotfix for Microsoft Project Server 2013 (KB2764026) 64-Bit Edition dialog, select the Click here to accept the Microsoft Software License Terms checkbox, and then click the Continue button to install the hotfix as shown in PU Fix 7.
PU Fix 7: Accept the Microsoft Software License Terms
After the installation of the hotfix completes, the resulting Hotfix for Microsoft Project Server 2013 (KB2760261) 64-Bit Edition dialog displays with a Do you want to reboot now to complete the installation of this package? message. Click the Yes button to reboot the server now as shown in PU Fix 8.
PU Fix 8: Do you want to reboot now?
Once the system reboots, open the SharePoint Products Configuration Wizard and click the Next button to run the wizard to complete the upgrade for the PWA instance(s) and the Project Server database(s) as shown in PU Fix 9.
PU Fix 9: SharePoint Products Configuration Wizard dialog
In the SharePoint Products Configuration Wizard dialog, click the Yes button to continue the configuration to allow the restart of the following services: Internet Information Services, SharePoint Administrative Service, and SharePoint Timer Service as shown in PU Fix 10.
PU Fix 10: Choose yes to restart the services
The SharePoint Products Configuration Wizard dialog displays the Completing the SharePoint Products Configuration Wizard page. Do
not change any of the default settings, and then click the Next button to continue.
When the Configuration Successful dialog displays, click the Finish button to close the wizard and launch the SharePoint 2013 Central Administration website to continue.
Once the SharePoint 2013 Central Administration site launches, from the Quick Launch menu click the Upgrade and Migration link.
On the resulting Upgrade and Migration page, click the Review the Patch Status link to review the status of the upgrade as shown in PU Fix 11. In the Microsoft Project Server 2013 section, shown in PU Fix 12, you see the Hotfix for Microsoft Project Server 2013 (KB2760261) 64-Bit Edition with an Installed status.
PU Fix 11: Manage Patch Status dialog, upper section
PU Fix 12: Manage Patch Status dialog, lower section
Finally, check the database status by clicking the Upgrade and Migration link on the Quick Launch menu to display the Upgrade and Migration page. On the Upgrade and Migration page, click the Review Database Status link to display the Manage Databases Upgrade Status page. On the Manage Databases Upgrade Status page shown in PU Fix 13, for Type: ProjectDatabase and Content Database the status should indicate No action required for all instances in your farm. This indicates that your upgrade was successful for all of the PWA instances and corresponding databases.
PU Fix 13: Manage Database Upgrade Status dialog
Best Practice: msProjectExperts recommends as a best practice to follow any patches or updates with a system validation such as following the guidelines in Module 05: Verifying Project Server Functionality in Implementing and Administering Microsoft Project Server 2013 by Gary Chefetz & Bill Raymond.