Loading persisted workflow instances with WorkflowApplication

When building workflows, you must consider the developer experience, available tools, long-term maintenance, and future versioning.

Matt Milner

MSDN Magazine May 2008

I have a Workflow that is using an InfoPath task form.  In the "FormEvents_Loading" method event handler I have some code that needs to run each time the form is opened.   I recycle the App Pool and open the form the code runs perfectly, but if I close and try to re-open the form the code is not run at all.  I can then recycle the App Pool again and on the next load the code executes just fine.   The code that is supposed to be run is a very simple statement to set a field value, so I don't think it is interfering.

Does anyone know what this might be?

Thanks,
--Aaron

Hi,

I've created simple sequential workflow. It's only creates one task and is waiting in while loop until task is Approved. It works fine when I run only one instance of this workflow, but if I start another instance before first one is finished it gets stack and doesn't complete task an workflow stays in In Progress state forever.

Hi,

We are using WF 3.5 with a SqlWorkflowPersistenceService with the ownershipduration set at 2 hours and the loadingInternval at 1 hour.  We are finding that on certain occasions, rehydrated or attempts to rehydryate a persisted state results in some unusual behaviour. Of particular note, has been two of the same instance running and subsquently one fails (e.g. the first one removes data from a server, the second one attempts the same op -to remove the same data and subsquently fails becasue it was already removed by the first). In some cases, it almost resembes race conditions of two of the same instances!  Trying to replicate or reproduce the issue can be diffucult, but the closest I can get appears to be shortening the ownership interval in a running workflow instance resulting in

System.Workflow.Runtime.Hosting.PersistenceException: This workflow is not owned by the WorkflowRuntime. The WorkflowRuntime's ownership has expired, or another WorkflowRuntime owns the workflow.

but Im not sure if this is the problem.  Does this sound like an ownership issue with a particular workflow runtime? If so, I fail to see how two instances could run at once (I would have thought WD/Sql persistence server would prevent this from occurring)?

Any help would be greatly appreciated,

Thanks

B.

Hello!

Let's assume we would like to have a WindowsApplication which should be executing two WorkflowApplication instances within one transaction.

We could imagine a button click event handler which should:

1. Start the transaction.
2. Execute WorkflowApplication1.
3. Execute WorkflowApplication2.
4. Commit the transaction.

Should I just create a TransactionScope and somehow pass it to the WorkflowApplications? If yes, how to pass the TransactionScope to the WorkflowApplications, must this be done explicitly or is it done implicitly?

Best regards,

Henrik Dahl

We are using Workflow Foundation 4 Beta 2 with a client / server architecture where the client runs workflow through the server  using a WorkflowServiceHost. The client itself runs no workflow. The workflow is long running, requiring that it persist while awaiting user input. We have set up correlation and persistence such that the user can successfully move the workflow from one activity to another. The problem occurs when the workflow is unloaded or the server application is restarted; we are unable to determine how to continue a workflow that has been unloaded. We have looked at numerous samples such as the Hiring Request Process (http://msdn.microsoft.com/en-us/library/ee622985(VS.100).aspx) and the samples demonstrate the same issue…everything works great until the workflows are unloaded or the server (application running the workflowservicehost) is restarted. There is no exception thrown by the client call, the workflow simply doesn’t move forward.

Hi all, i found the below error in event log. How can i fix this issue.

Event ID: 6875            Source: Windows SharePoint Services 3

Error loading and running event receiver Microsoft.SharePoint.Workflow.SPWorkflowAutostartEventReceiver in Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Additional information is below.

: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

Please help me out in this issue. Thanks in advance.

Srikanth

K2Blackpearl, Sharepoint, .Net

Our app has this concept of being able to "embed" workflows inside other workflows.  So, we have a custom activity called EmbedWF.  In the EmbedWF's execute handler, we are essentially loading the XAML workflow definition of a particular workflow ... and then we need to invoke it, or run it. 

The parent workflow is hosted in a WorkflowApplication instance ... it uses persistance, navigation, etc.  The idea is that when it executes and comes to an instance of an EmbedWF activity, we want to then kick off that other embedded workflow. 

Is there a good way to do this? 

I've tried this (from the Execute event of the EmbedWF activity):

          WorkflowInvoker wfi = new WorkflowInvoker(activity);
          wfi.Extensions.Add(context.GetExtension<NavigationInformation>());
          wfi.Extensions.Add(context.GetExtension<EclpWorkFlowWindow>());
          IDictionary<string, object> resultArgs = wfi.Invoke(args);

But that's just causing the workflow application to hang when it's running UI activities.  I've also tried this:

context.ScheduleActi