Version: 1.2, Modified: 12/29/2014
Microsoft Project Professional edition is the desktop client in Microsoft Project Server (MSPS). The version of the server and client software should be at a supported level in order of the two to work together. Service Pack or Cumulative Update (CU) patches if deployed without planning can cause issues in MS Project Server Enterprise Project Management (EPM) system.
Below are some of the scenarios:
a. Not using the right edition of MS Project (Professional VS Standard)
b. Not using the right edition of MS Project Professional with the right edition of MS Project Server (2010 VS 2013)
c. Not using the correct URL of Project Web Access (PWA)
d. Not having enough permissions (a user with team member or lower rights trying to connect MS Project Professional to MS Project Server)
e. Not using the right version of MS Project Professional with the right version allowed by MS Project Server in PWA > Server Settings
The focus of this article is about the last scenario. I’ll also cover special case of this scenario.
There are known issue if your MS Project Server (MSPS) is at latest patch version and your desktop MS Project Professional edition used it too old.
MS Project Server 2010 / 2013 / Project Online circumvent this problem by allowing the Project Server Admins / PMO Admins / PMO Analysts to set limit on the least version of MS Project Professional that can connect with the Project Server.
The short summary is:
|Softvative Infographics – Microsoft Project Professional and MS Project Server Editions Compatibility|
Review the Infographic slides:
Microsoft Project Server 2010 / 2013 has the configuration setting that allows you to control which version of MS Project Professional within the same edition (2010 or 2013) can connect with the MS Project Server.
The settings are located in Project Web Access (PWA) > Server Settings > Additional Server Settings.
|Microsoft Project Web Access (PWA) > Server Settings > Additional Server Settings link|
On that ‘Additional Server Settings’ page there is a setting to set the minimum version number of MS Project Professional that can connect with that instance of the MS Project Server EPM. Ms Project Professional versions prior to that number will not be able to connect with MS Project Server.
|PWA Additional Server Settings > Project Professional Versions|
You can see this pilot instance supports a minimum of 14.0.6123.5000 version of MS Project Professional. That version is dated back to June 2012. That is little too old.
As per ITIL best practices for Configuration Management and Problem Management and also as per Information Security’s Patch Management Life cycle, the application versions should be maintained at the best possible levels. Even from Information Risk Management prospective, sometimes supporting too old version means also keeping old vulnerabilities alive in your new system. There is lot more to talk about on these best practices related to this topic. But that is little out of scope at this time for the topic.
I’ve seen a special case where a Project Manager was not able to connect to MS Project Server with everything correct as per the scenarios discussed at the beginning of this article.
The PM was getting the error listed below when launching MS Project Professional using connection with MS Project Server.
The following job failed to complete.
Job Type: Load
Error ID: 12015 (0x2EEF)
Error Description: An internal error occurred.
Cloud not load Project. Please try after some time. If the problem persists, contact your system administrator.
|MS Project can not connect with Project Server – Error ID 12015|
Clicking more Info button reveals more details. You can see the version that is passed on to the PWA is not the right one.
|MS Project can not connect with Project Server – Error ID 12015 – More Info|
Click OK to the first error message brings the second error:
Cloud not retrieve Enterprise global template.
There seems to be a problem with the database, please contact your server administrator.
I verified that the MS Project Professional version was new relatively i.e. 14.0.7015.1000. That was higher than the minimum supported version configured in PWA.
Looking at the File > Help in MS Project Professional and reviewing the version screen in a large print out, I was able to find an anomaly. See the above screen shot again. It shows that MS Project Standard and MS Project Professional both as activated versions!
It turned out to be the Desktop Engineering person deployed MS Project Standard version first by mistake (& without any service packs or updates). Later he installed MS Project Professional over the same version as upgrade rather than removing the standard version. Now when the PM was trying to connect to MS Project Server using Ms Project Professional, somehow the desktop was passing the lower version 14.0.4751.1000 (see one of the screen shot above) and thus PWA was rejecting the connection.
Uninstall any version of Microsoft Project from the desktop, reboot and then install the correct version of MS Project Professional with the the latest service pack and CU level as supported by the organization.
Revo Uninstaller – Free version is one nice 3rd party application (Pro Version) to remove the stubborn applications. That helped in getting rid of the old version completely and then installing the MS Project Professional version again.
The correct version once installed and activated should only show MS Project Professional under File > Help.
MS Project Professional was able to connect with the Project Server.