FIXED – Workflow Manager Backend – Error 1067 / HTTP 500

Recently I came across Workflow errors and resolved by manually executing TSQL to update Workflow Resource and Workflow Instance tables.  Wild but true.  The SQL files can be found on the C:\ drive of the Workflow Manager server.  After running SQL, the windows service promptly started.

Details below on the error symptom and resolution.  Cheers!  shades_smile

Error Symptoms

  1. Windows Service.  Error 1067 – The process terminated unexpectedly.
  2. HTTP 500 – Internal Server Error Occurred when opening http://workflow:12291 or https://workflow:12290 in a web browser
  3. Register-SPWorkflowService : An internal error occured. For more details, please see the server logs. Client ActivityId :3033487b-7c53-4f17-ae08-8516c2ec0bef.

Resolution

  1. RDP to Workflow Manager
  2. Open “C:\Program Files\Workflow Manager\1.0\Workflow\” folder
  3. Open file “wfServerUpgradePolicy.config” and look for <wfupgrade targetVersion=”1.3.0.0”>
  4. Open SQL and execute “SELECT * FROM [StoreVersionTable]” on [WFResourceManagementDB]
  5. Compare CONFIG file to to SQL table versions
    1. They mismatch.  This the root cause of errors above.
  6. Open “C:\Program Files\Workflow Manager\1.0\Workflow\” folder
  7. Execute SQL scripts to update
    1. WorkflowServiceInstanceManagementDBUpgradeScript.sql
    2. WorkflowServiceResourceManagementDBUpgradeScript.sql
  8. Register-SPWorkflowService -SPSite http://sharepoint -WorkflowHostUri http://workflowserver:12291 -AllowOAuthHttp -Force
  9. Test to verify

Error Screenshots

image

image

image

Resolution Screenshots

image

image

image

image

image

image

image

image

enter image description here

Reference

Return to Top ▲Return to Top ▲