Project Server 2010, 2013 and 2016 May 2016 PU Announcement


Yesterday saw the release of the May 2016 Public Update (PU) for Project Server 2010, 2013 and 2016.  The Project 2013 and 2016 client updates continued their new pattern this month – and this will be the same for all future months – and the Office client non-security updates released on the 1st Tuesday – May 3rd.  Any Office client security updates will still release on 2nd Tuesday.  We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential).  These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016, SP1 for 2013 and SP2 for 2010).

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below.  SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs!  This also means RTM is no longer supported!  See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don’t have the ‘right’ SP1.  Slipstream would work with the original SP1 – but the updates require the re-released SP1.  Since the May PU this shouldn’t be an issue – but including here just in case.

Another important point to add here is that there was in early 2013 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 May 2016 PU and then run the configuration wizard (if you didn’t already load the April 2013 through June 2014 CU).

This release for the 2010 products, like all 2010 patches since the November CU, has a hard requirement on Service Pack 2 – see notes below, (Support for Microsoft Office 2010 Service Pack 1 ended on 10/14/14).  Don’t forget language packs SP2 if you have any language packs loaded!  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 July PU will contain all previous CU releases (at least back to the applicable baseline).  Also worth noting that mainstream support for Project and Project Server 2010 ended October 13th 2015 – see https://support.microsoft.com/en-us/lifecycle

Also a reminder – an SP1 patched 2010 system (with no SP2) is no longer supported – see the Lifecycle site for more information – http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

Project 2016

An overview of all the Office 2016 releases for May 2016 can be found here – https://support.microsoft.com/en-us/kb/3158453 - May 10, 2016, update for Office (although as mentioned above – the client releases happened May 3rd.)

Project Server 2016

With the 2016 release we just have a single patch – as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though).

May 10, 2016, update for SharePoint Server 2016 (KB3115088) – (includes Project fixes, like the roll-up patch in Project Server 2013)

https://support.microsoft.com/en-us/kb/3115088

There is a database schema update this month – so the dbo.Versions table should now show 16.0.4378.1000 after applying the May 2016 PU.  Remember, Project Server 2016 data is in the content database.  The version number 16.0.4378.1000 can be used to control the connecting client to the May 2016 level.  For reference – the RTM build number seen for the DB schema would be 16.0.4327.1000.

Project 2016 Client Package:

May 3, 2016, update for Project 2016 (KB3115105)

https://support.microsoft.com/en-us/kb/3115105

The version of Project Professional 2016 will be updated to 16.0.4378.1000.  However, I have noticed that in 2016 we don’t do a good job of displaying the version and in File, Account, About Project we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe – in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the ‘16’ level then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area – Current Branch for Business is now called Deferred Channel. We are aware that we don’t appear to expose the full change details for Project and are looking into it.

Project and Project Server 2013

An overview of all the Office 2013 releases for May 2016 can be found here – https://support.microsoft.com/en-us/kb/3158453 - May 10, 2016, update for Office (although as mentioned above – the client releases happened May 3rd.)

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 May PUs from the following articles:

Project Server 2013 Server Rollup Package

May 2016 can be found here – https://support.microsoft.com/en-us/kb/3158453 - May 10, 2016, update for Office (although as mentioned above – the client releases happened May 3rd.)

May 10, 2016, cumulative update for Project Server 2013 (KB3115024)

https://support.microsoft.com/en-us/kb/3115024 

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

May 10, 2016, update for Project Server 2013 (KB3115036)

https://support.microsoft.com/en-us/kb/3115036

There is a database schema update this month – so the dbo.Versions table should now show 15.0.4819.1000 after applying the May 2016 PU.  The version number 15.0.4823.1000 can be used to control the connecting client to the May 2016 level, but only if you are loading the November 2014 CU or more recent to the server.  This version control no longer blocks server side scheduling engine since the November 2014 CU, but as this fix is server side you cannot use a higher value until you have this server patch or a more recent one.

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

Project 2013 Client Package:

May 3, 2016, update for Project 2013 (KB3115040)

https://support.microsoft.com/en-us/kb/3115040

The client version number will be 15.0.4823.1000.  The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.4823.1000 value to control connection of the May 2016 PU patched client..  If you are running a server CU earlier than November 2014 CU 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.  As mentioned above – the version number entered no longer controls the server side scheduling engine – so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

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.  Installations in Enterprise Environments that have been modified will be deployed based on the schedule determined by your Administrator.  See http://support2.microsoft.com/gp/office-2013-click-to-run.  You may also choose to update your click to run Project Pro for Office 365 to the new 2016 level – this can still connect to Project Server 2013 – see the 2016 section above for current version..

Project and Project Server 2010

An overview of all the Office 2010 releases for May 2016 can be found here – https://support.microsoft.com/en-us/kb/3158453 - May 10, 2016, update for Office (although as mentioned above – the client releases happened May 3rd.)

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 May PUs from the following articles:

Project Server 2010

NOTE: No individual Project Server 2010 package this month – the roll up doesn’t add anything new for Project Server 2010.

Project Server roll-up package

May 10, 2016, cumulative update for Project Server 2010 (KB3115122)

https://support.microsoft.com/en-us/kb/3115122

NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package).  This does however contain all the updates shipped up to the January update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch.

The Project Server database version does not get updated with the May 2016 PU – and will show – 14.0.7156.5000 – same as for the September 2015 update – after applying this  hotfix and running the configuration wizard.

Project 2010 Client Package:

May 3, 2016, update for Project 2010 (KB3115001)

https://support.microsoft.com/en-us/kb/3115001

The version of Project Professional 2010 will be updated to 14.0.7169.5000. 

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, the November 2014 Cumulative Update and above requires your client and server to already be at the Service Pack 1 (SP2) level – if you get a message saying the patch does not apply to your system then this may be the reason – the message may be “expected version of the product was not found”

SP2 for the Project Server 2010 can be found at Service Pack 2 for Microsoft SharePoint and Project Server 2010 (KB2687452) – and a description at SP2 at Description of Project Server 2010 SP2.  If you have language packs installed then these will also need to be patched to SP2 or the message above will be seen – SP2 for the server language packs can be found at Download the Microsoft Office Servers 2010 Language Pack Service Pack 2 package now and a description at http://support.microsoft.com/kb/2687462.

SP2 for the Project Professional 2010 client can be found at http://www.microsoft.com/en-us/download/details.aspx?id=39669 for the 32-bit and http://www.microsoft.com/en-us/download/details.aspx?id=39661 for the 64-bit and a description at http://support.microsoft.com/kb/2687457

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.

Or, from February 2015 onwards use Windows Update to download and install the patches.


Comments (6)

  1. Eric says:

    Brian, the “names” on the links are less than telling – really?
    it seems poorly labeled, but the 1st one is Project Server ONLY
    the code words “update for Project Server 2013” versus “cumulative update for Project Server 2013” does not really convey the difference.

    1. Hi Eric, I am just using the descriptions from the releases, so I have no control over that but can pass on that feedback. I try to show the difference by listing them under rollup package – or individual package. Would it make more sense for me to not use the name from the release but one that is more ‘telling’? Happy to change if it helps.
      Best regards,
      Brian.

  2. A Bauman says:

    Have there been any issues with this patch when trying to run SharePoint Configuration Wizard? The wizard runs successfully and cleanly on the central admin box, but continually fails on my second server. The upgrade, diagnostic, and uls logs have not provided any helpful information.

    1. A Bauman says:

      -Sorry – this is for the Project Server 2013 Updates

      1. Hi A Bauman – Not aware of any issues with the May update for Server 2013 – what was the error? It might ring some bells.
        Best regards,
        Brian

        1. A Bauman says:

          Unfortunately, the errors are very nondescript. “This upgrade session has been stopped. Possible causes include the process being terminated abruptly or the OS has rebooted. Please restart the upgrade again.” The logs only show the same message as in the configuration wizard: Sending a task driver stop event: TaskDriverEventArgs.EventCriticalityType error, TaskDriverEventArgs.EventType.stop, Configuration of SharePoint Products failed. Configuration must be performed before you use SharePoint Products. For further details, see the diagnostic log located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS\PSCDiagnostics_6_13_2016_10_54_56_432_379393058.log and the application event log.”

Skip to main content