Archive for the ‘ProjectOnline’ Category

SQL Query to Find Active Resources for Licensing

Monday, December 14th, 2015

SQL Query to Find Active Resources for Licensing

V: 1.2, MD: 01/24/2017

Following SQL query will show the list of users that are active, that connected to Project Web App (PWA) since specified date (Oct 1st, 2015 or the date you specify) and should be counted towards the licensing.

* Contact Softvative for accurate licensing assessment of your SharePoint or Project Server PPM farms. We have done Software Asset Management (SAM) projects for customers where we worked with the software vendors to save the licensing costs. We have skills in Microsoft MAP, System Center and other custom tools for the SAM.

Click here to download the SQL query file.

Replace the syntax with your Project Server database name.

 

 

Rename a Project in MS Project Server Part 5

Friday, January 30th, 2015

Rename a Project in Microsoft Project Server – Part 5

Version: 2.0

Applies to:
MS Project Server 2010
MS Project Server 2013
MS Project Online (Office 365)

This is the fifth and last part of the series to explain the details of different cases and how to best rename a project schedule in Microsoft Project Server EPM.

Table of Contents

1. Steps to rename a project using Project Web Access (PWA)
2. Steps to rename a project using MS Project Professional
3. Rename Project site
4. Scenarios: Renaming Project and different Statuses of Timesheets
5. Renamed Project Schedule and Business Intelligence Center Reports
Conclusion

 

Summary

Renaming a project in a MS Project Server EPM environment might require considerations for the OLAP data cube and the Business Intelligence (BI) Center reports.
 

5. Renamed Project Schedule and Business Intelligence Center Reports

We covered so far all the steps to rename project schedule in MS Project Server. The Business Intelligence (BI) Center reports out of SSAS OLAP Cube will show the old and new project name. It is best to select both project names for accurate EPM reporting.

Let’s look Project Web Access (PWA) > Business Intelligence (BI) timesheet reports.
As an example let’s pick one of the timesheet template. Go to PWA > Project BI Center > Templates Library on left> English (United States) folder > Server Name – OLAP Database Name folder > OlapTimesheet.xltx
The path of that file is something like this:
http://pwa.softvative.com/PWA/ProjectBICenter/Templates/English%20(United%20States)/SSAS_server_domain.com_instance%20-%20EPM_Project_Prod/OlapTimesheet.xltx
Click on the OlapTimesheet.xltx template file to open it in Microsoft Excel. First save the file to the root of your Template library using save option or to a place where you like to organize Project BI Reports. I saved it to following location
http://pwa.softvative.com/PWA/ProjectBICenter/Templates/
With Excel report still open, now choose the fields from the PivotTable Fields list on the right side. Create a timesheet report that will have Timesheet Project List in it.
 
Project Web Access - BI Center Excel Report - Choose PivotTable Fields
Project Web Access – BI Center Excel Report – Choose PivotTable Fields
 
Filter the project list and select only the project name. You will notice only the old project.
 
Project Web Access - BI Center Excel Report - EPM Timesheet Report before project renamed
Project Web Access – BI Center Excel Report – EPM Timesheet Report before project renamed
 
Close the OLAP Excel Report file.
Now enter hours under a different timesheet period and submit. Later process the PWA OLAP cube manually from Server Settings > OLAP Database Management. Highlight your OLAP Database name row (don’t click on cube name), then click on Build Now icon above. Once the cube builds successfully, launch your timesheet report again from the place where you saved it. Apply the filter on the project name and expand the row data. You will now notice the old and new project names there.
 
Project Web Access - BI Center Excel Report - EPM Timesheet Report after project renamed
Project Web Access – BI Center Excel Report – EPM Timesheet Report after project renamed
 
Here the linkto the sample cached excel report from the BI Center.

Conclusion

You can see renaming a project might look like a quick thing to do. But it requires careful steps to update name at different places. You miss a major step and you will see your users complaining about different issues:

  •  I don’t see my project anymore
  • My timesheet hours are lost
  • I can’t get my project SharePoint site
  • List goes on….
A better communication plan for the change and doing this change at non-peak hours is the recommended approach.

That finishes last part of this series. We covered the following topics in this series.

Keywords:

  • Renaming a project in Project Server
  • Renaming a project in Microsoft Project Server
  • Rename a project using MS Project
  • Rename a project using MS Project Professional
  • Rename a Project in Project Server
  • best practice to rename a project in Project Server
  • best practice to change a project name in Project Server
  • How to change a project name in Project Server
  • How To guide for renaming a project in Project Server
  • Primer on renaming a project in Project Server
  • Step by step guide to rename a project in project server
  • Edit Project details to rename a project
  • Rename a project schedule in Project Server
  • Rename a project plan in Project Server
  • How to rename projects in Project Server
  • How to rename a mpp file in Project Server
  • Renaming Projects
  • Project rename process
  • Project rename job aid



Visit www.softvative.com for professional services.

Rename a Project in MS Project Server Part 4

Friday, January 30th, 2015

Rename a Project in Microsoft Project Server – Part 4

Version: 2.0

Applies to:
MS Project Server 2010
MS Project Server 2013
MS Project Online (Office 365)

This is the fourth part of the series to explain the details of different cases and how to best rename a project schedule in Microsoft Project Server EPM.

Table of Contents

1. Steps to rename a project using Project Web Access (PWA)
2. Steps to rename a project using MS Project Professional
3. Rename Project site
4. Scenarios: Renaming Project and different Statuses of Timesheets
5. Renamed Project Schedule and Business Intelligence Center Reports
Conclusion

 

Summary

Renaming a project in a MS Project Server EPM environment might require team members to adjust their timesheets based on few conditions.
 

4. Scenarios: Renaming Project and different Statuses of Timesheets

There are few scenarios based on different statuses of timesheet in MS Project Server.

1. In progress timesheet
2. Approved timesheet (Submitted)
3. Period Closed timesheet
Below is the table that summarizes the conditions.
Timesheet Status Table
Timesheet Status
Description
Can Recall
Can Delete
Project Name
In Progress
Active timesheet created before rename
Yes
Old
Approved (Final)
Approved timesheet
Yes
Old
Period Closed (Final)
Timesheet period closed
No
No
Old
Not Yet Created
Not active yet
New
Note: In this scenario, we assume that users are listed as their own Timesheet Managers and so the submitted timesheets are auto-approved.
You can view status of a timesheet by going to Timesheet page and reviewing the bar above the timesheet grid area (below the ribbon).
 
Project Web Access TimeSheet - In Progress Timesheet
Project Web Access TimeSheet – In Progress Timesheet
 
Project Web Access TimeSheet - Approved Timesheet
Project Web Access TimeSheet – Approved Timesheet
 
New Project name will show up in new timesheets if you go to future or past timesheet periods that were not created at the time the project was renamed (those with status of ‘Not Yet Created’). Timesheets where the project’s tasks were not shown, once you add tasks using Insert Row > Insert Task, will also show the new project name.
You can review summary of timesheets by going to Manage Timesheets page under Settings section on left navigation.
 
Project Web Access Manage Timesheets Link
Project Web Access Manage Timesheets Link
 
Review the status column and you will find timesheets with either one of the three statuses.
Project Web Access Manage Timesheets Page
Project Web Access Manage Timesheets Page
• Clicking on ‘My Timesheet’ under timesheet column for a period will take you to that Timesheet’s page and will show the details.
• Highlighting the row by clicking any area on the row except ‘My Timesheet’ will activate the Recall or Delete icons on the top left ribbon area. Review the Timesheet Status Table listed above to see when you can recall or delete a timesheet based on timesheet status.
Timesheet Recall icon
Timesheet Recall icon
Timesheet Delete icon
Timesheet Delete icon

Exception 1: In Progress Timesheet previously created

Timesheets that were created prior to the project rename will still show the old project name.

Note:
In screen shots of this part you can notice, I renamed the project again before this part.

Project Web Access (PWA) - In Progress Timesheet showing old project name
Project Web Access (PWA) – In Progress Timesheet showing old project name
Resolution
1. Go to Manage Timesheets page, select the row for the timesheet and hit Delete icon on top left of ribbon to delete the In-Progress timesheet showing old project name.

Project Web Access (PWA) – Delete In Progress Timesheet

 

2. Now click over ‘Click to Create’ under Timesheet name to recreate the timesheet.
Project Web Access (PWA) - Create Timesheet
Project Web Access (PWA) – Create Timesheet

 

3. Once timesheet is created, you will be redirected to that timesheet. You can notice the new project name. Notice the previously saved hours are still intact.
Project Web Access (PWA) – Enter time in Timesheet under Project Tasks

Exception 2: Approved Timesheet previously created & Submitted

The timesheets that were approved prior to project rename will need to be recalled and deleted. Then recreate and resubmit the timesheets. Other than recall, the rest of the steps are the same as listed in exception 1 case.
Project Web Access (PWA) - Save and Submit Timesheet Got Approved
Project Web Access (PWA) – Save and Submit Timesheet Got Approved
Project Web Access (PWA) - Recall an Approved Timesheet
Project Web Access (PWA) – Recall an Approved Timesheet
That finishes third part of this series.
 
More on this and other scenarios is coming in next parts of this series. So far we have completed the three parts. Review the fourth part for timesheet related gotchas and remedies.
 


Keywords:

  • Renaming a project in Project Server
  • Renaming a project in Microsoft Project Server
  • Rename a project using MS Project
  • Rename a project using MS Project Professional
  • Rename a Project in Project Server
  • best practice to rename a project in Project Server
  • best practice to change a project name in Project Server
  • How to change a project name in Project Server
  • How To guide for renaming a project in Project Server
  • Primer on renaming a project in Project Server
  • Step by step guide to rename a project in project server
  • Edit Project details to rename a project
  • Rename a project schedule in Project Server
  • Rename a project plan in Project Server
  • How to rename projects in Project Server
  • How to rename a mpp file in Project Server
  • Renaming Projects
  • Project rename process
  • Project rename job aid



Visit www.softvative.com for professional services.

Rename a Project in MS Project Server Part 3

Friday, January 30th, 2015

Rename a Project in Microsoft Project Server – Part 3

Version: 2.1

Applies to:
MS Project Server 2010
MS Project Server 2013
MS Project Online (Office 365)

This is the third part of the series to explain the details of different cases and how to best rename a project schedule in Microsoft Project Server EPM.

Table of Contents


Summary

1. Steps to rename a project using Project Web Access (PWA)
2. Steps to rename a project using MS Project Professional
3. Rename Project site
4. Scenarios: Renaming Project and different Statuses of Timesheets
5. Renamed Project Schedule and Business Intelligence Center Reports
Conclusion

 

Summary

Renaming a project site in a MS Project Server EPM environment requires the following procedure.
 

3. Rename a Project Site

Renaming a project site is optional step. Even if you keep the old project site name, it will work and not break things. It is though good to have consistent naming across all places. The connection between a project schedule and project site is maintained by Project Server under Server Settings > Project Sites area. Renaming Project site has two steps:

a. Rename Project site’s Title and URL
b. Update the connection between Project schedule and Project site with new URL
 

a. Rename Project site’s Title and URL

To rename the project site follow the steps listed below.
1. Go to PWA > Project Center and locate your project
2. Select the project by clicking the first empty cell on left and then in the navigate ribbon group, click on Project Site
 
MS Project Web Access (PWA) - Select a Project and go to Project Site
MS Project Web Access (PWA) – Select a Project and go to Project Site


3. That will open your project site in new tab / window
4. Click on Site Actions > Site Settings on top left

MS Project Web Access (PWA) - Project Site > Site Settings
MS Project Web Access (PWA) – Project Site > Site Settings


5. Under Look and Feel section, click on ‘Title, description and icon’

MS Project Web Access (PWA) - Project Site > Site Settings > Look and Feel
MS Project Web Access (PWA) – Project Site > Site Settings > Look and Feel


6. Update the fields as needed:

Title and Description: to reflect the new name that will show up on the project site’s top left.
Web site Address: to update the URL address of the project site

MS Project Web Access (PWA) - Project Site > Site Settings > Title Description and Icon
MS Project Web Access (PWA) – Project Site > Site Settings > Title Description and Icon


7. Click OK to save your changes

b. Update the connection between Project schedule and Project site with new URL

Following the steps below. Without this step, the project site link will not work from Project Center and other places as it will be still be pointing to old project site URL. Users will get 404 not found error.

1. To update the connection URL between Project Schedule and Project Site, go to PWA > Server Settings
2. Click on Project Sites under Operations Policies section

MS Project Web Access (PWA) - Server Settings > Project Sites
MS Project Web Access (PWA) – Server Settings > Project Sites


3. Locate your project (using new name) in the list. Note the old URL still showing up even though the project schedule is showing the new name

MS Project Web Access (PWA) - Server Settings > Project Sites > Project showing old project name in URL
MS Project Web Access (PWA) – Server Settings > Project Sites > Project showing old project name in URL



4. Select the project by clicking on the row and then from top of the page click on ‘Edit Site Address’

MS Project Web Access (PWA) - Server Settings > Project Sites > Edit Site Address
MS Project Web Access (PWA) – Server Settings > Project Sites > Edit Site Address
5. In the Edit Site Address dialog box, update the URL address with new project site address (changed in section 3.a.6 above)


MS Project Web Access (PWA) - Server Settings > Project Sites > Edit Site Address Dialog box
MS Project Web Access (PWA) – Server Settings > Project Sites > Edit Site Address Dialog box


6. Click OK to any prompt and then locate the project on the page and verify the new site address

MS Project Web Access (PWA) - Server Settings > Project Sites > Edit Site Address Prompt for permissions
MS Project Web Access (PWA) – Server Settings > Project Sites > Edit Site Address Prompt for permissions
MS Project Web Access (PWA) - Server Settings > Project Sites > Project showing new project name in URL
MS Project Web Access (PWA) – Server Settings > Project Sites > Project showing new project name in URL


That finishes third part of this series.

More on this and other scenarios is coming in next parts of this series. So far we have completed the three parts. Review the fourth part for timesheet related gotchas and remedies.
 
 
Summary
 


Keywords:

  • Renaming a project in Project Server
  • Renaming a project in Microsoft Project Server
  • Rename a project using MS Project
  • Rename a project using MS Project Professional
  • Rename a Project in Project Server
  • best practice to rename a project in Project Server
  • best practice to change a project name in Project Server
  • How to change a project name in Project Server
  • How To guide for renaming a project in Project Server
  • Primer on renaming a project in Project Server
  • Step by step guide to rename a project in project server
  • Edit Project details to rename a project
  • Rename a project schedule in Project Server
  • Rename a project plan in Project Server
  • How to rename projects in Project Server
  • How to rename a mpp file in Project Server
  • Renaming Projects
  • Project rename process
  • Project rename job aid



Visit www.softvative.com for professional services.

Rename a Project in MS Project Server Part 2

Friday, January 30th, 2015

Rename a Project in Microsoft Project Server – Part 2

Version: 2.1

Applies to:
MS Project Server 2010
MS Project Server 2013
MS Project Online (Office 365)

This is the second part of the series to explain the details of different cases and how to best rename a project schedule in Microsoft Project Server EPM.

Table of Contents


Summary

1. Steps to rename a project using Project Web Access (PWA)
2. Steps to rename a project using MS Project Professional
3. Rename Project site
4. Scenarios: Renaming Project and different Statuses of Timesheets
5. Renamed Project Schedule and Business Intelligence Center Reports
Conclusion

Summary

Renaming a project using Microsoft Project Professional in a MS Project Server EPM environment requires the following procedure.

2. Steps to rename a project using MS Project Professional

To rename a project schedule, open the Microsoft Project Professional and make sure it is connected to MS Project Server.

1. Go to Filemenu and choose Open.

Microsoft Project Professional - File Open Dialog Box showing project from local cache
Microsoft Project Professional – File Open Dialog Box showing project from local cache
 
Tip: Notice in the screenshot that we renamed the EPM 2010 Rollout project in a previous step to EPM 2013 Rollout. But in the open dialog box it is still showing 2010 in the project name. That is due to local cache feature of MS Project Professional. Due to this reason, it is recommended that Project Managers publish their changes made in the project schedule using MS Project Professional before a project is renamed.
 
2. Click on the link ‘Retrieve the list of all projects from Project Server
3. Locate your project from the list and right click over it then choose Rename
Microsoft Project Professional - List of Projects - Right Click a project and choose Rename
Microsoft Project Professional – List of Projects – Right Click a project and choose Rename


4. Enter new name of project (append V2 in name as an example) and hit enter key. A message box will bring this message

The rename job was successfully submitted to server
Based on the server load, it may time some time for this to complete. You will continue to see the old name till the operation is completed.
Microsoft Project Professional - Project Renamed Confirmation Message
Microsoft Project Professional – Project Renamed Confirmation Message


5. Click OK to the message
6. Close the open dialog box and open it again. You will notice the new project name in the list.

Tip:
Notice in the Open dialog box that you are using the Working store. Select the Publishstore and locate your project in the list. You will notice that the old project name will still show in the list. What happened here?
In MS Project Server, there are multiple databases (stores) draft, published etc. Save and Publish operations update different tables in the system. To resolve the issue, you need to open the working store version of project and publish it.


Microsoft Project Professional - Previous Project name shows up in Published Store
Microsoft Project Professional – Previous Project name shows up in Published Store


7. Make sure your have Working selected under Store in the dialog box
8. Open the project (showing new project name) by double clicking on project name or by selecting it and clicking Open button at the bottom right

Microsoft Project Professional - Working Store showing new project name
Microsoft Project Professional – Working Store showing new project name

Tip:
If you get message regarding user submitted updates on the project, click No for now. You can approve those update later after the project is renamed. Update Center will show the new project name for the updates.

Microsoft Project Professional - Team Members submitted updates message
Microsoft Project Professional – Team Members submitted updates message


9. Go to File menu and choose Publish to publish the project data. That will update the new project name across all stores. (you can verify by going to file > open > ‘Retrieve the list of all projects from project server’ and then switching between working and published stores value and looking at the new project name)

Microsoft Project Professional - Publish Option
Microsoft Project Professional – Publish Option



10. Go to File > Close to close the project
11. Click Yes to any check-in message

More on this and other scenarios is coming in next parts of this series. So far we have completed the two parts. Review the third part to understand renaming the Project sites.
Summary

1. Steps to rename a project using Project Web Access (PWA)
2. Steps to rename a project using MS Project Professional

3. Rename Project site
4. Scenarios: Renaming Project and different Statuses of Timesheets
5. Renamed Project Schedule and Business Intelligence Center Reports
Conclusion

Keywords:

  • Renaming a project in Project Server
  • Renaming a project in Microsoft Project Server
  • Rename a project using MS Project
  • Rename a project using MS Project Professional
  • Rename a Project in Project Server
  • best practice to rename a project in Project Server
  • best practice to change a project name in Project Server
  • How to change a project name in Project Server
  • How To guide for renaming a project in Project Server
  • Primer on renaming a project in Project Server
  • Step by step guide to rename a project in project server
  • Edit Project details to rename a project
  • Rename a project schedule in Project Server
  • Rename a project plan in Project Server
  • How to rename projects in Project Server
  • How to rename a mpp file in Project Server
  • Renaming Projects
  • Project rename process
  • Project rename job aid
Visit www.softvative.com for professional services.

Rename a Project in MS Project Server Part 1

Thursday, January 29th, 2015

Rename a Project in Microsoft Project Server – Part 1

Version: 2.3

Applies to:
MS Project Server 2010
MS Project Server 2013
MS Project Online (Office 365)

When working on projects in a PMO environment using Enterprise Project Management (EPM) system like Microsoft Project Server, you come across situations where you might have to rename objects. Those rename item request could be for project, resource, tasks or other objects in the system.

MS Project Server has evolved as a mature EPM / PPM solution compared to its predecessor editions. In MS Project Server 2003 edition, we had to use other utilities to rename a project. Sometimes, special characters in project names used to cause so much trouble to the Cube build process.

These series of articles will explain the details of different cases and how to best rename a project schedule in Microsoft Project Server EPM.

Table of Contents

Summary

1. Steps to rename a project using Project Web Access (PWA)
2. Steps to rename a project using MS Project Professional
3. Rename Project site
4. Scenarios: Renaming Project and different Statuses of Timesheets
5. Renamed Project Schedule and Business Intelligence Center Reports
Conclusion

Summary

A project was created in Microsoft Project Server (MSPS) with a name. Later PMO / business teams wanted to change the name of the project.

1. Steps to Rename a Project using Project Web Access

Follow the steps below to rename a project using Project Web Access (PWA):

1. Go to PWA and click Project Center on left navigation

MS Project Web Access (PWA) - Project Center Link
MS Project Web Access (PWA) – Project Center Link

2. Find the project from the list that you would like to rename and then select a cell other than the project name in the row or click the first empty cell on the left of the row [Hint: Don’t click on the project name as it will bring the project details page]

Project Web Access PWA - Select the Project to Rename
Project Web Access PWA – Select the Project to Rename

3. Click on PROJECTS ribbon tab on top, Click on OPEN dropdown under Project ribbon group and select ‘In Project Web App for Editing’

Project Web Access PWA - Open Project in PWA for Editing
Project Web Access PWA – Open Project in PWA for Editing

4. On top area of left navigation, under project name, click on ‘Project Information’ or any PDP that has Name (that has project name) field in it.

Project Web Access PWA - Project Information PDP Page containing Name field
Project Web Access PWA – Project Information PDP Page containing Name field

5. Change the name of the project under NAME field
6. Click Save button in top left area of ribbon.
7. You will be presented with this message. Click OK to the following message:
“The page and left navigation titles will not be updated with the new name of the project until the page has been reloaded.”

Project Web Access PWA - Warning after Project Renamed in PWA
Project Web Access PWA – Warning after Project Renamed in PWA

You will see Save job message popping out from top right of screen.

Project Web Access PWA - Save Job Queued message
Project Web Access PWA – Save Job Queued message

then

Project Web Access PWA - Save completed successfully message
Project Web Access PWA – Save completed successfully message

At this point you can close the project and it will show the new name in PWA. I prefer to publish it just so that other database tables are updated as well.

8. Refresh the page to confirm the project has been renamed

Project Web Access PWA - Refresh the page to confirm the new project name on left nav
Project Web Access PWA – Refresh the page to confirm the new project name on left nav
9. Click on SCHEDULE link on top left
10. Under Schedule Tools > Tasks tab of ribbon, click on PUBLISH.
Project Web Access PWA - Go to Schedule PDP page and Publish the Project
Project Web Access PWA – Go to Schedule PDP page and Publish the Project
11. Watch for message popping from the top right with status message:
   a. Processing
   b. Save job queued
   c. Publish completed successfully
12. Once the Publish operation is complete, click on PROJECT ribbon tab on top
13. Click Close button
Project Web Access PWA - Close the Project in PWA
Project Web Access PWA – Close the Project in PWA
14. You will be presented with the Check-in message. Click Yes
Project Web Access PWA - Check in project in PWA
Project Web Access PWA – Check in project in PWA

Exceptions:

The TASKS page for team members will show the new project name. But the TIMESHEET page will show the old project name, if the timesheet was created prior to project rename. In that case delete / recall and create the timesheet again. It will then show the new project name.
More on this and other scenarios is coming in next parts of this series. So far we have completed the first part. Stay tuned for the second part.
Summary
1. Steps to rename a project using Project Web Access (PWA)
2. Steps to rename a project using MS Project Professional
3. Rename Project site
4. Scenarios: Renaming Project and different Statuses of Timesheets
5. Renamed Project Schedule and Business Intelligence Center Reports
Conclusion


References:
1. Back to Basics: Renaming a Project correctly in Project Server 2013


Keywords:

  • Renaming a project in Project Server
  • Renaming a project in Microsoft Project Server
  • Rename a Project in Project Server
  • best practice to rename a project in Project Server
  • best practice to change a project name in Project Server
  • How to change a project name in Project Server
  • How To guide for renaming a project in Project Server
  • Primer on renaming a project in Project Server
  • Step by step guide to rename a project in project server
  • Edit Project details to rename a project
  • Rename a project schedule in Project Server
  • Rename a project plan in Project Server
  • How to rename projects in Project Server
  • How to rename a mpp file in Project Server
  • Renaming Projects
  • Project rename process
  • Project rename job aid
Visit www.softvative.com for professional services.

MS Project cant Connect with MSPS MSProjectServer

Friday, December 26th, 2014

Microsoft Project can’t Connect with Microsoft Project Server EPM due to Version Mismatch

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.

There are different reasons as to why MS Project Professional can’t connect with MS Project Server EPM.

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.

e. Not using the right version of MS Project Professional with the right version allowed by MS Project Server in PWA > Server Settings

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.

Which MS Project Professional product can connect with which MS Project Server product

The short summary is:

  • MS Project Professional 2010 can only connect with MS Project Server 2010
  • MS Project Professional 2013 can connect with MS Project Server 2013 & MS Project Online
  • MS Project Standard can’t connect with MS Project Server.
Softvative Infographics - Microsoft Project Professional and MS Project Server Editions Compatibility
Softvative Infographics – Microsoft Project Professional and MS Project Server Editions Compatibility

Review the Infographic slides:

How to Control Which version of MS Project Professional Can connect with MS Project Server EPM

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
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
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.

Special Case Scenario due to version mismatch

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 Error - The following job failed to complete Error ID 12015
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
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.

Issue Cause

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.

Resolution

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.

References:

  1. Project Server 2013: Controlling the version of connecting clients–and PWA edits?
  2. How do I know???? Project Professional Versions and Consistency

Keywords:

  • MS Project can’t connect with Project Server
  • MS Project can’t connect with Project Online
  • MS Project can’t connect with PWA
  • Microsoft Project can’t connect with Project Server
  • MS Project can’t connect with Microsoft Project Server
  • Microsoft Project Professional can’t connect with Project Server
  • Microsoft Project Professional supported versions for Project Server
  • Microsoft Project Professional version inconsistencies with Project Server
  • Can not use MS Project with Project Server
  • Can not use MS Project with PWA
Visit www.softvative.com for professional services.