Apr 21
2013 Migration error messages of Out-of-box version of Project Server 2010

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

  1. Test-SPContentDatabase
  2. Test-SPSite
  3. Test-SPProjectDatabase
  4. 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.

PS> Test-SPContentDatabase -Name $PS2010ContentDBname -WebApplication $URL

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        : 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        : MissingSetupFile
Error           : True
UpgradeBlocking : False
Message         : 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        : MissingSetupFile
Error           : True
UpgradeBlocking : False
Message         : 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       :

PS > Test-SPSite -Identity $PWA

​Site               : SPSite Url=http://sp2013v6a/PWA

Results            : {

                     SPSiteHealthResult Status=Passed RuleName="Conflicting Content Types" RuleId=befe203b-a8c0-48c2-b5f0-27c10f9e1622,

                     SPSiteHealthResult Status=FailedWarning RuleName="Customized Files" RuleId=cd839b0d-9707-4950-8fac-f306cb920f6c,

                     SPSiteHealthResult Status=Passed RuleName="Missing Galleries" RuleId=ee967197-ccbe-4c00-88e4-e6fab81145e1,

                     SPSiteHealthResult Status=Passed RuleName="Missing Parent Content Types" RuleId=a9a6769f-7289-4b9f-ae7f-5db4b997d284...}

PassedCount        : 6

FailedWarningCount : 1

FailedErrorCount   : 0

 

PS > Test-SPProjectDatabase -Name $ProjectServiceDBname  -DatabaseServer $SqlServer

Category        : Upgrade
Error           : False
UpgradeBlocking : False
Message         : Upgrader version 15.0.4569.1000 matches stored version 15.0.45691000.0
Remedy          :
Locations       :
Category        : Security
Error           : False
UpgradeBlocking : False
Message         : Permissions for all existing roles are correct
Remedy          :
Locations       :
 
Category        : Security
Error           : False
UpgradeBlocking : False
Message         : All SQL database roles are present
Remedy          :
Locations       :

​PS> Test-SPProjectWebInstance -Identity $PWA

RuleName  : ProjectBICenterExistenceHealthRule
TimeStamp : 4/22/2016 2:33:01 AM
Message   :
            The following ProjectBICenters have missing lists: (/PWA/ProjectBICenter, Reports).
Status    : FailedWarning
Results   :
RuleName  : ProjectWorkspacesExistenceHealthRule
TimeStamp : 4/22/2016 2:33:01 AM
Message   : All projects have workspace webs.
Status    : Passed
Results   :

RuleName  : SiteQueueServicedStatus
TimeStamp : 4/22/2016 2:33:01 AM
Message   : Service status of Queue: (771b2ec1-944b-4c45-b9ea-25598d3865a7, True).
Status    : Passed
Results   :
 
RuleName  : QueueJobs
TimeStamp : 4/22/2016 2:33:02 AM
Message   :
Status    : Passed
Results   : {SP2013V6A, SP2013V6A, SP2013V6A}​

RuleName  : QueueMissingTriggers
TimeStamp : 4/22/2016 2:33:02 AM
Message   : Number of unprocessed jobs in Queue: 0.
Status    : Passed
Results   :

RuleName  : QueueStaleServerGroups
TimeStamp : 4/22/2016 2:33:02 AM
Message   : All Queue Groups OK.
Status    : Passed
Results   : ​

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.

 

Comments

There are no comments for this post.

 ‭(Hidden)‬ Blog Tools