Migration from Project Server 2010 to Project Server 2013 can be a daunting experience. The one thing that puzzled me the most was the results from the PowerShell TEST verbs. There are four test verbs that are used during the migration

Test-SPContentDatabase

Test-SPSite

Test-SPProjectDatabase

Test-SPProjectWebInstance

These are very useful tools that can help you be successful with a migration, but my biggest question was; are these normal messages. Finally, I decided to find out. My assumption is that if I built a brand new project server 2010 with service pack 2 and add a couple of projects and resources, then when I migrated to project server 2013, there would be no message. The following PowerShell test verbs were executed on a plain out-of-box version of project server and though I expected that all the tests would come clean. They didn't.

The following examples show the output from PoweShell test commands on a out-of-box version of project server 2010 that is being migrated to 2013. Project server 2010 was using the classic authentication.

​Category : MissingSetupFile Error : True UpgradeBlocking : False Message : File [Features\ReportServer\ReportViewer.dwp] is referenced [1] times in the database [SP2010V6_WSS_Content], but is not installed on the current farm. Please install any feature/solution which contains this file.​ Remedy : One or more setup files are referenced in the database [SP2010V6_WSS_Content], but are not installed on the current farm. Please install any feature or solution which contains these files.

​Locations : ​

Category : MissingSetupFileError : TrueUpgradeBlocking : FalseMessage : File [Features\ReportServer\ReportViewer.dwp] is referenced [1] times in the database [SP2010V6_WSS_Content], but is not installed on the current farm. Please install any feature/solution which contains this file.Remedy : One or more setup files are referenced in the database [SP2010V6_WSS_Content], but are not installed on the current farm. Please install any feature or solution which contains these files.Locations :

Category : MissingSetupFileError : TrueUpgradeBlocking : FalseMessage : File [SiteTemplates\BICENTERSITE\mossbisample.aspx] is referenced [1] times in the database [SP2010V6_WSS_Content], but exists only under Microsoft SharePoint Foundation 2010 setup folder. Consider upgrading the feature/solution which contains this file to the latest version.Remedy : One or more setup files are referenced in the database [SP2010V6_WSS_Content], but are not installed on the current farm. Please install any feature or solution which contains these files.Locations :

Category : MissingSetupFileError : TrueUpgradeBlocking : FalseMessage : File [SiteTemplates\BICENTERSITE\ppssample.aspx] is referenced [1] times in the database [SP2010V6_WSS_Content], but exists only under Microsoft SharePoint Foundation 2010 setup folder. Consider upgrading the feature/solution which contains this file to the latest version.Remedy : One or more setup files are referenced in the database [SP2010V6_WSS_Content], but are not installed on the current farm. Please install any feature or solution which contains these files.Locations :

In summary, this is only a list of message that seem normal to me. I have done many migrations and have ignore the messages and the migration appear to work without any issues. If you google the messages, there are fixes for most of the messages.