Databases
StackOverflow2013
Postsdbo
POWhy do resume suspended workflow in AppFabric give errors?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy do resume suspended workflow in AppFabric give errors?
    primarykey
    data
    text
    <p>I'm running a couple of WF 4 services with Windows Server AppFabric. Sometimes an unhandled exception occurs in a workflow and it gets abandonded (if action on unhandled exception is set to "abandon"), or suspended (if action is set to "abandon and suspend").</p> <p>In the case of "abandon", the workflow is still "Running (active)" after the exception, and I expect AppFabric WorkflowManagementService to automatically continue the workflow from its last persisted point.</p> <p>In the case of "abandon and suspend", I excpet to be able to manually resume the workflow via the AppFabric Dashboard.</p> <p>In either case, this does not happen, but I get various error and warning messages in AppFabric Dashboard and Windows Event Viewer (Windows -> Application Server-System Services -> Admin):</p> <p>Error:</p> <blockquote> <p>Failed to invoke service management endpoint at 'net.pipe://jon-hp/Afis.Workflow/ServiceManagement.svc' to activate service '/Afis.Workflow/ATP.xamlx'.\rException: 'The open operation did not complete within the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout.'</p> </blockquote> <p>Error:</p> <blockquote> <p>Failed to Resume instance d626005a-63bd-4ab1-8192-62616755015c via control endpoint net.pipe://jon-hp/Afis.Workflow/ATP.xamlx/System.ServiceModel.Activities_IWorkflowInstanceManagement.\rException: System.TimeoutException: The open operation did not complete within the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout. Inner Exception: System.TimeoutException: The pipe connection was aborted because an asynchronous read from the pipe did not complete within the allotted timeout of 00:00:59.9989999. The time allotted to this operation may have been a portion of a longer timeout. Inner Exception: System.IO.PipeException: The operation cannot be completed because the pipe was closed. This may have been caused by the application on the other end of the pipe exiting..</p> </blockquote> <p>Warning (periodically every 20 minutes)</p> <blockquote> <p>WMS was not able to activate any of the hosts - backing off. Store name 'defaultSqlPersistenceStore' ('Root).</p> </blockquote> <p>Net.pipe is enabled for my web site and applications, and I can see the management endpoints listed in IIS Manager -> Endpoints -> Remove filter (System.ServiceModel.Activities.IWorkflowInstanceManagement).</p> <p>My application endpoints are running net.tcp with transport security and Windows authentication.</p> <p>This thread seems to be related, but I didn't manage to solve my problem from it: <a href="http://social.msdn.microsoft.com/Forums/en/dublin/thread/e1705e89-34cc-4526-b11e-9d67d66c403d" rel="nofollow">http://social.msdn.microsoft.com/Forums/en/dublin/thread/e1705e89-34cc-4526-b11e-9d67d66c403d</a></p> <p>EDIT 1: My scenario involves a client calling workflow A, which does some processing, then persists and returns. Workflow A then calls workflow B, and workflow B immediately throws an exception. Workflow A does not catch this, and is abandoned, but still Running (Active) from its last persistence point. Workflow B is also abandoned but has not been persisted, so gets status Running (Idle), waiting from message from workflow A.</p> <p>I then expect workflow A to resume automatically and call workflow B again, but this does not happen.</p> <p>EDIT 2: The types of errors I get in the Event Log don't seem consistent. In periods, I don't get any errors, but I've also seen to following (in addition to the those above):</p> <p><code> Failed to Resume instance 032274d1-b6e6-4163-a33a-73bffc8da2cc via control endpoint net.pipe://jon-hp/Afis.Workflow/ATP.xamlx/System.ServiceModel.Activities_IWorkflowInstanceManagement.\rException: System.ServiceModel.FaultException: The execution of an InstancePersistenceCommand was interrupted because the instance '032274d1-b6e6-4163-a33a-73bffc8da2cc' has not yet been persisted to the instance store.. </code></p> <p><code> Failed to Resume instance d2b19a41-985e-4dc4-8fd1-955df2cde243 via control endpoint net.pipe://jon-hp/Afis.Workflow/Import.xamlx/System.ServiceModel.Activities_IWorkflowInstanceManagement.\rException: System.ServiceModel.FaultException: The execution of the InstancePersistenceCommand named {urn:schemas-microsoft-com:System.Activities.Persistence/command}LoadWorkflow was interrupted by an error.. </code></p> <p><code> Failed to invoke service management endpoint at 'net.pipe://jon-hp/Afis.Workflow/ServiceManagement.svc' to activate service '/Afis.Workflow/ATP.xamlx'.\rException: 'There was an error reading from the pipe: Unrecognized error 109 (0x6d).' </code></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjonsb
    1. USjonsb
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhy do resume suspended workflow in AppFabric give errors?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COdid you fix this? how?
      singulars
      1. POWhy do resume suspended workflow in AppFabric give errors?
      1. USPablo Castilla
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload