none
HELP!: Migrate-SPProjectDatabase : Error encountered while migrating project data in Content database. Action 16.0.34.0 of Microsoft.Office.Project.Server.Upgrade.PSDatabaseSequence failed.

    Question

  • Am trying to migrate Project server over from 2013 to 2016. I have two instances of PWA on the same server. One instance upgrades perfectly fine, while the second gives me the following error. I am using this guide (https://blog.devoworx.net/2017/10/30/project-server-2016-migration/) as a reference. 

    I am at the step where I migrate the PWA database. Here's what happens:

    Migrate-SPProjectDatabase -SiteCollection http://Server/pwa -DatabaseServer SP-DEVLDATABASE -DatabaseName SP_ProjectServer_DB -Overwrite -Verbose -confirm

    VERBOSE: Leaving BeginProcessing Method of Migrate-SPProjectDatabase.
    VERBOSE: Found site collection 'http://Server/pwa'.
    VERBOSE: Found web application 'Project Web App Devl'.
    VERBOSE: Found service application 'Project Web App Devl Application Service'.
    VERBOSE: Found database server address: SP-DEVLDATABASE.
    VERBOSE: Validating that project schema is provisioned in the destination Content database.
    VERBOSE: Validating project database has the supported schema version or higher.
    VERBOSE: Upgrading the project database.
    VERBOSE: Leaving ProcessRecord Method of Migrate-SPProjectDatabase.

    Migrate-SPProjectDatabase : Error encountered while migrating project data in Content database. Action 16.0.34.0 of 
    Microsoft.Office.Project.Server.Upgrade.PSDatabaseSequence failed.
    At line:1 char:1
    + Migrate-SPProjectDatabase -SiteCollection http://Server ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OperationStopped: (Microsoft.Offic...ProjectDatabase:PSCmdletMigrateSPProjectDatabase) [Migrate-SPProjectDatabase], SPException
        + FullyQualifiedErrorId : Microsoft.Office.Project.Server.Cmdlet.PSCmdletMigrateSPProjectDatabase


    • Edited by Zuhair Khan Thursday, December 6, 2018 6:05 PM Typo
    Tuesday, December 4, 2018 10:09 PM

All replies

  • The reference that you are referring to is migrating from 2013 to 2016.

    Are you planning to migrate from 2013 to 2016 and then migrate from 2016 to 2019?

    It's a two hop process and wanted to be clear, that in your documentation above that migration is from 2013 to 2016 (and not 2019).



    Michael Wharton, Project MVP, MBA, PMP and a Great Guy <br/> Website http://www.WhartonComputer.com <br/> Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Thursday, December 6, 2018 5:36 AM
    Moderator
  • Oh darn! It's a typo. I'll edit the post. I am migrating from 2013 to 2016. Thank you for pointing that out.
    Thursday, December 6, 2018 6:04 PM
  • See if this snippet helps answer questions.   Several things have to be done prior to migration. In my script, I create web application and site and mount the 2013 database.

    $SqlServerName = "WCC2014SQL.DOMAIN.LOCAL"
    $WebAppURL = "http://WCC2016SP.DOMAIN.LOCAL"
    $SitePwaURL = "http://WCC2016SP.DOMAIN.LOCAL/pwa"
    $WebAppName = "Project Server 2016"
    $ProjectServiceApp = "Project Service App"
    $ProjectServicePool = "Project Service Pool2"
    $ServiceSP = "DOMAIN\ServiceSP"
    $WSS_ContentDB = "DOMAIN_WSS_CONTENT_PWATEMP"
    #
    $WSS_Content2013 = "DOMAIN_WSS_CONTENT_WCC2" #--> replace name with migrated SharePoint 2013 Content database
    $ProjectWebApp2013 = "WCC2_ProjectWebApp" #--> replace name with migrated ProjectWebApp database
    #
    #################################################################
    # Create Web Application that contains project server collection
    # Create a TEMP
    $AP = New-SPAuthenticationProvider -Verbose
    New-SPWebApplication -Name $WebAppName -port 80 -URL $WebAppURL -DatabaseName $WSS_ContentDB -DatabaseServer $SqlServerName -ApplicationPool $ProjectServicePool -ApplicationPoolAccount (Get-SPManagedAccount $ServiceSP) -AuthenticationProvider $AP -Verbose -Confirm:$false
    # Mount WSS_Content converts to SharePoint 2016
    Mount-SPContentDatabase -Name $WSS_Content2013 -WebApplication $WebAppName -Verbose
    # Review issues found with database
    # It's possible that some error may block the upgrade or that you wish to be fix some of the issue before moving to production
    Test-SPContentDatabase -Name $WSS_Content2013 -WebApplication $WebAppName
    #Test-SPContentDatabase -Name $WSS_Content2013 -WebApplication $WebAppName | Out-File "C:\notes"
    # Upgrade-SPContentDatabase -Name $WSS_Content2013 -WebApplication $WebAppName -Verbose
    # Enable SharePoint features for PWA and BI
    # Enable-SPFeature PWASITE -Url $SitePwaURL -Verbose
    # note: PWA feature should already be enable in the migrated database
    Enable-spfeature -identity PWABIODataReports -Url $SitePwaURL -Force
    # Migrate ProjectWebApp 2013 to 2016
    Migrate-SPProjectDatabase -SiteCollection $SitePwaURL -DatabaseServer $SqlServerName -DatabaseName $ProjectWebApp2013 -Overwrite -Confirm:$false -Verbose
    # Migrate Resource Plans
    Migrate-SPProjectResourcePlans -URL $SitePwaURl -Verbose
    # Test the Project Instance for issues
    Get-SPProjectWebInstance
    Get-SPProjectWebInstance | Test-SPProjectWebInstance
    Test-SPProjectServiceApplication -Identity $ProjectServiceApp
    # Start up Project Server App Web site


    Michael Wharton, Project MVP, MBA, PMP and a Great Guy <br/> Website http://www.WhartonComputer.com <br/> Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Friday, December 7, 2018 2:51 AM
    Moderator
  • Thank you for getting back to me Michael.

    I ran the script and here is what I got. Keep in mind that I already have the service running and the content database migrated, so some errors on those steps are expected

    VERBOSE: Leaving BeginProcessing Method of New-SPAuthenticationProvider.
    VERBOSE: Leaving ProcessRecord Method of New-SPAuthenticationProvider.
    VERBOSE: Leaving EndProcessing Method of New-SPAuthenticationProvider.
    VERBOSE: Leaving BeginProcessing Method of New-SPWebApplication.
    VERBOSE: Performing the operation "New-SPWebApplication" on target "Project Web Application".
    VERBOSE: Leaving ProcessRecord Method of New-SPWebApplication.
    New-SPWebApplication : ApplicationPool exists, either specify an existing ApplicationPool alone, or specify a non existing ApplicatioPool and an 
    ApplicationPoolAccount.
    At line:43 char:1
    + New-SPWebApplication -Name $WebAppName -port 80 -URL $WebAppURL -Data ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidArgument: (Microsoft.Share...PWebApplication:SPCmdletNewSPWebApplication) [New-SPWebApplication], SPCmdletException
        + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPWebApplication
     
    VERBOSE: Leaving BeginProcessing Method of Mount-SPContentDatabase.
    VERBOSE: Getting the web application
    VERBOSE: Found web application: Project Web Application
    VERBOSE: Getting the database server
    VERBOSE: Found database server address: SP-DATABASE
    VERBOSE: Performing the operation "Mount-SPContentDatabase" on target "SP_Projects_ContentDB".
    VERBOSE: Mounting content database
    WARNING: Check D:\APPLCTN\SharePoint\DEVL\PROGRAM FILES\Logs for upgrade progress
    Mount-SPContentDatabase : The attach operation cannot continue because another object in this farm already contains the same ID. Each object in a farm must have a 
    unique ID. In order to proceed with the attach operation you must assign a new ID to this database. To attach this database with a new ID, use the 
    Mount-SPContentDatabase command with the -AssignNewDatabaseId parameter. Note that if this new database and an existing database contain the same site collections, 
    attaching this database will likely result in orphaned site collections due to conflicts between the two databases.
    At line:47 char:1
    + Mount-SPContentDatabase -Name $WSS_Content2013 -WebApplication $WebAp ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (Microsoft.Share...ContentDatabase:SPCmdletMountContentDatabase) [Mount-SPContentDatabase], SPException
        + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletMountContentDatabase
     
    VERBOSE: Leaving ProcessRecord Method of Mount-SPContentDatabase.
    VERBOSE: Leaving EndProcessing Method of Mount-SPContentDatabase.


    Category        : MissingSetupFile
    Error           : True
    UpgradeBlocking : False
    Message         : File [Features\ReportServer\ReportViewer.dwp] is referenced [1] times in the database [SP_Projects_ContentDB], 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 [SP_Projects_ContentDB], but are not installed on the current farm. Please install 
                      any feature or solution which contains these files.
    Locations       : 

    Category        : MissingWebPart
    Error           : True
    UpgradeBlocking : False
    Message         : WebPart class [e6002ce8-69ee-168a-8f7c-a1d98d51da29] (class [Microsoft.Office.Excel.WebUI.ExcelWebRenderer] from assembly 
                      [Microsoft.Office.Excel.WebUI, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [52] times in the database 
                      [SP_Projects_ContentDB], but is not installed on the current farm. Please install any feature/solution which contains this web part.
    Remedy          : One or more web parts are referenced in the database [SP_Projects_ContentDB], but are not installed on the current farm. Please install any 
                      feature or solution which contains these web parts.
    Locations       : 

    VERBOSE: Leaving BeginProcessing Method of Migrate-SPProjectDatabase.
    VERBOSE: Found site collection 'http://ProjectServer/pwa'.
    VERBOSE: Found web application 'Project Web Application'.
    VERBOSE: Found service application 'Project Web Application Application Service'.
    VERBOSE: Found database server address: SP-DATABASE.
    VERBOSE: Validating that project schema is provisioned in the destination Content database.
    VERBOSE: Validating project database has the supported schema version or higher.
    VERBOSE: Performing the operation "Migrate-SPProjectDatabase" on target "SP_ProjectServer_ServiceDB".
    VERBOSE: Upgrading the project database.
    VERBOSE: Leaving ProcessRecord Method of Migrate-SPProjectDatabase.
    Migrate-SPProjectDatabase : Error encountered while migrating project data in Content database. Action 16.0.34.0 of 
    Microsoft.Office.Project.Server.Upgrade.PSDatabaseSequence failed.
    At line:69 char:1
    + Migrate-SPProjectDatabase -SiteCollection $SitePwaURL -DatabaseServer ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OperationStopped: (Microsoft.Offic...ProjectDatabase:PSCmdletMigrateSPProjectDatabase) [Migrate-SPProjectDatabase], SPException
        + FullyQualifiedErrorId : Microsoft.Office.Project.Server.Cmdlet.PSCmdletMigrateSPProjectDatabase
     
    VERBOSE: Leaving BeginProcessing Method of Migrate-SPProjectResourcePlans.
    VERBOSE: Leaving ProcessRecord Method of Migrate-SPProjectResourcePlans.
    Migrate-SPProjectResourcePlans : Error encountered while migrating project resource plans data. No rows in MSP_WEB_ADMIN table for the site collection. Possibly PWA 
    was not provisioned or it is deleted.
    At line:73 char:1
    + Migrate-SPProjectResourcePlans -URL $SitePwaURl -Verbose
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OperationStopped: (Microsoft.Offic...teResourcePlans:PSCmdletMigrateResourcePlans) [Migrate-SPProjectResourcePlans], SPException
        + FullyQualifiedErrorId : Microsoft.Office.Project.Server.Cmdlet.PSCmdletMigrateResourcePlans
     
    Id                 : 579a018e-5281-4f49-97d6-0edf6eb81337
    ServiceApplication : PsiServiceApplication Name=Project Web Application Application Service
    ParentWebApp       : SPWebApplication Name=Project Web Application
    Url                : http://ProjectServer/PWA2
    SiteId             : 579a018e-5281-4f49-97d6-0edf6eb81337
    Lcid               : 1033
    AdminAccount       : i:0#.w|domain\user
    Database           : SPContentDatabase Name=SP_Projects_ContentDB
    DatabaseServer     : SP-DATABASE
    DatabaseName       : SP_Projects_ContentDB
    ProvisioningResult : Successful
    Online             : True
    InReadOnlyMode     : False

    RuleName  : ProjectBICenterExistenceHealthRule
    TimeStamp : 2018/12/07 5:48:10 PM
    Message   : ProjectBICenter exists for all the Project sites.
    Status    : Passed
    Results   : 

    RuleName  : ProjectRDBUserViewsRepairableHealthRule
    TimeStamp : 2018/12/07 5:48:10 PM
    Message   : The RDB User Views are valid
    Status    : Passed
    Results   : 

    RuleName  : ProjectWorkspacesExistenceHealthRule
    TimeStamp : 2018/12/07 5:48:10 PM
    Message   : All projects have workspace webs.
    Status    : Passed
    Results   : 

    RuleName  : QueueJobs
    TimeStamp : 2018/12/07 5:48:10 PM
    Message   : 
    Status    : Passed
    Results   : {Server01, Server01, Server01, Server01...}

    RuleName  : QueueMissingTriggers
    TimeStamp : 2018/12/07 5:48:10 PM
    Message   : Number of unprocessed jobs in Queue: 0.
    Status    : Passed
    Results   : 

    RuleName  : QueueStaleServerGroups
    TimeStamp : 2018/12/07 5:48:10 PM
    Message   : All Queue Groups OK.
    Status    : Passed
    Results   : 

    Test-SPProjectServiceApplication : exception encountered with rule Microsoft.Office.Project.Server.HealthRules.DatabasePermissionsRule for psi service application 
    Project Web Application Application Service
    At line:81 char:1
    + Test-SPProjectServiceApplication -Identity $ProjectServiceApp
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidResult: (Microsoft.Offic...PermissionsRule:DatabasePermissionsRule) [Test-SPProjectServiceApplication], InvalidOperationException
        + FullyQualifiedErrorId : Microsoft.Office.Project.Server.Cmdlet.PSCmdletCheckProjectServiceApplicationHealth
     
    RuleName  : CalcServiceWorkerState
    TimeStamp : 2018/12/07 5:48:40 PM
    Message   : All worker instances OK.
    Results   : {Server01, Server01, Server01, Server01...}
    Status    : Passed

    RuleName  : QueueInFlightJobs
    TimeStamp : 2018/12/07 5:49:10 PM
    Message   : All queue job status OK.
    Results   : {}
    Status    : Passed

    RuleName  : QueueServiceInternalState
    TimeStamp : 2018/12/07 5:49:41 PM
    Message   : All queue job counts OK..
    Results   : {CurrentQueueLength, AvailableQueueSlots}
    Status    : Passed
    Friday, December 7, 2018 7:16 PM
  • several things I see

    !) once a migration fail, it requires deleting the content database and restoring the backup content database

    2) the same content database cannot be restore twice by renaming one database

    3) the script does not have any error checking or check if the step has already been done


    Michael Wharton, Project MVP, MBA, PMP and a Great Guy <br/> Website http://www.WhartonComputer.com <br/> Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Saturday, December 8, 2018 1:55 AM
    Moderator
  • So I dropped all the databases. Deleted the Project service. Deleted the web application. Started from scratch.

    After a fresh database cross load from the 2013 environment to the 2016. I created the Project Server Service Application and ran the script you shared.

    There is 1 content database, and 3 Project databases that get cross loaded. I am able to migrate successfully 2 of the 3 Project databases. It's just this one project database that errors out.  

    Migrate-SPProjectDatabase : Error encountered while migrating project data in Content database. Action 16.0.34.0 of Microsoft.Office.Project.Server.Upgrade.PSDatabaseSequence failed. At line:62 char:1 + Migrate-SPProjectDatabase -SiteCollection $SitePwaURL -DatabaseServer ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OperationStopped: (Microsoft.Offic...ProjectDatabase:PSCmdletMigrateSPProjectDatabase) [Migrate-SPProjectDatabase], SPException + FullyQualifiedErrorId : Microsoft.Office.Project.Server.Cmdlet.PSCmdletMigrateSPProjectDatabase
    • Edited by Zuhair Khan 8 hours 15 minutes ago added more details about the 3 project databases
    8 hours 34 minutes ago