Archive for the ‘ProjectServer’ Category

Database is up to date, but some sites are not completely upgraded

Saturday, April 2nd, 2016

Database is up to date, but some sites are not completely upgraded

Version: 1.0, Updated 03/22/2016

Applies to: SharePoint and Project Server PPM 2010, 2013, 2016

Scenario:

You review the SharePoint Central Administration site for Servers and database statuses and notice below messages:

Server Status: Upgrade Required

Central Admin Site > System Settings > Manage servers in this farm

SP2013_SomeSiteNotUpgraded_01A

 

Database Status: Database is up to date, but some sites are not completely upgraded

Cental Admin Site > Upgrade and Migration > Review Database Status.

SP2013_SomeSiteNotUpgraded_01b

 

Resolution:

First lets try to find out which site is causing that error.

  1. On one of the SharePoint / Project Server PPM server, open command prompt with elevated permissions.
  2. Go to SharePoint Bin folder c:\Program Files\Microsoft Shared\Web Server Extensions\15\Bin\ [the two digit folder name for SharePoint 2010 = 14, 2013 = 15, 2016 = 16]
  3. Type STSAdm command and use pipe to export it to a text file: stsadm.exe -o localupgradestatus > e:\UpgradeStatus.txt  SP2013_SomeSiteNotUpgraded_02 
  4. After executing the command, open the UpgradeSTatus.txt file exported in previous step. Search the text file for the status Needs Upgrade. Those sections will list the site name in question. You can see in the image below that the site name is listed.SP2013_SomeSiteNotUpgraded_03
  5. Go to the bottom of this UpgradeStatus.txt file and you will see overall status of content database(s), Site collection(s) or objects that may need upgrade.SP2013_SomeSiteNotUpgraded_04
  6. In Review Database Status page we saw the name of database(s) that had the status with the error message (second image on the top). Open PowerShell with elevated rights and run the following commands: Get-SPContentDatabase -Identity wss_epm_content [where wss_epm_content is the name of the content database]. That will give us the database ID that we’ll use in next command to upgrade the database.SP2013_SomeSiteNotUpgraded_05
  7. Now run the PowerShell command: Upgrade-SPContentDatabase -Identity GUID# [where GUID# is the ID we got from previous step]. Click Y or A to confirm the command execution. SP2013_SomeSiteNotUpgraded_06
  8. Now go to Manage Servers in the Farm and Review Database Status pages and check the status. The Servers page will still show ‘Upgrade Required’ status. The database page will not show error this time and instead will show ‘No Action Required’ message. SP2013_SomeSiteNotUpgraded_07  SP2013_SomeSiteNotUpgraded_08
  9. Run the stsadm command again and export the status with a new file name UpgradeStatus2.txt. stsadm.exe -o localupgradestatus > e:\UpgradeStatus2.txt. Review the file after command executes and you will find that none of the database, site Collection or object need upgrade this time. SP2013_SomeSiteNotUpgraded_09
  10. At this point, run either the SharePoint Configuration Wizard GUI or run the command line option. SP2013_SomeSiteNotUpgraded_10 Run the PowerShell command on each server in the farm one at a time. PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresourcesSP2013_SomeSiteNotUpgraded_11
  11. After executing the command on all servers, go to the Central Admin site and review the status of servers in the farm. All the servers should have ‘No Action Required’ as the status. SP2013_SomeSiteNotUpgraded_13

 

 

References:

  1. Sharepoint Troubleshooting: Data base is Up to date but some sites are not completely upgraded
  2. Data base is Up to date but some sites are not completely upgraded
  3. sharepointdiary – Database is up to date, but some sites are not completely upgraded
  4. Stefan Gossner – Why I prefer PSCONFIGUI.EXE over PSCONFIG.EX

 

Create New Project from Existing in MS Project

Monday, March 21st, 2016

Creating a new project using an existing Project

[If your project was on Project Server, first save as the project on your desktop as .mpp file]

  1. Open MS Project Professional 2013 and make sure you are connected to MS Project Server PPM
  2. Go to File menu > New
  3. Under Featured tab click on ‘New from existing project’ icon

MSP2013_UseExisting_ProjectTemplates2

  1. In ‘New from Existing Project’ dialog box, navigate to the .MPP project file from your desktop and click Open
  2. Click on File > Save As > Save button
  3. In the next dialog box, enter the name of the project and click Save

MSP2013_UseExisting_ProjectTemplates3

  1. Continue to modify the project after the status bar in bottom middle says ‘Save completed successfully’

 

Creating a new project using Enterprise Templates

Only Project Server Administrators can save projects as Enterprise Templates.

  1. Open MS Project Professional 2013 and make sure you are connected to MS Project Server PPM
  2. Go to File menu > New. Then click on Enterprise tab on the right side (the view defaults to Featured)

MSP2013_UseExisting_ProjectTemplates

  1. Click on one of the relevant template
  2. Before making changes, click the File > Save option
  3. Enter the name of the project and other custom fields information
  4. Click OK
  5. Continue to modify the project after the status bar in bottom middle says ‘Save completed successfully’

Protected: Project PPM Reporting and BI

Tuesday, March 1st, 2016

This content is password protected. To view it please enter your password below:

Six Steps to Remove Project Server from SharePoint Farm

Tuesday, December 22nd, 2015

Six Steps to Remove Project Server from SharePoint Farm

Version: 1.0, Last Modified: 12/22/2015

Applies to: Project Server 2010, Project Server 2013

Microsoft Project Server PPM relies on SharePoint Farm for the base architecture. There are situations where you have to remove Project Server from the farm. The situation could be due to erroneous servers, Farm or the data might have been migrated over to next version and you need to decommission just the Project Server from the farm.

I’ll take the example of  SharePoint / Project Server 2010 farm. Following are the high level steps needed to remove Project Server:

  1. Delete Project Web App (PWA) 2010 instance
  2. Delete Project Server 2010 Service Application
  3. Delete Web Application for Project Web App 2010
  4. Stop ‘Project Application Service’ on each server in the Farm
  5. Remove custom Solutions related to PPM
  6. Other configuration items that may need removal / release from config books

CAUTION – Don’t remove Project Server software bits. Doing so will cause the whole farm to go in a bad state.

 

1 Delete Project Web App (PWA) 2010 instance

Follow the steps to delete the PWA instance.

  1. Go to SharePoint Central Administration > Manage Service Applications.
  2. Click on Project Server Service Application name.
  3. That will bring you to ‘Manage Project Web App sites’ page. Hover over the Project Web App (PWA)  instance and click on the drop down menu on the right. Choose Delete option.

    SharePoint 2010 Unprovision Project Server PWA 2010

    SharePoint 2010 Unprovision Project Server PWA 2010

  4. Review the information on next page and hit the delete button

    SharePoint 2010 Unprovision Project Server PWA 2010 b

    SharePoint 2010 Unprovision Project Server PWA 2010 b

  5. You will be back to Manage Project Web App Sites page after instance is deleted.

    SharePoint 2010 Unprovision Project Server PWA 2010 c

    SharePoint 2010 Unprovision Project Server PWA 2010 c

 

2 Delete Project Server 2010 Service Application

Follow the steps to delete the Project Server Service Application.

  1. Go to SharePoint Central Administration > Manage Service Applications.
  2. Click anywhere in the row for Project Server Service Application except the name to highlight the service application.
  3. Click the delete button on the top ribbon

    SharePoint 2010 Delete Project Server Service Application

    SharePoint 2010 Delete Project Server Service Application

  4. On ‘Delete Service Application‘ dialog box, check the box ‘Delete data associated with the Service Application‘ and click Ok button

    SharePoint 2010 Delete Project Server Service Application b

    SharePoint 2010 Delete Project Server Service Application b

  5. Project Server Service application will be deleted.

 

3 Delete Web Application for Project Web App 2010

Now delete the web application including its content database and IIS Website by following step below:

  1. Go to SharePoint Central Administration >  Manage Web Applications
  2. Click on Web Application that hosted the PWA. Make sure there are no other site collection that may have been created besides /PWA site collection.
  3. Click on the Delete drop down button in the ribbon and then choose Delete Web Application
  4. Under ‘Delete Web Application’ dialog box, check Yes for ‘Delete content database’ and for ‘Delete IIS web sites’

    SharePoint 2010 Delete PWA Web App

    SharePoint 2010 Delete PWA Web App

  5. Click the Delete button
  6. The web application including its Content Database from SQL Server and IIS website will be deleted.

 

4 Stop ‘Project Application Service’ on each server in the Farm

Follow the steps below.

  1. Go to SharePoint Central Admin > Manage Servers in this Farm.
  2. Click on one of the Server name that is running ‘Project Application Service’
  3. On the next page, click stop link on the right of ‘Project Application Service’. That will stop the two windows services console services for Events and Queue. The service will show Stopped status.

    SharePoint 2010 Stop Project Server Service

    SharePoint 2010 Stop Project Server Service

  4. Switch to other server(s) in the farm and perform the same steps to stop the service.

 

5 Remove custom solutions related to PPM

Remove any custom solutions that might have been deployed for the PPM. Go under System Settings > Manage Farm Solutions and remove those solutions. You may have to review and update the web.config file for other web applications.

 

6 Other configuration items that may need removal / release from config books:

  1. Load Balancer Virtual IP (VIP) and configurations related to PWA Web App
  2. Remove DNS entries if the PWA Web App name is no longer needed
  3. Release the IP configuration that may have been reserved for PWA
  4. Remove the PWA Web App from the SharePoint Search Content Source and other configurations
  5. Remove the PWA related Service Accounts that may not be needed
  6. Remove the Active Directory Kerberos SPN that are no longer valid under the service accounts
  7. Remove any SSL certificates related to PWA
  8. Remove any IIS Application Pools that may not be needed
  9. Any firewall / proxy configuration updates
  10. Removing / upgrading older versions of MS Project Professional

 

After all these removal steps, you should be fine. Don’t try to uninstall the Project Server software bits on the servers. That will cause your farm to go worst.

 

References:

  1. Uninstall Project Server from SharePoint Farm
  2. How do you remove a server from the SharePoint 2010 Farm which includes Project Server 2010
  3. Uninstalling Project Server from a farm? Don’t forget to run PSConfig!
  4. Deleting a Project Service Application within SharePoint 2010

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.

 

 

SharePoint Project Server 2016 Resources

Monday, August 24th, 2015

V: 3.1, Updated on: 03/19/2016

On Jan 21, 2016 Bill Baer – Microsoft’s Senior SharePoint Product Manager announced the availability of the SharePoint Server 2016 on Yammer. On Mar 14 2016 Microsoft released the RTM for SharePoint and Project Server.

SharePoint 2016 comes with lots of improvements, enhancements and features.

SharePoint 2016 Preview

You can use the following resources to start your game plan for SharePoint 2016 and Project Server 2016. The game is on…..

SharePoint Server 2016 Resources

  1. SharePoint 2016 – Technet Center – https://technet.microsoft.com/en-us/library/cc303422(v=office.16).aspx
  2. SharePoint 2016 Technet Forums – https://social.technet.microsoft.com/Forums/en-us/home?forum=SP2016
  3. Announcing availability of SharePoint Server 2016 and cloud hybrid search – https://blogs.office.com/2015/08/24/announcing-availability-of-sharepoint-server-2016-it-preview-and-cloud-hybrid-search/
  4. SharePoint Server 2016 Datasheet – http://www.microsoft.com/en-us/download/details.aspx?id=48715
  5. SharePoint Server 2016 Quick Start Guide – http://www.microsoft.com/en-us/download/details.aspx?id=48714
  6. SharePoint Server 2016 Reviewer Guide – http://www.microsoft.com/en-us/download/details.aspx?id=48713
  7. SharePoint Server 2016 Download – https://www.microsoft.com/en-us/download/details.aspx?id=51493
  8. Language Packs for SharePoint Server 2016 – https://www.microsoft.com/en-us/download/details.aspx?id=51492
  9. SharePoint 2016 RTM and the Future of SharePoint event – https://blogs.office.com/2016/03/14/sharepoint-2016-rtm-and-the-future-of-sharepoint-event/
  10. Technet Forums – SharePoint 2016 – https://social.technet.microsoft.com/Forums/office/en-US/home?forum=SP2016
  11. What’s new for admins in SharePoint Server 2016 – https://blogs.office.com/2016/03/14/whats-new-for-admins-in-sharepoint-server-2016/
  12. First look at SharePoint Server 2016 IT Preview – Youtube video – https://www.youtube.com/watch?v=rV6PVzGs51I
  13. Hybrid Center – http://hybrid.office.com/

 

Project Server 2016 Resources

Project Server 2016 is a service application in SharePoint 2016. That will makes its installation and deployment easier. SharePoint Server 2016 resources apply to ProjectServer 2016 as well. Below are some of the additional resources specific to Project Server 2016,

  1. Project Server 2016 – Technet Center – https://technet.microsoft.com/en-us/library/cc303399(v=office.16).aspx
  2. Project Forums – https://social.technet.microsoft.com/Forums/projectserver/en-us/home?category=project
  3. Project Online – https://products.office.com/en-us/Project/project-online-portfolio-management
  4. Find information about Project Online – https://support.office.com/en-us/article/Find-information-about-Project-Online-e33e2273-dfaf-4eb7-aacc-393e80e58a97
  5. What’s new in Project 2016 – https://blogs.office.com/2015/09/30/whats-new-in-project-2016/
  6. Users Voice – Office 365 Project & Portfolio Management (PPM) – https://microsoftproject.uservoice.com/forums/218133-office-365-project-portfolio-management-ppm

 

Office Online Server 2016 Resources

Office Online Server 2016 is a next version of Office Web Apps Server.

  1. Office Online Server 2016 on Technet – https://technet.microsoft.com/en-us/library/jj219456(v=office.16).aspx

 

Keep watching this space for updated information, resources and news.

logo 250x250

Keywords:

  • Download SharePoint Server 2016
  • Download Project Server 2016
  • Resources on SharePoint Server 2016
  • Resources on Project Server 2016
  • Resources on SharePoint 2016
  • How to Start with SharePoint Server 2016
  • How to Start with Project Server 2016
  • Play the game of SharePoint 2016
  • Help with SharePoint Server 2016
  • Help with Project Server 2016
  • Project Server PPM 2016
  • ProjectServer PPM 2016
  • Best resources on SharePoint 2016
  • Helpful resources on SharePoint 2016

Project Web Access 2010 Manage Timesheets and IE 11 Compatibility

Thursday, February 5th, 2015

Version: 1.0

Scenario

I came across a scenario where a user needed to recall and delete some of his Project Web Access (PWA) 2010 timesheets. Its not straightforward, keep reading :). The user was using Internet Explorer (IE) 11 on Windows 7 running under VMware VDI.

Normally a user would click on ‘Manage Timesheets‘ from PWA to delete / recall timesheets. With IE 11 the user was getting error:

Error
This Project Server 2010 feature requires at least Microsoft Internet Explorer 7.0.
Correlation ID:####
Date and Time: MM/DD/YYYY TT:TT

Project Web Access - Manage Timesheets page Error when using IE 11
Project Web Access – Manage Timesheets page Error when using IE 11

Background

Looking at the official Project Web Access 2010 Support page, I noticed that IE 11 is not supported browser for by Microsoft Project Web Access (PWA).

Reference:
Plan browser support (Project Server 2010)
https://technet.microsoft.com/en-us/library/ff631137(v=office.14).aspx

The way to go with IE 11 with Project Web Access 2010

Solution 1:

Add your PWA URL *.companyname.com in the local intranet zone of Internet Explorer.

Besides that review the Compatibility View Settings under Tools menu. The default compatibility view settings display the local intranet sites in Compatibility View.

PWA Manage Timesheets page error - Default IE 11 Compatibility View settings
PWA Manage Timesheets page error – Default IE 11 Compatibility View settings

The above method has few benefits:
a. user will not be prompted with the login to PWA site on local intranet
b. Compatibility view default settings will make the PWA URL to work in compatibility mode

Solution 2:
If adding sites to IE Local Intranet zone is locked down by IT, then review the Compatibility View settings and make sure Local Intranet sites option is checked (above screenshot). If it is not than check it or just add the companyname.com url into the field above and click Add

Solution 3:
If IE Local Intranet zone and Compatibility View settings are locked down by IT, then your next option is to use IE Developer Tool using F12 key and changing Document Mode and User Agent settings.

To recall / delete timesheet using IE11, follow these steps:

Log on to your VDI or virtual desktop environment and launch default Internet Explorer session. In this case IE 11. then follow steps listed below.

1. Go to your PWA 2010 portal http://pwa.svlab.com/pwa
2. Click on Manage Timesheets link on bottom left. The page link is http://pwa.svlab.com/pwa/_layouts/pwa/timesheet/mytssummary.aspx
3. You will get error saying, it need at least IE 7. Press F12 key on keyboard to bring IE developer tools window
4. Go to Emulation tab
5. Change the mode to following

  • Document Mode: 8 (Default)
  • User agent string: Internet Explorer 9

6. The page will automatically refresh and will bring the user timesheets
7. Select a timesheet and click Recall or delete icon for the timesheet

  • You can Delete a Timesheet with Status In Progress
  • You can Recall a Timesheet with status Approved

8. Click on the timesheet link for the period that you want to adjust. For deleted timesheet click on ‘Click to Create’ link
9. Save and submit the timesheet or proceed as needed.

Project Web Access - Manage Timesheets page in IE 11 using F12 Dev Tools and changing Mode
Project Web Access – Manage Timesheets page in IE 11 using F12 Dev Tools and changing Mode

Solution 4:
There are few other tricks but I’ll not cover those details here for the sake of time. Those are around manipulating the user agent & x-ua Compatible settings.

Solution 5:
Roll out Local Intranet Sites and Compatibility view settings via Active Directory Group Policy (GPO) settings.

Alternatively for a Virtual Desktop Infrastructure (VDI), Remote Desktop / Terminal Server or Citrix type environments, make the configuration as part of the global / admin change that all users in that virtual environment will automatically get.

Scope:
This article is not about details of Browser mode, user agent, compatibility view or other related settings.

References:

  1. Project Web App 2010 can use IE 10 in compatibility mode
  2. Erik Van Hurck – Internet Explorer 11, Windows 8.1 and Project Server 2013
  3. Cory Peters – SharePoint and Internet Explorer 11
  4. IEInternals MSDN – Internet Explorer 11’s Many User-Agent Strings

Keywords:

  • using IE 11 with PWA 2010
  • using IE 11 with Microsoft Project Web Acccess 2010
  • manage timesheets page error in pwa 2010
  • this feature requires at least Internet Explorer 7
  • using compatibility view settings with PWA 2010
  • using compatibility view settings in IE 11
Visit www.softvative.com for professional services.

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.