none
Dispatcher failfast is causing the Workflow Manager backend to terminate

    Question

  • im receiving this error on our event log - workflow, with event ID 359: i tried to restart the IIS of the Workflow Server no Luck, and then did the restart of the workflow backend service, still the same and finally i restarted the whole production server. but still the below error is still popping up. please help on how you solve the issue below. i followed all the trouble shooting tips on this site": http://technet.microsoft.com/en-us/library/jj193529.aspx

    Dispatcher failfast is causing the Workflow Manager backend to terminate. Exception: System.AggregateException: The dispatcher failure rate has reached 11%. InnerException is the last failure; see traces for other failures. ---> System.Runtime.CallbackException: The call to OnRequestAbort on the WorkflowInstance 'a742053a-ed2c-496d-a103-0adfbd2d4437' threw an exception. This is considered fatal. See inner exception for details. ---> System.AggregateException: Should be processing if notifying about persistable idle. ---> System.NullReferenceException: Object reference not set to an instance of an object.    at System.Activities.Runtime.ActivityExecutor.CancelRootActivity()    at System.Activities.Hosting.WorkflowInstance.WorkflowInstanceControl.ScheduleCancel()    at Microsoft.Activities.Hosting.HostedWorkflowInstance.Cancel()    at Microsoft.Activities.Hosting.WorkflowSession.TryDispatchNextSubroutineWorkItem()    at Microsoft.Activities.Hosting.WorkflowSession.OnPaused(HostedWorkflowInstance pausedInstance)    at Microsoft.Activities.Hosting.HostedWorkflowInstance.ReleaseLock()    at Microsoft.Activities.Hosting.HostedWorkflowInstance.OnNotifyPaused()    at System.Activities.Runtime.ActivityExecutor.OnSchedulerIdle()    --

    Thursday, September 05, 2013 6:56 AM

Answers

  • Hi Jeff12.12.12,

    seems your workflow got stuck in somewhere in the process,

    perhaps you can elaborate me more detail regarding this,

    do this workflow is a custom workflow?

    is there any steps that we can try to reproduce the issue in our lab?

    is there any other error from the ULS log that you able to find regarding this workflows?

    please have a try to clean up the cache.ini,

    http://support.microsoft.com/kb/939308/en-us


    Regards,
    Aries
    Microsoft Online Community Support


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, September 11, 2013 11:11 AM

All replies

  • Hi,
    For this issue, I'm trying to involve someone familiar with this topic to further look at it.
    Thanks,

    Jason Guo
    TechNet Community Support

    Wednesday, September 11, 2013 8:26 AM
  • Hi Jeff12.12.12,

    seems your workflow got stuck in somewhere in the process,

    perhaps you can elaborate me more detail regarding this,

    do this workflow is a custom workflow?

    is there any steps that we can try to reproduce the issue in our lab?

    is there any other error from the ULS log that you able to find regarding this workflows?

    please have a try to clean up the cache.ini,

    http://support.microsoft.com/kb/939308/en-us


    Regards,
    Aries
    Microsoft Online Community Support


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, September 11, 2013 11:11 AM
  • Hi,

    Were you able to resolve the issue?

    I am having the same problem and none of my Workflows are working.

    The event viewer shows the same error as above.

    Please reply

    Tuesday, November 11, 2014 4:08 PM
  • 1 : Open IIS Manager.
    Under Application Pools, right-click WorkflowMgmtPool, and select Recycle… from the context menu.

    2 : Open a command prompt with administrator privileges.
    Execute the following command: net stop WorkflowServiceBackend
    Execute the following command: net start WorkflowServiceBackend

    3 : Reboot the server

    4 : Clearing the Cache on all boxes :  https://support.microsoft.com/en-us/kb/939308

    https://technet.microsoft.com/en-us/library/jj193529.aspx#ServerSetup

    --

    Troubleshooting
    Checked Workflow Manager services and related services:
    Service Bus Gateway
    Service Bus Message Broker
    Windows Fabric Host Service
    Workflow Manager Backend - repeatedly stopped and restarted; starting it (when stopped) did not resolve issue.
    Checked Windows Server Application log:
    Saw events 1000, 1026 and 7031
    Checked Microsoft Workflow logs
    Saw events ID : 358, events ID : 359, events ID :19 and events ID :10
    Checked Workflow Management Site through IIS:
    Site was started.  Restarting did not resolve issue.
    Checked Workflow Management Application Pool
    Pool was started.  Restarting it did not resolve issue

    --

    Finally : 

    the Fiexd the Issue update the latest CU for WF Client CU3

    We can directly install CU 3 for WFM: https://support.microsoft.com/en-us/kb/3104066

    The order of installation :

     Update WFM client https://support.microsoft.com/en-us/kb/3104066

    Update SB, https://support.microsoft.com/en-us/kb/2799752

    Update WFM https://support.microsoft.com/en-us/kb/3104066

    Make sure that we have the backup of the WFM and SB databases.


    Deepesh Yevle - MCTS MCITP






    • Proposed as answer by Deepesh Yevle Monday, December 14, 2015 7:40 PM
    • Edited by Deepesh Yevle Monday, December 14, 2015 10:24 PM Edit
    Thursday, December 03, 2015 6:18 PM
  • Before reinstalling WFM or messing with the config, see if you can locate the workflow instance shown in the error. We had this exact same issue and once we delete the problematic workflow instance (noted in the GUID) the error went away and the workflow service backend stopped crashing.
    Thursday, December 10, 2015 6:12 PM