none
Migrating to project server 2013 RRS feed

  • Question

  • Hi,

    I am new to the whole migration process and am attempting to migrate project server 2010 to 2013 in a test environment.

    When I attempt to mount the project web app database to the PWA instance (in Project Server 2013) using the cmdlet mount-spprojectwebinstance  I get the error message  "Project site is currently in use"

    I tried several things to resolve the issue and searched on-line for solutions but had no luck. 

    Any suggestions are appreciated. 

    thanks,

    MP11MP11

    Monday, April 28, 2014 8:09 PM

Answers

  • Actually, I get this now. You don't create one because you're moving an existing one over.  It gets added when you attach the content DB from the 2010 system. I'm not sure what I did wrong when I tried not creating one, but certainly you shouldn't create the PWA instance manually if you plan to migrate from 2010.

    Elli J Project Solutions Specialist Blog: http://projectserverpants.wordpress.com/

    Wednesday, August 6, 2014 6:30 PM
  • It looks like a PWA with the same is already created with the same name or you have attached similar content DB on a different Web App As well.

    In case this is a new setup and you are testing a migration, how about removing all the previously created PWA and the content DB (if they are not used) and perform the migration from start.

    You can follow the below steps for the same

    # Must run this section if executing script outside of Sharepoint 2013 Management Shell
    Add-PSSnapin Microsoft.Sharepoint.Powershell


    # Update these upgrade variables to match your environment
    $dbservername = "SQL34332"
    $contentdbname = "2010_WSS_Content"
    $archivedbname = "2010_Archive"
    $draftdbname = "2010_Draft"
    $publisheddbname = "2010_Published"
    $reportingdbname = "2010_Reporting"
    $p15dbname = "UpgradePWALab"
    $webapp = "http://SPPS:81/"
    $projectsitecollection = "http://SPPS:81/PWA"
    $adminaccount = "contoso\farmadmin"

    #----- SharePoint upgrade process starts -----#

    # Recommended : Test-SPContentDatabase
    Test-SPContentDatabase `
    -Name $contentdbname `
    -WebApplication $webapp `
    -ServerInstance $dbservername

    # Review the results and fix any upgrade blocking issues.

    # Mount-SPContentDatabase (Mount does an upgrade too)
    Mount-SPContentDatabase `
    -Name $contentdbname `
    -WebApplication $webapp `
    -Databaseserver $dbservername `
    -NoB2BSiteUpgrade

    # Taking ownership of the site collection we want to upgrade
    Set-SPSite `
    -Identity $projectsitecollection `
    -SecondaryOwnerAlias $adminaccount

    # If migrating from Windows classic authentication to claims
    # Migrate the users to Claims (http://msdn.microsoft.com/en-us/library/ee554321.aspx)
    (Get-SPWebApplication $webapp).MigrateUsers($true)

    # Recommended : Test-SPSite
    Test-SPSite $projectsitecollection

    # Review the results and fix any upgrade blocking issues.

    # Upgrade SPSite
    Upgrade-spsite `
    -Identity $projectsitecollection `
    -VersionUpgrade

    #----- SharePoint upgrade process ends -----#


    #----- Project upgrade process starts -----#

    # Convert databases to 15
    Convertto-SPProjectDatabase `
    -WebApplication $webapp `
    -Dbserver $dbservername `
    -ArchiveDbname $archivedbname `
    -DraftDbname $draftdbname `
    -PublishedDbname $publisheddbname `
    -ReportingDbname $reportingdbname `
    -ProjectServiceDbname $p15dbname 

    #-Lcid 1033  Commented this out, no longer required in the RTM build 
    # 1033 is for English - United States. Use other codes for other languages (http://msdn.microsoft.com/en-us/goglobal/bb964664.aspx)

    # Mount Project database
    Mount-SPProjectDatabase `
    -Name $p15dbname `
    -WebApplication $webapp `
    -Databaseserver $dbservername

    # Upgrade Project database
    Upgrade-SPProjectDatabase `
    -Name $p15dbname `
    -WebApplication $webapp `
    -Databaseserver $dbservername 

    # Mount Project web instance
    Mount-SPProjectWebInstance `
    -DatabaseName $p15dbname `
    -SiteCollection $projectsitecollection `
    -DatabaseServer $dbservername

    # Upgrade Project web instance
    Upgrade-SPProjectWebInstance `
    -Identity $projectSitecollection

    # Enable PWA features
    Enable-SPFeature `
    -Identity pwasite `
    -Url $projectSitecollection

    #----- Project upgrade process ends -----#


    Cheers! Happy troubleshooting !!! Dinesh S. Rai - MSFT Enterprise Project Management

    Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you. This can be beneficial to other community members reading the thread.


    Wednesday, August 6, 2014 8:57 PM
    Moderator

All replies

  • There may a step or two that you missed during the migration.  Check out Channel 9 and Project Conference. There were two good session on migration.

    http://channel9.msdn.com/Events/Project/2014/PC319

    Cheers!


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Tuesday, April 29, 2014 1:33 AM
    Moderator
  • Hi,

    Is there al a PWA site already made? That can explain the error.

    With Kind Regards, 

    Robin Kruithof


    Technical Consultant EPM

    Thursday, May 1, 2014 1:27 PM
  • Hello Robin,

    Yes, I have made a PWA site prior to migration. The way I understand the migration is that we need a PWA site created so that I can migrate the 2010 databases to the new site. Not sure if my understanding is wrong.

    Thank you very much,

    Meghna

    Tuesday, May 6, 2014 2:03 PM
  • Hello Michael,

    I had a look at the video and followed the instructions closely but unfortunately am still running into the same issue. Though I greatly appreciate your help!

    Thanks,

    Meghna

    Tuesday, May 6, 2014 2:04 PM
  • Please provide the PowerShell command that failed and the exact error message.

    Cheers


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Wednesday, May 7, 2014 12:40 AM
    Moderator
  • Hi,

    The cmdlet is: mount-spprojectwebinstance -databasename ProjectWebAppdb -sitecollection "Placed the site collection here" -databaseserver "database name"

    Error message:

    mount-spprojectwebinstance : Project site is currently in use.

    At line:1 char:1

    *mount-spprojectwebinstance -databasename ProjectWebAppdb -sitecollection http:// ....

    *~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    *categoryInfo :OperationStopped: <Microsoft.offic...ountPwaInstance:PSCmdletMountPwaInstance> {Mount-SPProjectWebInstance}, SPException

    *FullyQualifiedErrorId:Microsoft.Office.Project.Server.Cmdlet.PsCmdletMountPwaInstance

    Thanks

    Wednesday, May 7, 2014 1:38 PM
  • This error explains that the Web App you are trying to use for mounting is already in use by previous provisioning or already in use, suggested would be to either delete the existing PWA application and by my experience i would say delete the web app as well and recreate it and then use it for provisioning new PWA, but easiest would be to create a new web app and use it for migration 


    Thanks | Sunil Kr Singh | http://epmxperts.wordpress.com

    Wednesday, May 7, 2014 2:21 PM
    Moderator
  • Hello Sunil,

    Here are the steps I followed:

    1. I created a SharePoint Site collection

    2. created my project web app instance in the site collection

    When I create the PWA instance it also provisions it. I thought that I will need to create a PWA prior to migration so that I can mount the 2010 database to it. Please advice if this is not the case.

    Thanks

    Wednesday, May 7, 2014 3:01 PM
  • Hi MP11MP11

    By point 1&2 i am assuming that's the PWA you created earlier, for your last question, Yes you are right, that's what i would do is create a web app and mount DB on that 


    Thanks | Sunil Kr Singh | http://epmxperts.wordpress.com

    Wednesday, May 7, 2014 4:31 PM
    Moderator
  • I am getting the same result - everything works fine through all the steps until I try to mount the consolidated database to the web app in this step.  I have tried twice (by starting over completely) with the same result. 

    I'm confused about the replies here because there's nothing in the instructions to indicate that you shouldn't create a PWA instance first, and when I try to run through the steps without having a PWA created, it fails with the error that it can't find the SPSite object.... plus, you already have to have a PWA created for the Upgrade-SPSite cmdlet earlier in the process, anyway.

    Is there some kind of secret instruction or magical assumption missing here? 


    Elli J Project Solutions Specialist Blog: http://projectserverpants.wordpress.com/

    Wednesday, August 6, 2014 5:39 PM
  • Actually, I get this now. You don't create one because you're moving an existing one over.  It gets added when you attach the content DB from the 2010 system. I'm not sure what I did wrong when I tried not creating one, but certainly you shouldn't create the PWA instance manually if you plan to migrate from 2010.

    Elli J Project Solutions Specialist Blog: http://projectserverpants.wordpress.com/

    Wednesday, August 6, 2014 6:30 PM
  • It looks like a PWA with the same is already created with the same name or you have attached similar content DB on a different Web App As well.

    In case this is a new setup and you are testing a migration, how about removing all the previously created PWA and the content DB (if they are not used) and perform the migration from start.

    You can follow the below steps for the same

    # Must run this section if executing script outside of Sharepoint 2013 Management Shell
    Add-PSSnapin Microsoft.Sharepoint.Powershell


    # Update these upgrade variables to match your environment
    $dbservername = "SQL34332"
    $contentdbname = "2010_WSS_Content"
    $archivedbname = "2010_Archive"
    $draftdbname = "2010_Draft"
    $publisheddbname = "2010_Published"
    $reportingdbname = "2010_Reporting"
    $p15dbname = "UpgradePWALab"
    $webapp = "http://SPPS:81/"
    $projectsitecollection = "http://SPPS:81/PWA"
    $adminaccount = "contoso\farmadmin"

    #----- SharePoint upgrade process starts -----#

    # Recommended : Test-SPContentDatabase
    Test-SPContentDatabase `
    -Name $contentdbname `
    -WebApplication $webapp `
    -ServerInstance $dbservername

    # Review the results and fix any upgrade blocking issues.

    # Mount-SPContentDatabase (Mount does an upgrade too)
    Mount-SPContentDatabase `
    -Name $contentdbname `
    -WebApplication $webapp `
    -Databaseserver $dbservername `
    -NoB2BSiteUpgrade

    # Taking ownership of the site collection we want to upgrade
    Set-SPSite `
    -Identity $projectsitecollection `
    -SecondaryOwnerAlias $adminaccount

    # If migrating from Windows classic authentication to claims
    # Migrate the users to Claims (http://msdn.microsoft.com/en-us/library/ee554321.aspx)
    (Get-SPWebApplication $webapp).MigrateUsers($true)

    # Recommended : Test-SPSite
    Test-SPSite $projectsitecollection

    # Review the results and fix any upgrade blocking issues.

    # Upgrade SPSite
    Upgrade-spsite `
    -Identity $projectsitecollection `
    -VersionUpgrade

    #----- SharePoint upgrade process ends -----#


    #----- Project upgrade process starts -----#

    # Convert databases to 15
    Convertto-SPProjectDatabase `
    -WebApplication $webapp `
    -Dbserver $dbservername `
    -ArchiveDbname $archivedbname `
    -DraftDbname $draftdbname `
    -PublishedDbname $publisheddbname `
    -ReportingDbname $reportingdbname `
    -ProjectServiceDbname $p15dbname 

    #-Lcid 1033  Commented this out, no longer required in the RTM build 
    # 1033 is for English - United States. Use other codes for other languages (http://msdn.microsoft.com/en-us/goglobal/bb964664.aspx)

    # Mount Project database
    Mount-SPProjectDatabase `
    -Name $p15dbname `
    -WebApplication $webapp `
    -Databaseserver $dbservername

    # Upgrade Project database
    Upgrade-SPProjectDatabase `
    -Name $p15dbname `
    -WebApplication $webapp `
    -Databaseserver $dbservername 

    # Mount Project web instance
    Mount-SPProjectWebInstance `
    -DatabaseName $p15dbname `
    -SiteCollection $projectsitecollection `
    -DatabaseServer $dbservername

    # Upgrade Project web instance
    Upgrade-SPProjectWebInstance `
    -Identity $projectSitecollection

    # Enable PWA features
    Enable-SPFeature `
    -Identity pwasite `
    -Url $projectSitecollection

    #----- Project upgrade process ends -----#


    Cheers! Happy troubleshooting !!! Dinesh S. Rai - MSFT Enterprise Project Management

    Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you. This can be beneficial to other community members reading the thread.


    Wednesday, August 6, 2014 8:57 PM
    Moderator
  • OK - after pulling my hair out for a day with this same issue...  Turns out you can't have a PWA2013 site provisioned on your 2013 Farm named the same as the site you are trying to upgrade from your 2010 Farm.  That sounds logical but it isn't obvious from all the steps that you should NOT create an upfront PWA Site to upgrade but that the Mount-SPContentDatabase command with the -NoB2BSiteUpgrade flag actually creates the initial site ON the Site collection.  So, you don't have to have a separate Site collection for PWA (like in 2010).  Once I deleted everything but my Top Level Site Collection at the Root, and ran the Mount-SPContentDatabase command - It created it. 

    David

    Friday, October 31, 2014 11:03 PM