none
Cannot create PWA RRS feed

  • Question

  • I have deleted PWA on project server and then delete the 4 associated databases. Then I try to create a new PWA but fail. The page shows that PWA URL and the 4 default database names have already been used. I wonder when I delete the PWA and the databases, some records are still in SQL and so I cannot reuse the names. So, how can I clear up the things and recreate PWA? Greatly need help!
    Wednesday, May 18, 2011 4:32 AM

Answers

  • Hi,

    You are correct, deleting the PWA through the site collection and deleting the PWA databases is most likely the cause of your issues. When you remove PWA this way, you don't unwire the various components, or remove any components that may be installed into the ConfigDB.

     

     


    Alex Burton
    www.epmsource.com | Twitter
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page
    Wednesday, May 18, 2011 10:07 AM
    Moderator
  • Type the following code to list all the pwa sites of the project server service application.
     
    PS C:\Users\spsservice> $psi=get-spserviceapplication | where {$_.TypeName -like
     "*Project*"}
    PS C:\Users\spsservice> $a=$psi.Sitecollection
    PS C:\Users\spsservice> $a

    PublishedDatabase           : ProjectDatabase Name=ProjectServer2_Published
    VersionsDatabase            : ProjectDatabase Name=ProjectServer2_Archive
    WorkingDatabase             : ProjectDatabase Name=ProjectServer2_Draft
    ReportingDatabase           : ProjectDatabase Name=ProjectServer2_Reporting
    EventHandlers               : Microsoft.Office.Project.Server.Schema.EventHandl
                                  ersDataSet
    CachedEventHandlers         : Microsoft.Office.Project.Server.Schema.EventHandl
                                  ersDataSet
    EventHandlersVersion        : 5090501c-86e2-4cfb-8217-fcabf9211197
    WebAppId                    : 2e938da4-c271-4a34-a826-bf60d425ec20
    SiteId                      : 07ad4b20-1d77-41c5-b2f0-e0c088fa655e
    AdminName                   : VIRTUALDOMAIN\spsservice
    Lcid                        : 1033
    ProvisionStatusText         : Provisioning job finished successfully.
    Provisioned                 : True
    PostProvisionIncomplete     : False
    ReportCenterProvisioned     : True
    CanRenameOnRestore          : False
    CanSelectForBackup          : True
    CanSelectForRestore         : True
    DiskSizeRequired            : 0
    Name                        : SharePoint - 80:PWA2
    CanUpgrade                  : True
    IsBackwardsCompatible       : True
    NeedsUpgradeIncludeChildren : True
    NeedsUpgrade                : True
    UpgradeContext              : Microsoft.SharePoint.Upgrade.SPUpgradeContext
    TypeName                    : Microsoft.Office.Project.Server.Administration.Pr
                                  ojectSite
    DisplayName                 : 07ad4b20-1d77-41c5-b2f0-e0c088fa655e
    Id                          : f192370c-ae32-41ee-b80c-c267378ee6e6
    Status                      : Online
    Parent                      : PsiServiceApplication Name=Project Server Service
                                   Application
    Version                     : 408382
    Properties                  : {}
    Farm                        : SPFarm Name=SharePoint_Config
    UpgradedPersistedProperties : {}
     

    Find the siteid of the pwa that is deleted through the delete site collection and enter the code below with that siteid in order to delete it completely.

     
    PS C:\Users\spsservice> $psi=get-spserviceapplication | where {$_.TypeName -like
     "*Project*"}
    PS C:\Users\spsservice> $a=$psi.Sitecollection | where {$_.SiteID -eq "07ad4b20-
    1d77-41c5-b2f0-e0c088fa655e"}
    PS C:\Users\spsservice> $a

    PublishedDatabase           : ProjectDatabase Name=ProjectServer2_Published
    VersionsDatabase            : ProjectDatabase Name=ProjectServer2_Archive
    WorkingDatabase             : ProjectDatabase Name=ProjectServer2_Draft
    ReportingDatabase           : ProjectDatabase Name=ProjectServer2_Reporting
    EventHandlers               : Microsoft.Office.Project.Server.Schema.EventHandl
                                  ersDataSet
    CachedEventHandlers         : Microsoft.Office.Project.Server.Schema.EventHandl
                                  ersDataSet
    EventHandlersVersion        : 5090501c-86e2-4cfb-8217-fcabf9211197
    WebAppId                    : 2e938da4-c271-4a34-a826-bf60d425ec20
    SiteId                      : 07ad4b20-1d77-41c5-b2f0-e0c088fa655e
    AdminName                   : VIRTUALDOMAIN\spsservice
    Lcid                        : 1033
    ProvisionStatusText         : Provisioning job finished successfully.
    Provisioned                 : True
    PostProvisionIncomplete     : False
    ReportCenterProvisioned     : True
    CanRenameOnRestore          : False
    CanSelectForBackup          : True
    CanSelectForRestore         : True
    DiskSizeRequired            : 0
    Name                        : SharePoint - 80:PWA2
    CanUpgrade                  : True
    IsBackwardsCompatible       : True
    NeedsUpgradeIncludeChildren : True
    NeedsUpgrade                : True
    UpgradeContext              : Microsoft.SharePoint.Upgrade.SPUpgradeContext
    TypeName                    : Microsoft.Office.Project.Server.Administration.Pr
                                  ojectSite
    DisplayName                 : 07ad4b20-1d77-41c5-b2f0-e0c088fa655e
    Id                          : f192370c-ae32-41ee-b80c-c267378ee6e6
    Status                      : Online
    Parent                      : PsiServiceApplication Name=Project Server Service
                                   Application
    Version                     : 408382
    Properties                  : {}
    Farm                        : SPFarm Name=SharePoint_Config
    UpgradedPersistedProperties : {}
     
    PS C:\Users\spsservice> $a.Delete()

    Verify that it is deleted.


    PS C:\Users\spsservice> $a=$psi.Sitecollection | where {$_.SiteID -eq "07ad4b20-
    1d77-41c5-b2f0-e0c088fa655e"}
    PS C:\Users\spsservice> $a
    PS C:\Users\spsservice>
     

    Delete the Project Server Service Application and recreate a new one. You can then create PWA again!

     

    • Marked as answer by Nahcyrret Saturday, May 21, 2011 3:21 PM
    Saturday, May 21, 2011 3:20 PM

All replies

  • Hello,

    Did you check if the Timer service is working in your farm? Also, make sure check if the Databases are not existing in SQL server & theer is no other PWA instance running with the database names as mentioned by you.

    Check if that might be useful:

    http://social.technet.microsoft.com/Forums/en-CA/projserv2010setup/thread/af6cde83-4bd7-4295-b48d-0cba137da077

    Lets us know the outcome.

    Thanks,

    Amit Khare

    Wednesday, May 18, 2011 5:14 AM
  • I do not find the following database role in SQL 2008 R2.

    RSExecRole

    SQLAgentOperatorRole

    SQLAgentReadRole

    SQLAgaentUserRole

    I wonder my action of deleting PWA through delete site collection is causing this error. I remember when I delete the 4 databases, they are locked and cannot be deleted. Only when I try to bring the databases offline and can then be deleted. I see in the sharepoint server event log that shows cannot open database "ProjectServer_Published" requested by the login. The login failed. I am afraid that something is left on sharepoint that constantly access the deleted databases. Nightmare!

     

    Wednesday, May 18, 2011 9:13 AM
  • When I try to backup sharepoint, the following errors show that sharepoint still know that 4 deleted databases. I think I had not deleted the PWA records completely through the delete site collection, so when I try to create a new PWA, it keep on saying the database names and the PWA URL have been used.

    If that is going to cause error, SharePoint should prevent me from doing this. Isn't it a big trouble to fix afterward?

     

    Backup Errors

    ProjectServer_Published  Error 5/18/2011 3:54 PM Object ProjectServer_Published failed in event OnBackup. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    SqlException: Cannot open database "ProjectServer_Published" requested by the login. The login failed.
    Login failed for user 'DOMAIN\mossfarmadmin'.
     
    ProjectServer_Draft  Error 5/18/2011 3:54 PM Object ProjectServer_Draft failed in event OnBackup. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    SqlException: Cannot open database "ProjectServer_Draft" requested by the login. The login failed.
    Login failed for user 'DOMAIN\mossfarmadmin'.
     
    ProjectServer_Archive  Error 5/18/2011 3:54 PM Object ProjectServer_Archive failed in event OnBackup. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    SqlException: Cannot open database "ProjectServer_Archive" requested by the login. The login failed.
    Login failed for user 'DOMAIN\mossfarmadmin'.
     
    ProjectServer_Reporting  Error 5/18/2011 3:54 PM Object ProjectServer_Reporting failed in event OnBackup. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    SqlException: Cannot open database "ProjectServer_Reporting" requested by the login. The login failed.
    Login failed for user 'DOMAIN\mossfarmadmin'.

    Wednesday, May 18, 2011 9:36 AM
  • Fixing an orphaned Site Collection within Project Server 2010

    February 24, 2011 by Mark Rhodes 1 Comment

    I had the pleasure of getting to know Project Server 2010 a couple of months ago.  I am a big fan of the way this has been implemeneted, as a SharePoint 2010 Service Application based approach seems to make more sense than a completely seperate product.

    During this installation I found out a few interesting things about Project Server :

    1. Do not try using Claim Based Authentication on your Project Server Web Application. It may look like it is working, but I assure you it is not.  Clicking around some of the less obvious areas of the site will probably reveal it is not working.
    2. Never, ever delete a /PWA Site Collection for any reason.  They look just like a normal SharePoint Site Collection, but doing this will leave you with an orphaned PWA site and will leave you scratching your head.  This also implies that PWA site collections cannot be backed up and restored by conventional SharePoint Site Collection Backups.
    3. If you try to convert Claims back to Classic mode (which is not supported), you will likely just break your PWA instance.

    There is no really clear cut way to recover from an orphaned Site Collection, and it becomes a real pain as you cannot retract the PWA Service Application until you fix the orphaned Site Collection.

    The short verison is it can be done with PowerShell with the following script :

    $psi = get-spserviceapplication | where {$_.TypeName -like “*Project*”}
    $a = $psi.Sitecollection | where {$_.SiteID -eq “0ce62ac4-d733-483f-b60b-ea7e75b104d4″}
    $a
    $a.Delete()
    $a = $psi.Sitecollection | where {$_.SiteID -eq “0ce62ac4-d733-483f-b60b-ea7e75b104d4″}
    $a

    Anyone has this experience and know that the above script can help to clear the orphaned PWA site collection?

     

    Wednesday, May 18, 2011 10:03 AM
  • Hi,

    You are correct, deleting the PWA through the site collection and deleting the PWA databases is most likely the cause of your issues. When you remove PWA this way, you don't unwire the various components, or remove any components that may be installed into the ConfigDB.

     

     


    Alex Burton
    www.epmsource.com | Twitter
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page
    Wednesday, May 18, 2011 10:07 AM
    Moderator
  • The site collection object has properties including the 4 database and PWA names. Hopefully by deleting it, I can clear the orphaned and free up project. But I need to know the deleted PWA SiteID first.
    Wednesday, May 18, 2011 1:38 PM
  • I find that no matter how I change the project web app path, the error always shows that the project web app site path is invalid, correct path and try again. This also happens when I create a whole new project server service application to create the project web app site.

    Is there a simple powershell cmdlet to get the orphaned PWA SiteID?

    Thursday, May 19, 2011 11:13 AM
  • $psi = get-spserviceapplication | where {$_.TypeName -like “*Project*”}
    $a = $psi.Sitecollection | where {$_.SiteID -eq “0ce62ac4-d733-483f-b60b-ea7e75b104d4″}
    $a
    $a.Delete()
    $a = $psi.Sitecollection | where {$_.SiteID -eq “0ce62ac4-d733-483f-b60b-ea7e75b104d4″}
    $a

    Is the above going to help? How to find the siteid of the deleted PWA site?

    What is the minimum action to fix this and to get project up and running again??

    Or I have no hope, need to reinstall the whole sharepoint and project server? Greatly need help!

     


    Thursday, May 19, 2011 6:02 PM
  • Type the following code to list all the pwa sites of the project server service application.
     
    PS C:\Users\spsservice> $psi=get-spserviceapplication | where {$_.TypeName -like
     "*Project*"}
    PS C:\Users\spsservice> $a=$psi.Sitecollection
    PS C:\Users\spsservice> $a

    PublishedDatabase           : ProjectDatabase Name=ProjectServer2_Published
    VersionsDatabase            : ProjectDatabase Name=ProjectServer2_Archive
    WorkingDatabase             : ProjectDatabase Name=ProjectServer2_Draft
    ReportingDatabase           : ProjectDatabase Name=ProjectServer2_Reporting
    EventHandlers               : Microsoft.Office.Project.Server.Schema.EventHandl
                                  ersDataSet
    CachedEventHandlers         : Microsoft.Office.Project.Server.Schema.EventHandl
                                  ersDataSet
    EventHandlersVersion        : 5090501c-86e2-4cfb-8217-fcabf9211197
    WebAppId                    : 2e938da4-c271-4a34-a826-bf60d425ec20
    SiteId                      : 07ad4b20-1d77-41c5-b2f0-e0c088fa655e
    AdminName                   : VIRTUALDOMAIN\spsservice
    Lcid                        : 1033
    ProvisionStatusText         : Provisioning job finished successfully.
    Provisioned                 : True
    PostProvisionIncomplete     : False
    ReportCenterProvisioned     : True
    CanRenameOnRestore          : False
    CanSelectForBackup          : True
    CanSelectForRestore         : True
    DiskSizeRequired            : 0
    Name                        : SharePoint - 80:PWA2
    CanUpgrade                  : True
    IsBackwardsCompatible       : True
    NeedsUpgradeIncludeChildren : True
    NeedsUpgrade                : True
    UpgradeContext              : Microsoft.SharePoint.Upgrade.SPUpgradeContext
    TypeName                    : Microsoft.Office.Project.Server.Administration.Pr
                                  ojectSite
    DisplayName                 : 07ad4b20-1d77-41c5-b2f0-e0c088fa655e
    Id                          : f192370c-ae32-41ee-b80c-c267378ee6e6
    Status                      : Online
    Parent                      : PsiServiceApplication Name=Project Server Service
                                   Application
    Version                     : 408382
    Properties                  : {}
    Farm                        : SPFarm Name=SharePoint_Config
    UpgradedPersistedProperties : {}
     

    Find the siteid of the pwa that is deleted through the delete site collection and enter the code below with that siteid in order to delete it completely.

     
    PS C:\Users\spsservice> $psi=get-spserviceapplication | where {$_.TypeName -like
     "*Project*"}
    PS C:\Users\spsservice> $a=$psi.Sitecollection | where {$_.SiteID -eq "07ad4b20-
    1d77-41c5-b2f0-e0c088fa655e"}
    PS C:\Users\spsservice> $a

    PublishedDatabase           : ProjectDatabase Name=ProjectServer2_Published
    VersionsDatabase            : ProjectDatabase Name=ProjectServer2_Archive
    WorkingDatabase             : ProjectDatabase Name=ProjectServer2_Draft
    ReportingDatabase           : ProjectDatabase Name=ProjectServer2_Reporting
    EventHandlers               : Microsoft.Office.Project.Server.Schema.EventHandl
                                  ersDataSet
    CachedEventHandlers         : Microsoft.Office.Project.Server.Schema.EventHandl
                                  ersDataSet
    EventHandlersVersion        : 5090501c-86e2-4cfb-8217-fcabf9211197
    WebAppId                    : 2e938da4-c271-4a34-a826-bf60d425ec20
    SiteId                      : 07ad4b20-1d77-41c5-b2f0-e0c088fa655e
    AdminName                   : VIRTUALDOMAIN\spsservice
    Lcid                        : 1033
    ProvisionStatusText         : Provisioning job finished successfully.
    Provisioned                 : True
    PostProvisionIncomplete     : False
    ReportCenterProvisioned     : True
    CanRenameOnRestore          : False
    CanSelectForBackup          : True
    CanSelectForRestore         : True
    DiskSizeRequired            : 0
    Name                        : SharePoint - 80:PWA2
    CanUpgrade                  : True
    IsBackwardsCompatible       : True
    NeedsUpgradeIncludeChildren : True
    NeedsUpgrade                : True
    UpgradeContext              : Microsoft.SharePoint.Upgrade.SPUpgradeContext
    TypeName                    : Microsoft.Office.Project.Server.Administration.Pr
                                  ojectSite
    DisplayName                 : 07ad4b20-1d77-41c5-b2f0-e0c088fa655e
    Id                          : f192370c-ae32-41ee-b80c-c267378ee6e6
    Status                      : Online
    Parent                      : PsiServiceApplication Name=Project Server Service
                                   Application
    Version                     : 408382
    Properties                  : {}
    Farm                        : SPFarm Name=SharePoint_Config
    UpgradedPersistedProperties : {}
     
    PS C:\Users\spsservice> $a.Delete()

    Verify that it is deleted.


    PS C:\Users\spsservice> $a=$psi.Sitecollection | where {$_.SiteID -eq "07ad4b20-
    1d77-41c5-b2f0-e0c088fa655e"}
    PS C:\Users\spsservice> $a
    PS C:\Users\spsservice>
     

    Delete the Project Server Service Application and recreate a new one. You can then create PWA again!

     

    • Marked as answer by Nahcyrret Saturday, May 21, 2011 3:21 PM
    Saturday, May 21, 2011 3:20 PM