none
Project Server 2013 - Cannot Create Site RRS feed

  • Question

  • When creating and publishing a project, Project Server is set up to create a site URL as part of the process. Since the middle part of this week 12/16/14 this functionality stopped working and we need it to be working.

    Here are the error messages and logs pulled from Project Server and SharePoint Central Admin

    Project Server Manage Queue Jobs

    Queue:?GeneralQueueJobFailed (26000) - CreateWssSite.CreateWssSiteMessage. Details: id='26000' name='GeneralQueueJobFailed' uid='5461af96-1787-e411-80e9-001dd8b71f51' JobUID='aa2d518a-1787-e411-80e9-001dd8b71f51' ComputerName='bbe43e90-a923-40ac-8ca7-e8953ab95807' GroupType='CreateWssSite' MessageType='CreateWssSiteMessage' MessageId='1' Stage='' CorrelationUID='9722d79c-33d8-a082-9580-749b949e39eb'. For more details, check the ULS logs on machine bbe43e90-a923-40ac-8ca7-e8953ab95807 for entries with JobUID aa2d518a-1787-e411-80e9-001dd8b71f51.

    ULS Logs from SharePoint

    Standard Information:PSI Entry Point: <unknown>

    Project User: <unknown>

    Correlation Id: <unknown>

    PWA Site URL:

    SA Name: <unknown>

    PSError: <unknown>

    A queue job has failed. This is a general error logged by the Project Server Queue everytime a job fails - for effective troubleshooting use this error message with other more specific error messages (if any), the Operations guide (which documents more details about queued jobs) and the trace log (which could provide more detailed context). More information about the failed job follows. GUID of the failed job: aa2d518a-1787-e411-80e9-001dd8b71f51. Name of the computer that processed this job: bbe43e90-a923-40ac-8ca7-e8953ab95807 (to debug further, you need to look at the trace log from this computer). Failed job type: CreateWssSite. Failed sub-job type: CreateWssSiteMessage. Failed sub-job ID: 1. Stage where sub-job failed:  (this is useful when one sub-job has more than one logical processing stages).

    Any assistance you can provide at this point will be key as our services are impacted with this error.

    Monday, January 5, 2015 11:30 PM

All replies