We recently ran into an issue attempting a reporting database rebuild for a customer.  We were receiving the customary duplicate key insert errors which are staples in requiring a reporting DB rebuild.  Unfortunately when we attempted the rebuild we received the error below.  Although we found an article on Brian Smith’s blog that had some similarities I decided to dig a bit deeper into the issue and indeed check the workflow metadata items (EPT, Phases, Stages).  When checking via SQL queries I could certainly see oddities where data elements were not being populated in the reporting database.  After some trial and error I was able to get the DB to rebuild successfully.  It should be noted this environment was significantly behind with cumulative updates.  We therefore applied them immediately in order to stabilize the system.


GeneralQueueJobFailed (26000) – ReportingWorkflowMetadataSync.ReportWorkflowMetadataSyncMessage. Details: id=’26000′ name=’GeneralQueueJobFailed’ uid=’ec262d1a-9c4d-4930-9a6c-386853cb9ffe’ JobUID=’91aa758f-df14-4e7a-96d2-679a7741c365′ ComputerName=’SFOWPMSQL12′ GroupType=’ReportingWorkflowMetadataSync’ MessageType=’ReportWorkflowMetadataSyncMessage’ MessageId=’1′ Stage=”. For more details, check the ULS logs on machine SFOWPMSQL12 for entries with JobUID 91aa758f-df14-4e7a-96d2-679a7741c365.


We opened each entity related to workflow, made a small change, then saved them.  Then looked at the queue to ensure the jobs that updated these elements ran successfully.  We also had to perform the updates in the order below, else they would fail as it appeared there are dependencies.

  • Enterprise Project Types (EPT)
  • Phases
  • Stages

Once we confirmed all queue jobs finished successfully we initiated a reporting database rebuild.  this time it ran successfully.