none
Project Server 2010 - Project site object creation failed after upgrading from PS 2007 RRS feed

  • Question

  • Hi together,

    we are preparing to upgrade a customer system from PS 2007 to PS 2010. We are doing several migration loops on a test environment to document all necessary steps before migrating the productive system.

    As we have a lot of Project Sites we are going to do a full database attach upgrade (WSS_Content + Project Server dbs). So far we did the first migration on test and all went well - WSS_Content was upgraded and PWA provisioned based on the WSS_Content and the restored Project Server dbs.

    Now we deleted everything (PWA deleted, WSS_Content removed, Project Server dbs deleted) and wanted to start from scratch. So far, we again successfully upgraded the WSS_Content. But if we now try to provision the PWA, we are getting the "Failed - See the Application event log" message.

    The Application log tells there are 3 errors:

    Event ID:      6051
    Task Category: Provisioning
    Level:         Error
    Description: ProjectSite not created.

    Date:          08.12.2011 16:06:35
    Event ID:      6962
    Task Category: Provisioning
    Level:         Error
    Keywords:     
    User:          username
    Computer:      AppServer
    Description:
    Provisioning 'PWA': Project site object creation failed. Exception '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)
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.CreateSite(ProjectProvisionSettings provset)'.

    Log Name:      Application
    Source:        Microsoft-SharePoint Products-Project Server
    Date:          08.12.2011 16:06:35
    Event ID:      6971
    Task Category: Provisioning
    Level:         Error
    Keywords:     
    User:          username
    Computer:      Appserver
    Description:
    Failed to provision site PWA with 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)
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.CreateSite(ProjectProvisionSettings provset)

    First, I don't understand why it is failing after the first migration went smoothly.

    Second, can anyone tell me what exactly might be the issue behind these errors? It's as if the communication suddenly fails - why is there a Reference set to null...?

    Can anyone help?

    Thursday, December 8, 2011 3:37 PM

Answers

  • Hi there,

    we resolved the issue. :-)

    After our first test migration (which worked fine) we recognized that because of the backup/restore of the databases all our old P12 productive service accounts were still registered as logins for the databases and as we are using new service accounts for the P14 environment we deleted them. No problem so far.

    As course of our lessons learned for our second test migration we restored the databases and deleted the P12 service accounts from the 4 Project Server databases before doing the migration. It seems the system didn't like that (the new service accounts are used for migration, but somehow he needs the information in the security of the databases - don't ask me why).

    As soon as we restored the 4 Project DBs a second time and did the migration without deleting the logins beforehand it worked fine.

    Regards,

    Gáski

    • Marked as answer by Gáski Monday, December 12, 2011 8:19 AM
    Monday, December 12, 2011 8:18 AM

All replies

  • Hello. I have same issue.
    Thursday, December 8, 2011 5:41 PM
  • Hello Gaski,

    Generally object reference error is related to SQL server, you may need to try to provision another PWA with new databases, if it works then you may need to restore Project databases one more time and try to provision the PWA.

    Reviewing ULS log may also give some additional information.

     

    Thanks,

    Hrishi Deshpande

     

    Thursday, December 8, 2011 6:01 PM
    Moderator
  • Hi Hrishi,

    thanks. We already tried to provision other PWAs without a database migration, that worked fine.

    The ULS log only shows that there's a difference between provisioning a new PWA and provisioning based on the migrated PWA - the latter is much shorter, less entries than creating a completely new one. But there's no hint whatsoever to why it is failing - at least I didn't see one.

    Regards,

    Gáski

     

    Monday, December 12, 2011 7:39 AM
  • Hi there,

    we resolved the issue. :-)

    After our first test migration (which worked fine) we recognized that because of the backup/restore of the databases all our old P12 productive service accounts were still registered as logins for the databases and as we are using new service accounts for the P14 environment we deleted them. No problem so far.

    As course of our lessons learned for our second test migration we restored the databases and deleted the P12 service accounts from the 4 Project Server databases before doing the migration. It seems the system didn't like that (the new service accounts are used for migration, but somehow he needs the information in the security of the databases - don't ask me why).

    As soon as we restored the 4 Project DBs a second time and did the migration without deleting the logins beforehand it worked fine.

    Regards,

    Gáski

    • Marked as answer by Gáski Monday, December 12, 2011 8:19 AM
    Monday, December 12, 2011 8:18 AM
  • Hi,

    A server restart resolve this error for me.

    Regards,

    Anthony


    Anthony Picot

    Tuesday, July 30, 2013 9:54 AM
  • Try with new web application.


    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    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.

    Tuesday, July 30, 2013 1:04 PM
    Moderator
  • Hi

    I just had the same error after recreating a web application, mounting the existing content database and trying to recreate the PWA site in a 2010 environment.

    No change after config wizard. But the reboot did the trick...

    Regards

    Christoph


    Christoph Muelder | Senior Consultant, MCSE, MCT | SOLVIN information management GmbH, Germany


    Friday, August 9, 2013 9:11 PM