Migrating from Server to Server provisioning PWA with same name failed RRS feed

  • Question

  • Hi all,

    am trying to migrate from a server to another one, on the same domain and same users.

    I restore all DBs including the wss Content DB.

    but when I provision pwa instance with the same name "PWA" as the old server I get the below error, if I create another instance using the same DBs but with different name "PWA2" it works fine.

    the error:

    System.NullReferenceException: Object reference not set to an instance of an object.    
    at Microsoft.SharePoint.SPSite..ctor(Guid id, SPFarm farm, SPUrlZone zone, SPUserToken userToken)    
    at Microsoft.SharePoint.SPSite..ctor(Guid id)    
    at Microsoft.Office.Project.Server.Administration.ProjectSite..ctor(Guid webAppId, Guid siteId, String adminName, Int32 lcid, Boolean needsUpgrade, PsiServiceApplication parent)    
    at Microsoft.Office.Project.Server.Administration.ProjectSiteCollection.Add(Guid webAppId, Guid siteId, String adminName, Int32 lcid, String PubDBConnString, String VerDBConnString, String WorkDBConnString, String RepDBConnString, Boolean needsUpgrade) 

    any suggestions?

    Twitter : @MShoubaki |

    Monday, July 23, 2012 1:04 PM

All replies

  • Hello Mohammad,

    This is a generic error message. you might be able to dig down more by enabling the verbose logging  for the project site from SharePoint 2010 Central Administration.

    Basically these error messages while provisioning might be due to custom fields or custom workflows which might be used in the old PWA environment.


    Shiva Prasad B C

    Friday, August 24, 2012 9:19 PM
  • Thanks Shiva,

    I dont this its because of custom workflows or fields.

    because when I provision with new name like "PWA2" it works fine.

    I think its sharepoint and site collection problem.

    Twitter : @MShoubaki |

    Friday, August 24, 2012 9:32 PM
  • hi there,

    did you remove and re-attach wss_content DB ?

    u have to remove and recreate WebApp, attach "old" wss_content (if possible)


    nguyễn dương phú

    Monday, August 27, 2012 6:52 PM
  • Hi nguyễn dương phú

    my steps were:

    1.Create web app

    2. restore the old content_DB

    3. attached the DB to the web application.

    4.tried to provision project web access. the error :)

    is this the right order? or any missing step?

    Twitter : @MShoubaki |

    Tuesday, August 28, 2012 9:17 AM
  • It may be that during the provisioning process your new server is detecting the PWA site on the old server. 

    I had a similar issue where I removed Project and Sharepoint from a server then reinstalled.  When attempting to provision a PWA site of the same name as it has previously been it failed with a similar error (I was installing 2007).  On investigation I found that the original PWA site still existed on the server, removing it from IIS  resolved the problem.

    That may not be viable for you if you want to keep your existing installation up and running, but maybe disabling IIS on that machine temporarily might help, or at least let you test the theory.


    Tuesday, August 28, 2012 9:38 AM
  • Thanks John,

    but they are two separate servers, so the two URLS will be different, for example:



    so if the new server detects the old, why should we have a problem?

    Twitter : @MShoubaki |

    Tuesday, August 28, 2012 10:22 AM
  • Good point

    Maybe a combination of the url name part (PWA) and the site UID might cause a conflict.  Since provisioning it under a new name works.


    Tuesday, August 28, 2012 10:45 AM
  • Dear shobaki

    My order:

      • Create new WebApp(same old one)
      • Remove content DB
      • Restore old content DB
      • Create new PWA (same old name)
      • Use sql delete 4DB (published draft archive and reporting)
      • Restore old 4DB
      • Reconfig farm

    i will explaint why have i to do exactly those steps later if u need

    Nguyễn Dương Phú

    Wednesday, August 29, 2012 10:30 AM
  • will try these steps and let you know.


    Twitter : @MShoubaki |

    Wednesday, August 29, 2012 10:36 AM
  • Its due to the conflict with the existing PWA (orphaned) instance

    Check the configuration database :

    select siteid from wss_content.dbo.webs where fullurl='pwa'
    select * from objects where name='site ID'

    If the site collection ID is already mapped with the PWA instance, then you will not be able to provision the PWA using the same site collection.

    There are two options:

    1. Create the PWA using different site collection

    2. Remove the old PWA site collection entry from the configuration database (Create support incident with MS)

    Cheers. Happy troubleshooting !!! Sriram E - MSFT Enterprise Project Management

    Thursday, August 30, 2012 4:02 AM
  • Hi Sriram, 

    This is another  logical thinking, I think its the closest to my case.

    I cant follow  option one becase the client is asking for it in the same sitecollection.

    i option 2, I will try to investigate it myself, u mean the sharepoint config db, right|?

    Twitter : @MShoubaki |

    Thursday, August 30, 2012 8:04 PM