none
Dispatcher failfast is causing the Workflow Manager backend to terminate RRS feed

  • 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()    --

    Friday, September 6, 2013 4:35 AM

Answers

All replies

  • Hi,

    I have seen a similar post from you, you had the workflow manager issue.

    You can take a look at the following thread:http://social.technet.microsoft.com/Forums/en-US/8495c3ee-fdba-405e-9955-c86a4e32a221/dispatcher-failfast-is-causing-the-workflow-manager-backend-to-terminate


    Jason Guo
    TechNet Community Support

    • Marked as answer by JasonGuo Monday, September 16, 2013 3:46 PM
    Wednesday, September 11, 2013 11:18 AM
  • 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: Check database table for workflow .. 

    insert the values in to database table.. (i was trying this also)

    Solution (resolution): The SharePoint to connect databases on the instance. Now, following 4 values must be set in the database "WFResourceManagementDB" in the table "WorkflowServiceConfig":

    INSERT INTO WorkflowServiceConfig VALUES('WorkflowServiceScopeSnapshotProcessBatchSize', '50')

    INSERT INTO WorkflowServiceConfig VALUES('WorkflowServiceScopeSnapshotProcessLoopInterval', '00:05:00')

    INSERT INTO WorkflowServiceConfig VALUES('WorkflowServiceSuspendedInstanceRetentionDuration', '00:30:00')

    INSERT INTO WorkflowServiceConfig VALUES('WorkflowServiceMaxInstanceCompressedSizeKB', '5120')

    ---------------Reboot again.......

    check workflow status  get-spwffarmstatus

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

    Troubleshooting steps  : Issues 
    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 358, 359, 19 and 10
    Checked Workflow Management Site through IIS:
    Site was started.  
    Checked Workflow Management Application Pool
    Pool was started.  Restarting 

    ----------More research on it no luck ----


    Deepesh Yevle - MCTS MCITP



    Thursday, December 3, 2015 6:12 PM