Project and Project Server 2010 and 2013 November 2014 CU release


I posted the November 2014 Cumulative Update (CU) release announcement for Project and Project Server 2010 and Project and Project Server 2013 over on the ProjectSupport blog at Microsoft Project Server 2010 and 2013 November 2014 CU Announcement.  At the time of posting a few of the KB articles were not published – so just a reminder if you can’t wait – you can always go direct to a download using the KB number in a link such as http://support2.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2899569&kbln=en-us (this is the Project 2013 client update – KB 2899569).

Also a reminder – SP2 is now required the required baseline for Project 2010 and Project Server 2010 before loading the November CU.  This not only applies to the Project Server 2010 SP2 (which can be found here – http://support.microsoft.com/kb/2687452 – server, and here http://support.microsoft.com/kb/2687457 – client) but also for any language packs you may have installed.  Language packs are sometimes referred to as MUI (multi-lingual user interface).  This caught me out, as I installed the individual server fix KB2899537 with no problems, but found that the localized package KB28999549 gave me an error – ‘The expected version of the product was not found on the system.’  After reviewing the logs I could see that the issue was my language packs.  An excerpt on the logs follows to help understand what the cryptic message means (this is near the end of the log):

OPatchInstall: Property ‘PJSRVMUI-AR-SA’ value ‘InvalidBaseline’
OPatchInstall: Property ‘PJSRVMUI-CS-CZ’ value ‘NoShow’
OPatchInstall: Property ‘PJSRVMUI-DA-DK’ value ‘InvalidBaseline’
OPatchInstall: Property ‘PJSRVMUI-DE-DE’ value ‘InvalidBaseline’
OPatchInstall: Property ‘PJSRVMUI-EL-GR’ value ‘InvalidBaseline’
OPatchInstall: Property ‘PJSRVMUI-EN-US’ value ‘NotInstalled’
OPatchInstall: Property ‘PJSRVMUI-ES-ES’ value ‘InvalidBaseline’
OPatchInstall: Property ‘PJSRVMUI-FI-FI’ value ‘NoShow’
OPatchInstall: Property ‘PJSRVMUI-FR-FR’ value ‘NotInstalled’
OPatchInstall: Property ‘PJSRVMUI-HE-IL’ value ‘InvalidBaseline’
OPatchInstall: Property ‘PJSRVMUI-HU-HU’ value ‘NoShow’
OPatchInstall: Property ‘PJSRVMUI-IT-IT’ value ‘NoShow’
OPatchInstall: Property ‘PJSRVMUI-JA-JP’ value ‘InvalidBaseline’
OPatchInstall: Property ‘PJSRVMUI-KO-KR’ value ‘InvalidBaseline’
OPatchInstall: Property ‘PJSRVMUI-NB-NO’ value ‘NoShow’
OPatchInstall: Property ‘PJSRVMUI-NL-NL’ value ‘NoShow’
OPatchInstall: Property ‘PJSRVMUI-PL-PL’ value ‘NoShow’
OPatchInstall: Property ‘PJSRVMUI-PT-BR’ value ‘InvalidBaseline’
OPatchInstall: Property ‘PJSRVMUI-PT-PT’ value ‘InvalidBaseline’
OPatchInstall: Property ‘PJSRVMUI-RU-RU’ value ‘InvalidBaseline’
OPatchInstall: Property ‘PJSRVMUI-SK-SK’ value ‘NoShow’
OPatchInstall: Property ‘PJSRVMUI-SL-SI’ value ‘NoShow’
OPatchInstall: Property ‘PJSRVMUI-SV-SE’ value ‘NoShow’
OPatchInstall: Property ‘PJSRVMUI-TR-TR’ value ‘NoShow’
OPatchInstall: Property ‘PJSRVMUI-UK-UA’ value ‘NoShow’
OPatchInstall: Property ‘PJSRVMUI-ZH-CN’ value ‘InvalidBaseline’
OPatchInstall: Property ‘PJSRVMUI-ZH-TW’ value ‘InvalidBaseline’
OPatchInstall: Property ‘PJSRVWFE-X-NONE’ value ‘Installed’

As you can see, this list all of the languages that will get updated by the localized patch.  The problem ones are the rows that show as InvalidBaseline.  For these I needed to get the SP2 of each of the Language packs from http://www.microsoft.com/en-us/download/details.aspx?id=39675.  I had quite a few of these to update!  NoShow means the language isn’t installed so doesn’t need patching. NotInstalled means the language is there at the correct baseline and will be installed (See FR_FR and EN_US above), and Installed means it is already installed (in this case PJSVRWFE-X_NONE was installed from the individual non-localized package).  One issue I did find is that the Arabic language pack was not listed (AR-SA) so instead I uninstalled the language back so that it did not need to be patched.  If anyone needs that pack I’ll try and find out why it is not present.

Hope someone else finds this is useful – I can’t believe I’ll be the only one running into this.

Comments (4)

  1. Tim Howells says:

    Hi Brian,

    Do you know if/when Project Server 2013 will be officially supported with DBs and SSAS on SQL 2014?  TechNet planning docs last updated July 2014 and still state SQL 2014 is not supported although SharePoint 2013 planning docs state it is supported with May 2014 CU.

    thanks,

    Tim

  2. TimHowells says:

    Hi Brian,

    Is Project Server 2013 supported with SQL 2014 DB and SSAS now?  The Project Server 2013 TechNet planning guide still says SQL 2014 is  unsupported while the SharePoint 2013 planning guide says SQL 2014 is supported with SharePoint 2013 and the May 2014 CU applied.

    thanks,

    Tim

  3. It is supported from SP1 Tim, we are working on getting our documentation updated accordingly.

    Best regards,

    Brian.

  4. TimHowells says:

    Excellent, thanks for the quick reply.

    Tim

Skip to main content