V
Vango
I currently have 1 Project Web Access Site running and in a Provisioned
state. We wanted to make another one for testing purposes and after a full
day of waiting the status is still currently at "Waiting for Resources".
When we created our first Project Web Access Site, the one that works and is
currently running, it went through almost immediately without any errors. I
searched through the diagnostic logs and can only find a few references of
the new Project Web Access site but still not sure why its hanging on Waiting
for Resources, has anyone else seen this? Or know of a way to clean out
that area so I can try and start over? There doesn’t seem like there is
anyway to delete the request to create the Project Web Access Site.
The server farm is a three tiered setup with 1 database server , 1
application server, and 1 webserver. Sharepoint Server is running at
version 2007 and Project Server is also 2007.
06/21/2007 12:59:08.40 OWSTIMER.EXE (0x0C04) 0x2EAC
Project Server Project Server Provisioning 6456
Information Scheduling Project Web Access instance provisioning job: Parent
Web Application GUID=275d2a44-2e60-4293-8b65-8fddc988953f, Site Path=Test3,
HostHeaderIsSiteName=False, Lcid=1033, Admin Account=Domain\Username,
Published=Data Source=SQLSERVER;Initial
Catalog=ProjectServer_TEST3_Published, Draft=Data Source=SQLSERVER;Initial
Catalog=ProjectServer_TEST3_Draft, Archive=Data Source=SQLSERVER;Initial
Catalog=ProjectServer_TEST3_Archive, Reporting=Data Source=SQLSERVER;Initial
Catalog=ProjectServer_TEST3_Reporting, Operation=Create
06/21/2007 12:59:08.40 OWSTIMER.EXE (0x0C04) 0x2EAC
Windows SharePoint Services Topology 8xqz Medium
Updating SPPersistedObject ProjectProvisionSettings
Name=601168f5-74fa-4670-837e-335367277607 Parent=SharedResourceProvider
Name=SharedServices1SSP1. Version: -1 Ensure: 0, HashCode: 4843707, Id:
7a854872-f304-4bc2-a804-c66c573c4629, Stack: at
Microsoft.SharePoint.Administration.SPPersistedObject.Update() at
Microsoft.SharePoint.Administration.SPPersistedObject.Update(Boolean ensure)
at Microsoft.SharePoint.Administration.SPPersistedChildCollection`1.Add(T
newObj, Boolean ensure) at
Microsoft.SharePoint.Administration.SPPersistedChildCollection`1.Add(T
newObj) at
Microsoft.Office.Project.Server.Administration.ProjectPSISharedApplication.SubmitCreateInstance(Guid
ParentWebAppGuid, String pwaPath, Boolean hostHeaderIsSiteName, Int32 lcid,
String adminAccount, String adminP...
06/21/2007 12:59:08.40* OWSTIMER.EXE (0x0C04) 0x2EAC
Windows SharePoint Services Topology 8xqz Medium
....assword, String publishedDbConnectionString, String
workingDbConnectionString, String versionsDbConnectionString, String
reportingDbConnectionString) at
Microsoft.Office.Project.Server.Administration.PWASSPSubmitSiteCreationTimerJob.Execute()
at Microsoft.Office.Server.Administration.JobHandler.Execute(Object
state, Boolean timedOut) at
System.Threading._ThreadPoolWaitOrTimerCallback.WaitOrTimerCallback_Context(Object
state, Boolean timedOut) at
System.Threading._ThreadPoolWaitOrTimerCallback.WaitOrTimerCallback_Context_t(Object
state) at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state) at
System.Threading._ThreadPoolWaitOrTimerCallback.PerformWaitOrTimerCallback(Object state, Boolean timedOut)
state. We wanted to make another one for testing purposes and after a full
day of waiting the status is still currently at "Waiting for Resources".
When we created our first Project Web Access Site, the one that works and is
currently running, it went through almost immediately without any errors. I
searched through the diagnostic logs and can only find a few references of
the new Project Web Access site but still not sure why its hanging on Waiting
for Resources, has anyone else seen this? Or know of a way to clean out
that area so I can try and start over? There doesn’t seem like there is
anyway to delete the request to create the Project Web Access Site.
The server farm is a three tiered setup with 1 database server , 1
application server, and 1 webserver. Sharepoint Server is running at
version 2007 and Project Server is also 2007.
06/21/2007 12:59:08.40 OWSTIMER.EXE (0x0C04) 0x2EAC
Project Server Project Server Provisioning 6456
Information Scheduling Project Web Access instance provisioning job: Parent
Web Application GUID=275d2a44-2e60-4293-8b65-8fddc988953f, Site Path=Test3,
HostHeaderIsSiteName=False, Lcid=1033, Admin Account=Domain\Username,
Published=Data Source=SQLSERVER;Initial
Catalog=ProjectServer_TEST3_Published, Draft=Data Source=SQLSERVER;Initial
Catalog=ProjectServer_TEST3_Draft, Archive=Data Source=SQLSERVER;Initial
Catalog=ProjectServer_TEST3_Archive, Reporting=Data Source=SQLSERVER;Initial
Catalog=ProjectServer_TEST3_Reporting, Operation=Create
06/21/2007 12:59:08.40 OWSTIMER.EXE (0x0C04) 0x2EAC
Windows SharePoint Services Topology 8xqz Medium
Updating SPPersistedObject ProjectProvisionSettings
Name=601168f5-74fa-4670-837e-335367277607 Parent=SharedResourceProvider
Name=SharedServices1SSP1. Version: -1 Ensure: 0, HashCode: 4843707, Id:
7a854872-f304-4bc2-a804-c66c573c4629, Stack: at
Microsoft.SharePoint.Administration.SPPersistedObject.Update() at
Microsoft.SharePoint.Administration.SPPersistedObject.Update(Boolean ensure)
at Microsoft.SharePoint.Administration.SPPersistedChildCollection`1.Add(T
newObj, Boolean ensure) at
Microsoft.SharePoint.Administration.SPPersistedChildCollection`1.Add(T
newObj) at
Microsoft.Office.Project.Server.Administration.ProjectPSISharedApplication.SubmitCreateInstance(Guid
ParentWebAppGuid, String pwaPath, Boolean hostHeaderIsSiteName, Int32 lcid,
String adminAccount, String adminP...
06/21/2007 12:59:08.40* OWSTIMER.EXE (0x0C04) 0x2EAC
Windows SharePoint Services Topology 8xqz Medium
....assword, String publishedDbConnectionString, String
workingDbConnectionString, String versionsDbConnectionString, String
reportingDbConnectionString) at
Microsoft.Office.Project.Server.Administration.PWASSPSubmitSiteCreationTimerJob.Execute()
at Microsoft.Office.Server.Administration.JobHandler.Execute(Object
state, Boolean timedOut) at
System.Threading._ThreadPoolWaitOrTimerCallback.WaitOrTimerCallback_Context(Object
state, Boolean timedOut) at
System.Threading._ThreadPoolWaitOrTimerCallback.WaitOrTimerCallback_Context_t(Object
state) at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state) at
System.Threading._ThreadPoolWaitOrTimerCallback.PerformWaitOrTimerCallback(Object state, Boolean timedOut)