Microsoft Project Support Blog

The place to come for Microsoft Project, Microsoft Project Server and Project Online support topics

Project Server 2013: Controlling the version of connecting clients–and PWA edits?

Project Server 2013: Controlling the version of connecting clients–and PWA edits?

  • Comments 3
  • Likes

Since Project Server 2010 it has been possible to control which patch level of Project Professional is allowed to connect to Project Server by referencing the Version in Server Settings.  This is configured in Server Settings, Additional Server Settings, and in Project Server 2013 this is one of the settings that is accessed via SharePoint C2013 Central Administration, General Application Settings, PWA Settings, Manage – and then under Additional Server Settings (and don’t forget to set the right Project Web App Instance if you have more than one).  So for example I might set the value to 15.0.4535.1000 – the version of the August 2013 Cumulative for Project Professional 2013.  But I might not…

image

If I then try to connect with a lower version of Project I get an error – The following job failed to complete.  Job Type: Load, Error ID: 12015(0x2EEF), Error: An internal error occurred – and I opened the More Info section and scrolled down to see the interesting stuff - name="ActiveCacheUnsupportedProjectProfessionalVersion" uid="53cf724e-f01e-e311-9415-00155d745a02" version="15.0.4517.1001"/.

image

So what’s the problem?  Seems to work?  What if I try and edit a plan in PWA?

Strange.  The plan doesn’t load, and you might also see other PDPs than the schedule also fail to load – *** additional info - 12/12/2013 - if you have script errors I.E. not disabled then you will also see an error something like

Webpage error details

Message: Unable to get property 'replace' of undefined or null reference
Line: 2
Char: 16751
Code: 0
URI: http://<servername>/_layouts/15/inc/pwa/library/shell.js?rev=VV59QN4O%2FYo%2BkyvfjP7EPg%3D%3D

***

If you look in the ULS logs you willI see something like the following:

09/16/2013 10:19:09.93    Microsoft.Office.Project.Server (0x3548)    0x0590    Project Server    Active Cache Load    3oh1    Medium    Error is: ActiveCacheUnsupportedProjectProfessionalVersion. Details: ActiveCacheUnsupportedProjectProfessionalVersion Attributes:  15.0.4525.1000  . Standard Information:  Project:73f0a279-f31e-e311-be99-f4b7e2e8268f Project:75cdd7db-1b68-4b70-a8d6-2fe52da83acd    549f439c-1222-a04c-45e7-ac3fd79c7a5a

09/16/2013 10:19:09.93    Microsoft.Office.Project.Server (0x3548)    0x0590    Project Server    Project Calculation Service (M)    ai2no    Unexpected    PWA:, ServiceApp:Project Server Service Application, User:i:0#.w|redmond\brismith, PSI: CalcServiceManager can't read PreReadProject2 for projectGuid 75cdd7db-1b68-4b70-a8d6-2fe52da83acd. Project:73f0a279-f31e-e311-be99-f4b7e2e8268f Project:75cdd7db-1b68-4b70-a8d6-2fe52da83acd    549f439c-1222-a04c-45e7-ac3fd79c7a5a

09/16/2013 10:19:09.95    Microsoft.Office.Project.Server (0x3548)    0x0590    Project Server    Project Calculation Service (M)    ai2mv    Exception    CalcServiceManager : Processing Error while opening project guid: 73f0a279-f31e-e311-be99-f4b7e2e8268f Microsoft.Office.Project.Server.BusinessLayer.PcsEngine.PcsManagerException: CalcServiceManager : ReadProjectData : CalcServiceManager can't read PreReadProject2     at Microsoft.Office.Project.Server.BusinessLayer.CalcServiceManager.ReadProjectData(IPlatformContext siteContext, WinProj winprojActiveCache, Guid ProjectGuid, Guid sessionGuid, UInt32 flags, Int32 lcid, String versionStamp, Boolean fNonCoreData, Boolean fEglobal, Boolean keepWriteLock, Byte[]& coreData, Byte[]& noncoreData, PSError psError)     at Microsoft.Office.Project.Server.BusinessLayer.CalcServiceManager.LoadProjectData(IPlatformContext siteContext, Guid projectGuid, WinProj winprojActiveCache, Guid globalGuid, Int32 lcid, IPCSPipe pipe, Guid sessionGuid, String oldVersion, String globalOldVersion, Boolean keepWriteLock, PSError psError)     at Microsoft.Office.Project.Server.BusinessLayer.CalcServiceManager.OpenProjectRemappedProject(CalcServiceCallState callState, Guid realProjectGuid, Guid remappedProjectGuid, EngineSessionState& sessionState, EngineSessionType sessionType, PSError& psError) StackTrace:  at Microsoft.Office.Project.Server.Native.dll: (sig=9f2c3f6c-406e-4293-ab26-21dadb9504de|2|microsoft.office.project.server.native.pdb, offset=3C1E) at Microsoft.Office.Project.Server.Native.dll: (offset=1255D)    549f439c-1222-a04c-45e7-ac3fd79c7a5a

You may see a different version reported there – depending on the server patch level.  This is with the August CU for Project Server 2013.

*** Update 10/15/2013 - The October 2013 CU does not give this issue if the Server and Client are both patched to Oct 2013 then the version reported by client and server is the same - 15.0.4551.1001 - obviously if the server isn't patched then trying to control the client to Oct CU will also limit the ability to edit plans in the Schedule Web Part in PWA. ***

That’s the reason I might not want to set the Project Professional version.  This issue in 2013 is due to the change in the server-side scheduling engine infrastructure.  In Project Server 2013 we now use the same scheduling engine as Project Professional in the server – which has many great benefits – but one side effect that I hadn’t considered.  When you open a plan for editing in PWA the server-side scheduling engine reports its version number – and if you are controlling the connected patch level as detailed above then you will get this failure to read the project.  The reason the server-side calculation engine may report a different version is that although this is the same scheduling engine – Project Professional may be patched for features that are not related to scheduling – such as printing issue for example – so its version can be different to the server scheduling engine.

In this case you could safely set the version to 15.0.4525.1000 and this would then only allow the August CU patched clients (as June CU was below this value) and PWA editing would work just fine.  We are reviewing this issue as a bug as there could be conditions where you want to control a client patch level yet your server may still be at an earlier level – if you are in this situation I would suggest opening a support incident.

Thanks to Hans Bellen of UMT for bringing this to our attention.

Comments
  • Hi Brian,

    Additional information... after October 13 CU... a PWA-originated new schedule (default EPT with 5 simple tasks with Baseline data) will NOT appear within the on-premise OLAP cube... it seems the time-phased data never gets into the Reporting database even after proper Publish within PWA... if you open the PWA-originated schedule in Pro and republish... the time-phased data shows in Pro Usage views ... but is still missing in the OLAP data...

    However... if you open PWA-originated schedule in Pro... then Save As new + publish... all of that data shows up in the OLAP cube as expected....

    I suspect some form of server-side scheduling engine problem within October 13 CU...

  • Thanks much for the input.  Do you know of a link providing each/all Microsoft Project Professional 2013 CU with their correspoding level?

    Aug-2013 = 15.0.4551.1001

    Oct-2013 = ?

    Dec-2013 = ?

    etc.

  • Good day
    We start new with Project Server 2013. All the PM can access MSP except for the one
    All of them are loaded in the same Group - they have the same type of access

    His 1st message is: Same as the one posted by Brian Brian on the 16 Sept 2013

    When he click on Ok

    His 2nd message says: Could not retrieve Enterprise Global Template. There seems to be a problem with the database, please contact your server administator

    I removed the account for MSP and add it back again without any luck

    I also cannot open it on his Computer as it also give me the same message

    As we are not in the same office and i need to travel to him to assist i send him a mail that i can view what version of MSP is loaded to his PC

    Could it be that MSP Profesional 2013 is not loaded?
    or
    Could it be that MSP Profesional 2010 that used to be in our Comp is loaded back

    Adri

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment