WorkflowCheckinNotify Error Microsoft Project Server 2013

I was receiving this error at a customer site recently.  They had no workflows setup in the system, although they did have all the necessary objects installed to deploy Project Server workflows.  In order to get around this issue I deployed a stateless workflow.  Steps are outlined below:

Queue:◦GeneralQueueJobFailed (26000) - WorkflowCheckinNotify.ProjectCheckinNotifyWorkflowMessage. Details: id='26000' name='GeneralQueueJobFailed' uid='285e76f4-9668-e611-944f-005056a12cd1' JobUID='6b18a9ec-9668-e611-944f-005056a12cd1' ComputerName='e933446d-3513-478e-9ead-6cb3035eaa0b' GroupType='WorkflowCheckinNotify' MessageType='ProjectCheckinNotifyWorkflowMessage' MessageId='1' Stage='' CorrelationUID='455b9c9d-b59b-60f4-1b8b-f8a2bc41cd2b'. For more details, check the ULS logs on machine e933446d-3513-478e-9ead-6cb3035eaa0b for entries with JobUID 6b18a9ec-9668-e611-944f-005056a12cd1.

• Create a single stage in Project Web App and add the appropriate PDPs to it

• Next create and deploy a workflow.  If you look at the screenshot you can see that all it does it
  1. Stage 1, log hello world to workflow history list
  2. Transition to stage: end of workflow

Next associate this workflow with your EPTs in use.  You should then no longer see this error in the queue

Related

• 2010 Solution Starter Workflow: Migration from Project Server 2010 to Project Server 2013
• How to set Project Custom Field value in workflow
• Using EPM Workflow Phases and Stages with Microsoft Project Server & Microsoft Project Online in Reporting–Tips and Tricks
• Unable to open Projects from PWA after migration to Microsoft Project Server 2013
• Project Server 2013 Workflow: Cannot Access Project UID in workflow