Cannot replace Project Server 2007 instance to another server. What is wrong? RRS feed

  • Question

  • Hello!

    Let me present my problem:

    I have PWA site on one server. I make backup of the databases: 4 for project server (publish,archive...) and WSS_Content. I copy them to the target server and restore via SQL Server Management Studio. Next, go to the CentralAdministration, create new WebApp with restored content database. Next, create new SharedServices instance, and there try to create new PWA site. Unfortunately, I cannot create site with name PWA. Other names are OK, but PWA invokes warning that this site already exists. So, I can create PWA1, and this works, but I have no idea how to create PWA itself??

    Here: are 3 ways to do this replacement, and I do it via the first one. Can you help me and give advice what tool use, or maybe any other "trick" to do it correct?

    Thank you in advance, Paul

    Tuesday, August 17, 2010 12:45 PM


All replies

  • Hello PaulTheMe

    Are these two instances of PWA in the same SharePoint farm?  Are they in separate farms?  If in the same farm, this may explain why SharePoint central has already found PWA.  Or it could be an orphan site collection.

    Are the PWA instances in the same domain?  If not, then you will need to manage the security on SQL server with the new accounts.

    What you can do is attach the project and content databases, setup the proper security for the db and when you provision the PWA instance, point to the newly attached databases.


    Michael Wharton, MBA, PMP, MCT


    Sincerely, Michael Wharton, MBA, PMP, MCT, MCSD, MCSE+I, MCDBA
    Tuesday, August 17, 2010 3:11 PM
  • Hi PaulTheMe,

    The answer is you cannot re-create /PWA if you already have /PWA in your content database.  As you have discovered, you can create /PWA1 - and then you could use the site relinker tool to link back to your workspace which are still under /PWA.  If you really must have /PWA as your 'PWA' site then you would need to use on of the other options, such as restoring the content db on another web application, so you have your PWA site at http://server/pwa and your content under (for example) http://server:81/pwa.

    In 2010 we handle this better and you can provision to an exisiting /PWA site.

    Best regards,


    Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page
    Thursday, August 19, 2010 7:46 PM