locked
"The Project Web App Site path is invalid. Correct path and try again." RRS feed

  • Question

  • Good Afternoon,

    We're currently fighting an issue with Project Server 2010.  Originally Project Server 2010 had been installed and configured successfully with the PWA site created (default location).  After some testing and hitting a wall where we were continually recieving a "Cannot connect ot server." error when attempting to access anything within PWA aside from Server Settings, Project Server 2010 was removed (most likely, the incorrect way).  After removal, the farm was updated with the wizard successfully.  Aftter reinstalling Project Server 2010 with the Microsoft documentation, when attempting to create a PWA site, we're recieving the above error, "The Project Web App Site path is invalid. Correct path and try again."  We've changed the databases utilized by Project Server so that they're not the default entries, but regardless of what we name the PWA instance, or where we put it, we still recieve this message.  At this point, we're at a loss.  Is there any documentation on successfully and correctly removing all of Project Server 2010?  I'd rather not have to recreate the entire farm, but at this point, we're almost out of options.

    Any assistance would be greatly appreciated.  Thanks.

    Brian

    Friday, October 15, 2010 8:35 PM

Answers

  • Turns out that the issue we were experiencing was actually due to the infrastructure; we have our SharePoint farm behind both Siteminder and TMG (ISA).  After tweaking the TMG rule, we were able to get around the afformentioned error.  Sorry for the late response, but thanks very much for your replies.

    Brian

    • Marked as answer by BT-JH Wednesday, October 27, 2010 4:18 PM
    Wednesday, October 27, 2010 4:18 PM

All replies

  • When you say "Project Server 2010 was removed (most likely, the incorrect way)" I am a bit concerned... What else does the ULS mentions?
    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
    Friday, October 15, 2010 9:27 PM
  • These are the majority of the errors being seen.  To further explain how this all was removed, we first deleted all Project Sites, then PWA, then removed Project Server from all of the servers and re-ran the SharePoint 2010 Products Configuration Wizard on all nodes.  After reinstalling, we're seeing the above issue.

    1. SQL Database 'ProjectServer_Archive' on SQL Server instance 'X\X' not found. Additional error information from SQL Server is included below. 

    Cannot open database "ProjectServer_Archive" requested by the login. The login failed. 

    Login failed for user 'DOMAIN\X'.

     

    2. Event 7626 (Project Server) of severity 'Critical' occurred 8 more time(s) and was suppressed in the event log. 

    3. Cannot start queue. SSP: b733f31c-73a2-4e53-8c93-050e8b55a0c4 SiteUID: 06d47695-8a5e-4c3f-bdce-a5ede85540e6 Url: Queue: TimesheetQ. 

    4. Cannot start queue. SSP: b733f31c-73a2-4e53-8c93-050e8b55a0c4 SiteUID: 06d47695-8a5e-4c3f-bdce-a5ede85540e6 Url: Queue: ProjectQ.

     

    Any help is greatly appreciated.  Thanks for your time.

     

    ULS clip now attached:

    [SPDelegateManager] [DEBUG] [10/18/2010 11:05:15 AM]: Begin registering Microsoft.Office.Project.Server.Upgrade, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. 
    10/18/2010 11:05:15.70  powershell.exe (0x149C)                  0x07C8 SharePoint Foundation          Upgrade                        fbv7 Medium   [powershell] [SPDelegateManager] [DEBUG] [10/18/2010 11:05:15 AM]: No assembly manifest found. 
    10/18/2010 11:05:15.74  powershell.exe (0x149C)                  0x07C8 SharePoint Foundation          Upgrade                        fbv7 Medium   [powershell] [SPDelegateManager] [DEBUG] [10/18/2010 11:05:15 AM]: Registering [Microsoft.Office.Project.Server.Upgrade.ProjectServiceSequence] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 5. 
    10/18/2010 11:05:15.74  powershell.exe (0x149C)                  0x07C8 SharePoint Foundation          Upgrade                        fbv7 Medium   [powershell] [SPDelegateManager] [DEBUG] [10/18/2010 11:05:15 AM]: Registering [Microsoft.Office.Project.Server.Upgrade.ProjectSiteSequence] for [Microsoft.Office.Project.Server.Administration.ProjectSite], Phase: 2147483647, Order: 5. 
    10/18/2010 11:05:15.74  powershell.exe (0x149C)                  0x07C8 SharePoint Foundation          Upgrade                        fbv7 Medium   [powershell] [SPDelegateManager] [DEBUG] [10/18/2010 11:05:15 AM]: Registering [Microsoft.Office.Project.Server.Upgrade.PsiServiceApplicationSequence] for [Microsoft.Office.Project.Server.Administration.PsiServiceApplication], Phase: 2147483647, Order: 5. 
    10/18/2010 11:05:15.74  powershell.exe (0x149C)                  0x07C8 SharePoint Foundation          Upgrade                        fbv7 Medium   [powershell] [SPDelegateManager] [DEBUG] [10/18/2010 11:05:15 AM]: Registering [Microsoft.Office.Project.Server.Upgrade.ProjectSharedResourceProvider12Sequence] for [Microsoft.Office.Server.Upgrade.SharedResourceProvider12], Phase: 2147483647, Order: 5. 
    10/18/2010 11:05:15.74  powershell.exe (0x149C)                  0x07C8 SharePoint Foundation          Upgrade                        fbv7 Medium   [powershell] [SPDelegateManager] [DEBUG] [10/18/2010 11:05:15 AM]: Registering [Microsoft.Office.Project.Server.Upgrade.SPFarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 5. 
    10/18/2010 11:05:15.74  powershell.exe (0x149C)                  0x07C8 SharePoint Foundation          Upgrade                        fbv7 Medium   [powershell] [SPDelegateManager] [DEBUG] [10/18/2010 11:05:15 AM]: Registering [Microsoft.Office.Project.Server.Upgrade.SPIisWebSiteProjectSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 5. 
    10/18/2010 11:05:15.74  powershell.exe (0x149C)                  0x07C8 SharePoint Foundation          Upgrade                        fbv7 Medium   [powershell] [SPDelegateManager] [DEBUG] [10/18/2010 11:05:15 AM]: Registering [Microsoft.Office.Project.Server.Upgrade.SPServerProjectSequence] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 5. 
    10/18/2010 11:05:15.74  powershell.exe (0x149C)                  0x07C8 SharePoint Foundation          Upgrade                        fbv7 Medium   [powershell] [SPDelegateManager] [DEBUG] [10/18/2010 11:05:15 AM]: Registering [Microsoft.Office.Project.Server.Upgrade.SPSiteProjectSequence] for [Microsoft.SharePoint.SPSite], Phase: 0, Order: 5. 
    10/18/2010 11:05:15.74  powershell.exe (0x149C)                  0x07C8 SharePoint Foundation          Upgrade                        fbv7 Medium   [powershell] [SPDelegateManager] [DEBUG] [10/18/2010 11:05:15 AM]: Registering [Microsoft.Office.Project.Server.Upgrade.PublishedDatabaseSequence] for [Microsoft.Office.Project.Server.Administration.ProjectDatabase], Phase: 2147483647, Order: 5. 
    10/18/2010 11:05:15.74  powershell.exe (0x149C)                  0x07C8 SharePoint Foundation          Upgrade                        fbv7 Medium   [powershell] [SPDelegateManager] [DEBUG] [10/18/2010 11:05:15 AM]: Registering [Microsoft.Office.Project.Server.Upgrade.ReportingDatabaseSequence] for [Microsoft.Office.Project.Server.Administration.ProjectDatabase], Phase: 2147483647, Order: 5. 
    10/18/2010 11:05:15.74  powershell.exe (0x149C)                  0x07C8 SharePoint Foundation          Upgrade                        fbv7 Medium   [powershell] [SPDelegateManager] [DEBUG] [10/18/2010 11:05:15 AM]: Registering [Microsoft.Office.Project.Server.Upgrade.VersionsDatabaseSequence] for [Microsoft.Office.Project.Server.Administration.ProjectDatabase], Phase: 2147483647, Order: 5. 
    10/18/2010 11:05:15.74  powershell.exe (0x149C)                  0x07C8 SharePoint Foundation          Upgrade                        fbv7 Medium   [powershell] [SPDelegateManager] [DEBUG] [10/18/2010 11:05:15 AM]: Registering [Microsoft.Office.Project.Server.Upgrade.WorkingDatabaseSequence] for [Microsoft.Office.Project.Server.Administration.ProjectDatabase], Phase: 2147483647, Order: 5. 
    10/18/2010 11:05:15.74  powershell.exe (0x149C)                  0x07C8 SharePoint Foundation          Upgrade                        fbv7 Medium   [powershell] [SPDelegateManager] [DEBUG] [10/18/2010 11:05:15 AM]: End registering Microsoft.Office.Project.Server.Upgrade, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. 
    10/18/2010 11:05:15.74  powershell.exe (0x149C)                  0x07C8 SharePoint Foundation          Upgrade                        fbv7 Medium   [powershell]

     

    Brian

    Monday, October 18, 2010 1:30 PM
  • Hi BT-JH

    What vesion of you SQL Server?Install the latest server-pack first,I have also had similar problems


    I sale myself ONLY half CNY!
    Tuesday, October 19, 2010 8:58 AM
  • Turns out that the issue we were experiencing was actually due to the infrastructure; we have our SharePoint farm behind both Siteminder and TMG (ISA).  After tweaking the TMG rule, we were able to get around the afformentioned error.  Sorry for the late response, but thanks very much for your replies.

    Brian

    • Marked as answer by BT-JH Wednesday, October 27, 2010 4:18 PM
    Wednesday, October 27, 2010 4:18 PM