- #MS PROJECT PROFESSIONAL HOW TO#
- #MS PROJECT PROFESSIONAL UPDATE#
- #MS PROJECT PROFESSIONAL PATCH#
- #MS PROJECT PROFESSIONAL SOFTWARE#
#MS PROJECT PROFESSIONAL PATCH#
That is little too old.Īs 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. You can see this pilot instance supports a minimum of .5000 version of MS Project Professional. PWA Additional Server Settings > Project Professional Versions Ms Project Professional versions prior to that number will not be able to connect with MS Project Server. 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. Microsoft Project Web Access (PWA) > Server Settings > Additional Server Settings link The settings are located in Project Web Access (PWA) > Server Settings > Additional Server Settings. 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.
#MS PROJECT PROFESSIONAL HOW TO#
MS Project Professional and MS Project Server versions compatibility from Softvative Inc How to Control Which version of MS Project Professional Can connect with MS Project Server EPM Softvative Infographics – Microsoft Project Professional and MS Project Server Editions Compatibility
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. 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. Not using the right version of MS Project Professional with the right version allowed by MS Project Server in PWA > Server Settings
I’ll also cover special case of this scenario. The focus of this article is about the last scenario. Not having enough permissions (a user with team member or lower rights trying to connect MS Project Professional to MS Project Server)Į. Not using the correct URL of Project Web Access (PWA)ĭ. Not using the right edition of MS Project Professional with the right edition of MS Project Server (2010 VS 2013)Ĭ. Not using the right edition of MS Project (Professional VS Standard)ī. There are different reasons as to why MS Project Professional can’t connect with MS Project Server EPM.Ī.
#MS PROJECT PROFESSIONAL UPDATE#
Service Pack or Cumulative Update (CU) patches if deployed without planning can cause issues in MS Project Server Enterprise Project Management (EPM) system.
#MS PROJECT PROFESSIONAL SOFTWARE#
The version of the server and client software should be at a supported level in order of the two to work together. Microsoft Project Professional edition is the desktop client in Microsoft Project Server (MSPS). Microsoft Project can’t Connect with Microsoft Project Server EPM due to Version Mismatch