I was setting up a project server web access site, and trying to publish new project workspaces to the server via the project client. It would publish just fine, however, the workspace wouldn't get provisioned correctly. I took a look at the event log on the project server and saw this event:
Standard Information:PSI Entry Point:
Project User: CONTOSO\spservice
Correlation Id: df195c38-5203-4ep1-a1hc-36376i6fe03l
PWA Site URL: http://contoso.com/project
SSP Name: ContosoPortal_SSP
PSError: GeneralQueueJobFailed (26000)
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: 77f17dbd-4085-4aab-8dc0-8638b3f06c6d. Name of the computer that processed this job: EXTWA03 (to debug further, you need to look at the trace log from this computer). Failed job type: ReportingWSSSync. Failed sub-job type: WSSSyncMessageEx. Failed sub-job ID: 1. Stage where sub-job failed: (this is useful when one sub-job has more than one logical processing stages).
This event didn't do anything to help me, so I turned on verbose logging for the Project Server Queue category in central administration, operations. After verbose logging was enabled, I published again from the client which spewed a huge log. By searching on the project name, in this case "Phil", I found a more detailed error:
Possible mismatch between the reported error with code = 0x81070504 and message: "There is no Web named "/project/phil"." and the returned error with code 0x80070002.
Not much here either, however, after hitting search a few more times I noticed an error saying a feature file was missing. Turns out I had developed a custom feature for my workspace, and those feature files were not getting deployed to my project server, and was only getting deployed to my web front ends. I resolved the issue by enabling the application server service on the project server box. This deployed those feature files to the project server, because they were wrapped in a solution package. Now my projects publish perfectly!
It was a random issue – but maybe someone else in the WWW will benefit from what it took for me to resolve…
Phil