The process of upgrading from Project Server 2010 to Project Server 2013, or migrating between environments can be quite complex, requiring a number of steps to be completed in the correct order. In this post, I am going to document some of the common and uncommon errors that you may run into. I also intend to update this post as I uncover more.
Unmounted Project Service Database
Unlike SharePoint Content databases, Project Service databases need to be mounted before you can run a Test against them. If you do not mount them, you will see the following error.
Test-SPProjectDatabase : Could not find the ProjectDatabase instance (looking for database name: ‘ProjectWebApp’, service name: ‘demo2013’)
To rectify this issue, make sure you mount the Project Database prior using
Mount-SPProjectDatabase –Name –WebApplication
ConvertTo-SPProjectDatabase returns a ‘There are no addresses available for this application’ error.
The ConvertTo-SPProjectDatabase is used during an upgrade to convert the four Project Server 2010 databases (Draft, Published, Archive and Reporting) into one consolidated Project Service database with the different schemas.
You will see the ‘There are no addresses available for this application’ error if you try and run this command and the Project Service App is not started. To rectify this, navigate to Central Administration and ensure the Project Service App is started and recycle the box, then try again.
Compilation Error – Microsoft.Office.Project.PWA.IDS does not contain a definition for ‘Licence_Copyright_Text’
You may run across this error message when navigating to a PWA instance that originated in Project Server 2010.
This error occurs when a 2010 PWA site has been mounted but the PWA site wasn’t upgraded using the following command:
Upgrade-SPSite -Identity -VersionUpgrade
The PWA Settings option is missing from the Site Settings Menu
In Project Server 2013, the Server Settings menu item has been replaced by a PWA Settings option on the Site Settings menu. When performing an upgrade from Project Server 2010, this menu option is not automatically added when using the DB Attach method via PowerShell.
In the screenshot below you can see that the upgrade has been completed successfully, but the PWA Settings option is missing.
To fix this error, ensure you enter the following PowerShell command:
Enable-SPFeature –Identity pwasite –URL
This will enable the pwasite feature which provides the PWA Setting menu link.