Short answer: Restart the “Service Bus Gateway” and “Service Bus Message Broker” Service on the server where Workflow Manager is installed. But you didn’t come here for that did you? This has happened to me and a colleague so I thought that the solution is worth sharing. So here is the detailed description.
On Project Server 2013 On premises instance, all my projects were stuck in “Project Workflow Check-in” queue job and that job was failing after about 45 minutes. The queue error message was:
GeneralQueueJobFailed (26000) –WorkflowCheckinNotify.ProjectCheckinNotifyWorkflowMessage. Details: id=’26000′ name=’GeneralQueueJobFailed’ uid=’b3f897eb-4695-e411-80cd-000d3ad00e15′ JobUID=’c7c8744b-4295-e411-80cd-000d3ad00e15′ ComputerName=’8fa7e1bd-09b4-4c64-b019-57c33d5c769c’ GroupType=’WorkflowCheckinNotify’ MessageType=’ProjectCheckinNotifyWorkflowMessage’ MessageId=’1′ Stage=” CorrelationUID=’1af0dc9c-9e05-a05e-c769-ca04319a2489′. For more details, check the ULS logs on machine 8fa7e1bd-09b4-4c64-b019-57c33d5c769c for entries with JobUID c7c8744b-4295-e411-80cd-000d3ad00e15.
Interestingly, I wasn’t even using Workflows for my EPT. A common solution for this problem is to publish a dummy workflow via SharePoint Designer 2013 on Project Server instance but I had done it already. The error mentioned above started to appear after few weeks of instance provisioning.
During the troubleshooting, I was able to publish workflows from SharePoint designer but noticed that if I associate a workflow to an EPT, the projects started to fail even on project creation screen. This gave me a hint about issues with Workflow Manager.
I found out that Workflow Manager related services named “Service Bus Gateway” and “Service Bus Message Broker” on the server were stopped. Restarting the two services solved the issue for me.
I really hope you find this soloution useful. If you would like more from us please subscribe to our mailing list.