Project Server 2013: March Public Updates

The February Cumulative Update that should have been released last month for Project Server 2013 and SharePoint Server 2013, was delayed due to some late breaking problems.  It was decided that due to the nature of these issues the best resolution was to release the planned fixes, along with the March Public Updates on Patch Tuesday, last week.  This applied to both the SharePoint and Project Server 2013 updates and all the associated technologies.  This also becomes the new baseline for all future updates – so you will need to install this patch before you could install, for example, the April 2013 CU.

*** Update 4/11 - see for details of an issue running the configuration wizard after applying the March PU ***

The following are the packages for the client and the server.  The client was released on time – just listing here again for completeness.  You can read about the fixes included in the Project and Project Server February CUs from the following articles:

Project 2013 Client Package: For Project Professional 2013 and Project Standard 2013

Description of the Project 2013 hotfix package (Project-x-none.msp): February 12, 2013

Project Server 2013 Package: Includes all updates for Project Server 2013 and SharePoint Server 2013

Description of the Project Server 2013 update: March 12, 2013

The deployment of the Server update is the same as for SharePoint 2013 and previous versions of Project Server.  The SharePoint article can be found at

Feel free to open a support incident at if you run into any issues with the installation and we will be happy to help!

Comments (4)

  1. Hello Brian, thanks for sharing this excellent information.

  2. anonymouscommenter says:

    Hi Brian,

    Just applied the update for one of our clients.

    Everything seems to be fine, configuration database verion has been updated to 15.0.4481.1005.

    However, checking under Upgrade and Migration > Review database status, the database called ProjectWebApp has the status of "Database is in compatibility range and upgrade is recommended."

    All other SharePoint related databases have the status of "No action required".

    I have already ran PSConfig twice.

    Can you please check if this is the same in your environments?

  3. anonymouscommenter says:

    Hi Vincent,

    I'm facing the same problem, can you tell me how you soved this problem?


  4. anonymouscommenter says:


    I solved the problem with :

    Upgrade-SPProjectdatabase -Name database -WebApplication http://WebApp

Skip to main content