Microsoft Project Server 2010 and 2013 September 2014 CU Announcement


I am very pleased to announce the release of the September 2014 Cumulative Update (CU) for Project, Project Server and SharePoint for 2013, and Project and Project Server and SharePoint 2010.  Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

For a discussion of the September CU, as well as the July and August fixes, see the webcast recording at https://www.youtube.com/watch?v=VZTgYXwu0GE&feature=youtu.be&list=PL_BmUqQrmneZHJoQ3Lfll77nfG09g8Cp9 

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 August CU will contain all previous CU releases (at least back to the applicable baseline Service Pack (the respective SP1’s for both 2010 and 2013).  The August CU for Project and Project Server 2013 does not include fixes that were included in SP1 – hence the requirement to have SP1 installed first..

Another important point to add here is that there was an issue early last year running the SharePoint Configuration Wizard on a server with Project Server 2013 installed – this is fixed by applying the April 2013 or later– so a good practice would be to load SP1, then the September 2014 CU and then run the configuration wizard (if you didn’t already load the April 2013 through June 2014 CU).

The September 2014 CU for Microsoft Project 2010, can be installed with Microsoft Project 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

An overview of all the Office 2013 releases for September 2014 can be found here – http://support.microsoft.com/kb/2995905Office 2013 cumulative update for September 2014

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 September CUs from the following articles:

Project Server 2013 Server Rollup Package

September 9, 2014 Cumulative Update for Project Server 2013 package

http://support.microsoft.com/kb/2883072

Again, like previous complete packages (although we didn’t have one last month), this package contains three files to download.  All need to be extracted to the same location which will give you one exe and 2 cab files – this makes up the ‘uber’ package that contains Project and SharePoint Server fixes.  If you get “The installation of this package failed” then ensure you downloaded and extracted all three files to the same location before running the exe.

Project Server 2013 Individual Project Package – (cumulative, but only the Project Server fixes):

Hotfix KB2889856 for Project Server 2013 September 9, 2014 (Projectserverwfe-x-none.msp; Projectservermui-<Language-Code>.msp)

http://support.microsoft.com/kb/2889856

The dbo.Versions table should show 15.0.4649.1001 after applying the September 2014 CU.  The version number 15.0.4649.1000 can be used to control the connecting client to the September 2014 level, but only if you are loading the September CU to the server and client.  This version relates to the server side scheduling engine and can be different from the database level.

SP1 for Project Server 2013 can be hound here – http://support.microsoft.com/kb/2880553

Project 2013 Client Package:

Hotfix KB2889883 for Project 2013 September 9, 2014 (Project-x-none.msp)

http://support.microsoft.com/kb/2889883

The client version number will be 15.0.4649.1000 and as this matches the server scheduling engine version this can be used if you want to restrict the client version that can connect to the server – assuming of course that you have upgraded the server to the September CU too.  If not then follow the suggested version number for the server patch level you are running.  See Project Server 2013- Controlling the version of connecting clients–and PWA edits- for more details.

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.

SP1 for Project Professional 2013 can be found here – http://support.microsoft.com/kb/2817433

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.

Project and Project Server 2010

An overview of all the Office 2010 releases for August 2014 can be found here – http://support.microsoft.com/kb/2995904  – Office 2010 cumulative update for September 2014

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 August CUs from the following articles:

Project Server 2010 Package

September 9, 2014 Cumulative Update for Project Server 2010 package

http://support.microsoft.com/kb/2883006

Project Server 2010 Individual package (cumulative – but just the Project Server 2010 fixes)

Hotfix KB2880531 for Project Server 2010 September 9, 2014 (Pjsrvwfe-x-none.msp)

http://support.microsoft.com/kb/2880531

The Project Server database version will be updated to 14.0.7132.5000 after applying this or the package hotfix above, and running the configuration wizard.

Project 2010 Client Package:

Hotfix KB2889911 for Project 2010 September 9, 2014 (Project-x-none.msp)

http://support.microsoft.com/kb/2889911

The client version number is 14.0.7131.5000, in case you want to limit the connection of certain patched release to Project Server 2010.

More information on deploying the Cumulative Update:

The article below provides information on how to deploy the Project Server Cumulative Update.

Updates for Project Server 2010 http://technet.microsoft.com/en-us/projectserver/gg176680.aspx

As Project Server 2010 is now based on SharePoint Server 2010 we strongly recommend that you install the Project Server 2010 Server Rollup Package (when available) 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.

Client Installation:

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.

Comments (2)

  1. Kevin Dostalek says:

    Installed the Project 2010 (with SharePoint 2010) Sept. 2014 CU on a server that was at SP2. SharePoint seems to have upgraded fine, but we are getting the following error with it upgrading the Project Server DB. Any ideas or is this a unique situation?
    ("An error occurred during decryption")

    [PSCONFIG] [SPUpgradeSession] [INFO] [12/8/2014 12:03:11 AM]: ProjectDatabase Name=ProjectServer_Published
    [PSCONFIG] [SPUpgradeSession] [ERROR] [12/8/2014 12:03:11 AM]: Upgrade [ProjectDatabase Name=ProjectServer_Published] failed.
    [PSCONFIG] [SPUpgradeSession] [INFO] [12/8/2014 12:03:11 AM]: ProjectDatabase Name=ProjectServer_Published
    [PSCONFIG] [SPUpgradeSession] [ERROR] [12/8/2014 12:03:11 AM]: Exception: An error occurred during decryption.
    [PSCONFIG] [SPUpgradeSession] [INFO] [12/8/2014 12:03:11 AM]: ProjectDatabase Name=ProjectServer_Published
    [PSCONFIG] [SPUpgradeSession] [ERROR] [12/8/2014 12:03:11 AM]: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
    at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
    at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
    at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
    at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
    at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
    at Microsoft.Office.Project.Server.Data.SqlSession.ExecuteScript(TextReader textReader, Int32 commandTimeout)
    at Microsoft.Office.Project.Server.Data.SqlSession.ExecuteScript(String path, Int32 commandTimeout)
    at Microsoft.Office.Project.Server.Upgrade.ProjectDatabaseSequence.ExecuteSqlScripts(String[] sqlFiles)
    at Microsoft.Office.Project.Server.Upgrade.ProjectDatabaseSequence.CreateSqlObjects()
    at Microsoft.Office.Project.Server.Upgrade.ProjectDatabaseSequence.PostUpgrade()
    at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)

  2. anonymouscommenter says:

    Hi Brian,
    We noticed that CU September was now synchronizing permissions on the Visitor groups of the project sites. I did not notice this new "feature" was documented (reason explained upon our Premier Support ticket was to give a full control to the Project Manager).
    Any plan to remove this sync ?

    Bye Brian
    Jeff, from STMicro 🙂

Skip to main content