Errors creating a new Project Web App site RRS feed

  • Question

  • Hello,

    We currently have a SharePoint farm that contains SharePoint Server 2010 and Project Server 2010 on one machine, and SQL Server 2008 on another machine. Our company has been using SharePoint for a while now and we haven't had any issues with the SharePoint web applications. Recently we created a Project Server service application within Central Management, which appeared to have been completed without errors. However, when we tried to create a new Project Web App site, we kept getting the "no web applications were found in the farm" error. This is quite puzzling since the web applications are clearly there. The associated ULS entries include:

    01/16/2012 21:46:09.27  Microsoft.Office.Project.Server (0x2B50) 0x2ED4 Project Server                 General                        f5sw Verbose  [WaitMany] using WaitHandle.WaitAny to wait on 2 handles   
    01/16/2012 21:46:09.27  Microsoft.Office.Project.Server (0x2B50) 0x2ED4 Project Server                 General                        8zdb High     [SERVICE] ProjectEventService14: ProcessWatcher signaled  
    01/16/2012 21:46:09.27  Microsoft.Office.Project.Server (0x2B50) 0x2ED4 Project Server                 General                        8zdk High     [SERVICE] ProjectEventService14: ProcessWatcher restarting service for 558c1aa7-f852-4002-99bf-824cd91d8372 PID: -1  
    01/16/2012 21:46:09.27  Microsoft.Office.Project.Server (0x2B50) 0x2ED4 Project Server                 Provisioning                   8zdn Medium   [SERVICE] ProjectEventService14: Getting list of Sites for ServiceApp: 558c1aa7-f852-4002-99bf-824cd91d8372  
    01/16/2012 21:46:09.27  Microsoft.Office.Project.Server (0x2B50) 0x2ED4 Project Server                 General                        27o3 Verbose  [SERVICE] ProjectEventService14, ExecProcess.Cleanup, Stack:    at Microsoft.Office.Project.Server.Services.ExecProcess.Cleanup()     at Microsoft.Office.Project.Server.Services.ProcessWatcher.RestartExecServices()     at Microsoft.Office.Project.Server.Services.ProcessWatcher.ProcessWatcherThread()     at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)     at System.Threading.ThreadHelper.ThreadStart()    
    01/16/2012 21:46:09.27  Microsoft.Office.Project.Server (0x2B50) 0x2ED4 Project Server                 General                        8zd0 Medium   [SERVICE] ProjectEventService14: Not starting ExecProcess for ServiceApp: 558c1aa7-f852-4002-99bf-824cd91d8372  No sites defined 

    The GUID listed above is the Project Server service application.

    Does anybody have any clue on what we can do to get past this to at least create and provision a project web app site?

    Many thanks!


    Tuesday, January 17, 2012 4:14 AM

All replies

  • Hi Vivian,

    Just check you've selected correct Web Application, just navigate through the following

    Server Settings > Project Site Provisioning Settings > Site Url

    Hope this helps out.


    Thanks, Kashif
    Tuesday, January 17, 2012 7:59 AM
  • Hi there,

    Can you try via PowerShell:

    Do you have a Top level site in the web application where you are trying to provision the PWA site? Have you seen the TechNet guide?:



    Paul Mather | Twitter |
    Tuesday, January 17, 2012 10:54 AM
  • Hi,

    You need to create a top level site or a web application to provision project web access.

    So create a web application from Manage Web application then try to provision the project web access site.

    Tuesday, January 17, 2012 3:31 PM
  • Thanks for the responses. Unfortunately, we haven't had much luck. A few more details: We had a functioning PWA site prior to this, but about 2 weeks ago the SharePoint server went down. We did a restore job, but while that got our SharePoint sites back up and running, we noticed that none of the Project Server queue jobs was moving. After trying to fix that to no avail, we got to the point where we had to delete the old PWA site, recreate the Project Server service application, and provision a new PWA site. So, this is where we are. My previously stated problem was that for some reason none of the existing web applications was recognized. So, I created another top level site using a different port #. This time I was able to create a PWA site associated with the newly added web application. However, the provisioning job is stuck at "waiting for resources." I've reviewed all job statuses and there's nothing related to the provisioning job. All timer services are running as expected. This has now taken about 2 weeks and we haven't been able to pin-point the exact problems (the log entries haven't helped much). If we can't get this fixed, our last resort is to go back and rebuild the farm from scratch (*shivers*).
    • Edited by VivianQ Tuesday, January 17, 2012 6:50 PM
    Tuesday, January 17, 2012 6:48 PM