Migrate to Project Server 2016 Step By Step

In this article, I will explain how to

Migrate from Project Server 2013 to Project Server 2016 Step By Step?


Upgrade to Project Server 2016 Prerequisites

Before we get started, you should check the below Project Server 2016 Migration Prerequisites.

In Project Server 2013 Source Farm,
  • Make sure that the current Project Server 2013 farm is at least patched to Service Pack1.

To get the latest SharePoint Cumulative Update installed check Find farm patch level / latest cumulative update that has been installed on SharePoint farm

  • Specify the Web Application content databases.
  • Specify the PWA instance with its ‘Project Web App‘ database.
  • Take a full database backup for the PWA instance database.
  • Take a full database backup for the Project content databases.
In Project Server 2016 Destination Farm,
  • Prepare Project Server 2016 farm.

Check Install and Configure Project Server 2016

  • Take a full database backup from the Content Database.

Note: In Project Server 2016, a single database (SharePoint Content Database) holds the project data and the content to facilitate the database operations, such as backup and restore, migration, etc.

In next section, I will explain the Project Server 2016 Migration prerequisites in details


Migrate from Project Server 2013 Prerequisites

In Project Server 2013 Source farm, you should do the following:

Specify the Web Application Content Databases.

  • Open SharePoint Management Shell as Administrator.

Upgrading to Project Server 2016

  • Perform Get-SPContentDatabase cmdlet to get all the content databases of your web application

Get-SPContentDatabase -WebApplication http://webApp

Upgrading to Project Server 2016

In my case, I have two content databases.

  • WSS_Content (The Main web application Content Database).
  • WSS_Content_PWA (An independent Project Content Database).

Specify the PWA Instance with its ‘Project Web App‘ database

  • Open SharePoint Management Shell as Administrator.
  • Perform Get-SPProjectWebInstance to get the related information of PWA instance.

Get-SPProjectWebInstance -Url http://PWAInstanceUrl

Upgrading to Project Server 2016

Take a full database backup for the PWA Database

  • Open SQL Server Management Studio.

open-sql-managment-studio

  • Connect to the SQL Server instance.

connect-to-ssms

  • Backup ‘ProjectWebApp‘ Database.
    • Right click on Database name > Tasks > Back Up.
    • Ensure that the Backup type is Full > In destination section, Select Disk > Browse the backup path > OK.

Backup database

  • The Backup should be now completed successfully.

back-up-database-2

Take a full database backup for the Project Content Database

  • Repeat the above backup steps for the below Project content database:
    • WSS_Content_PWA.

Migrate to Project Server 2016 Prerequisites

In Project Server 2016 destination farm, you should do the following:

Prepare Project Server 2016 farm

One of the biggest changes in Project Server 2016 is the installation process. So before you get started to Install and configure Project Server 2016, you should be aware of the following:

  • A separate installation is no longer required as it was in previous versions of Project Server.
  • The SharePoint Server 2016 MSI file will contain the installation files for Project Server 2016 as well.
  • Project Server 2016 runs as a service application in SharePoint Server 2016.
  • Project Server 2016 is only available on SharePoint Server 2016 Enterprise.

Note: Although Project Server 2016 is included as part of the SharePoint Server 2016 Enterprise installation, but it is still require a separate license.

To Configure Project Server 2016, check the details steps at


Project Server 2016 Migration Steps

  1. Copy the Project Server 2013 databases backup to the Project Server 2016 Database Server.
  2. Restore the Project Server 2013 databases backup to the SQL Server.
  3. Dismount the Current PWA 2016 Content Database.
  4. Mount the PWA Content Database.
  5. Test the PWA Content Database.
  6. Migrate the PWA Database.
  7. Disable database quota limits for the PWA site.
  8. Upgrade the Resource Plans to Resource Engagements.
  9. Change PWA Instance Site Collection.
  10. Test the migrated PWA Site.

Copy the Project Server 2013 databases backup to Project Server 2016 Database Server

Move the databases backup from the Project Server 2013 source farm to the backup path at Project Server 2016 database server.

  • WSS_Content_PWA‘.(PWA Content Database).
  • ProjectWebApp‘. (PWA Database).

PWA content databases in project server

Restore the Project Server 2013 databases backup to the SQL Server.

  • Open the SQL Server Management Studio.
  • Connect to the SQL Server instance.
  • Perform the restore operation for each database as shown below.

Upgrading to Project Server 2016

  • Repeat the above steps for ‘ProjectWebApp‘.

Dismount the PWA 2016 Content Database.

If you have already deployed the PWA instance In Project Server 2016, so you should first dismount the current PWA 2016 content database before going to the next step.

  • Open the SharePoint 2016 Management Shell as an Administrator.

Upgrading to Project Server 2016

  • Dismount the current PWA 2016 Content Database using the below cmdlet.

Dismount-SPContentDatabase "Current PWA 2016 Content Database"

Note: In Project Server 2016, there is only a single content database that holds the Projects Data and Projects Content to facilitate the operation tasks like the backup.

pwa content database in project server 2016

For more details, check Simply, what’s new and deprecated in Project Server 2016?

Mount the PWA Content Database.

Once the restore operation is completed, you should now mount (reattach) the PWA Content Database to its web application as mentioned below:

  • Open the SharePoint 2016 Management Shell as an Administrator.

Upgrading to Project Server 2016

  • Run the ‘Mount-SPContentDatabase’ for ‘WSS_Content_PWA’ database to attach it to its web application that host the PWA instance.

Mount-SPContentDatabase "MyDatabase" -DatabaseServer "MyServer" -WebApplication http://WebAppURL

Mount PWA Content Database - Upgrading to Project Server 2016

Note:

  • Mount database operation will take some minutes based on its size.
  • After the database has been mounted successfully, you may see its status still Upgrading In Content Database list in Central Administration, so in this case, click on its name to open its details then click Ok, The mounted database status should be now started.

Test the PWA Content Database.

Now, you should run Test-SPContentDatabase cmdlet to verify all customizations referenced within the content database are installed in the new Project Server 2016 web application.

  • Open the SharePoint 2016 Management Shell as an Administrator.

Upgrading to Project Server 2016

  • Run the Test-SPContentDatabase as below.

Test-SPContentDatabase -Name WSS_Content_PWA -WebApplication "http://NewWebAppURL"

Note: The results do not imply that the upgrade of the SharePoint 2013 content database has failed, but will only note things you need to look into in your new environment.

Test PWA Content Database - Upgrade from Project Server 2013 to 2016

This message means that the Excel Services Web Part that is referenced in the upgraded content database is not found on the SharePoint Server 2016 farm.

You might need to install Office Online Server on your SharePoint Server 2016 farm to use it.

Migrate the PWA Database.

Now, you should migrate the PWA Database (‘ProjectWebApp’) as the following:

  • Open the SharePoint 2016 Management Shell as an Administrator.

Upgrading to Project Server 2016

  • Run the Migrate –SPProjectDatabase as below.

Migrate-SPProjectDatabase -DatabaseName ProjectWebApp -SiteCollection "http://PWASiteURL"

Migrate Project Web APP Database in Project Server 2016 - Migrate-SPProjectDatabase

Disable database quota limits for the PWA site.

In Project Server 2016, By default the database quota limit restriction is set, so you should disable the database quota limit restriction to avoid the below error

This site is read-only at this moment

If you don’t disable the database quota limit restriction, you will get

This site is read-only at this moment” error, in case

  • The current migrated ‘PWA Database’ is larger than 10 GB
  • or the current migrated ‘PWA Database’ is less than 10 GB but with daily use, it goes over the 10GB limit.
  • Another reason you may get this error, in case you are using a Sharepoint 2016 trial version that was expired!

To disable the database quota limit restriction, you should do the following:

  • Open the SharePoint 2016 Management Shell as an Administrator.

Upgrading to Project Server 2016

  • Run the Set-SPProjectDatabaseQuota as below.

Set-SPProjectDatabaseQuota -URL http://PWASiteURL -Enabled:$false -ReadOnlyLimit 10200 -ReadOnlyWarningThreshold 90 -MaxDbSize 10240

Disable PWA database quota limits - Upgrading to Project Server 2016

Upgrade the Resource Plans to Resource Engagements

As we know, the Resource Plan is now deprecated, replaced with a new Resource Engagements in Project Server 2016.

Read more at Simply, what’s new and deprecated in Project Server 2016?

So you should upgrade the Resource Plan to the new Resource Engagements as the following:

  • Open the SharePoint 2016 Management Shell as an Administrator.

Open SharePoint 2016 PowerShell - Upgrade and Migrate to Project Server 2016

  • Run the Migrate-SPProjectResourcePlans as below:

Migrate-SPProjectResourcePlans -URL "http://PWASiteURL"

Migrate Project Resource Plan - Upgrade to Project Server 2016

After running the cmdlet, you should receive one of the following confirmation messages:

  • All Project Resource Plans successfully migrated.
  • Migrated {0} of {1} Project Resource Plans. Check the logs for more details.
  • There are no more project resource plans to migrate. Either all resource plans were migrated or exceeded the maximum retry count. Please check table MSP_RESOURCE_PLANS in the published store and verify RESPLAN_IS_MIGRATED is set for all projects.

Change the Migrated PWA Site Collection Administrator

  • Open Central Administration > Application Management.
  • Below Site Collections  > Click on Change Site Collection Administrators.

Change site collection administrators in Project Server 2016

  • Set the new PWA Site Collection Administrators.

Change site collection administrator for PWA in Project Server 2016

Test the migrated PWA 2016 Site.

Finally, browse the new migrated PWA site, perform a quick smoke test!

  • Open PWA 2016 Instance.
  • Check the  Project Center and make sure it opened and render projects properly.
  • Click on one of the Projects to make sure that the PDP and Schedule Page working properly.

Migrate from Project Server 2013 to 2016

If everything is OKay and working properly, go to the database server to delete

  • ProjectWebApp 2013 database.
  • Old PWA 2016 Content database.

Project Server 2016 Known Issue

Missing Project Database Users Views in Project Server 2016 

Although the PWA instance is migrated and browsed successfully, the PWA content database may miss some of the main Users views like “[pjrep].[MSP_EpmProject_UserView]“.

Missing PWA views In Project Server 2016

To check if your PWA content database is created properly or miss some views, try to do the following:

  • Connect to the SQL Server that hosts your SharePoint environment.
  • Create a new query on your PWA content database, query “MSP_EpmProject_UserView“.

Select * from [pjrep].[MSP_EpmProject_UserView]

  • If you got invalid object name, that means the PWA content database miss some of the User views!

PWa Database Missing views

In this case, you should repair the PWA Instance using  Repair-SPProjectWebInstance as the following:

Repair the PWA 2016 Instance
  • Open SharePoint Management Shell via Administrator.
  • Run the Repair-SPProjectWebInstance abased on your PWA Instance URL as shown below:

PS C:\Users\mqassas> Repair-SPProjectWebInstance

cmdlet Repair-SPProjectWebInstance at command pipeline position 1
Supply values for the following parameters:
Identity: https://PWA Instance URL
RepairRule: 7

RuleName TimeStamp Message Status
-------- --------- ------- ------
...irableHealthRule 11/27/2017 10:33... The RDB User Vie... Succeeded

PS C:\Users\mqassas>

PWA Content Database Missing Views

Note: you may also face this issue either for the new created PWA instance in a new installation or after patching the Project Server 2016 with new cumulative updates.


Applies To

Project Server 2016.

Conclusion

In this article, I have explained How to Upgrade and Migrate PWA Instance from Project Server 2013 to Project Server 2016 Step By Step?

See Also
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s