workflow faulting

Hi,

For some reason, on one particular machine we run workflow on, i cant get anything to "stick" in workflow. I'm able to get an instance into workflow, but shortly after this, i get the below tracking detail which shows that the workflow is faulting. How do i find out exactly what's going on? thanks.

Symyx.Workflow.StateMachineTrackingChannel [(null)] - Tracking detail: Activity: 'SymyxBasicWorkflow' Faulting

Symyx.Workflow.StateMachineTrackingChannel [(null)] - Tracking detail: Activity: 'Start' Canceling

Symyx.Workflow.StateMachineTrackingChannel [(null)] - Tracking detail: Activity: 'Start' Closed

Symyx.Workflow.StateMachineTrackingChannel [(null)] - Tracking detail: Activity: 'SymyxBasicWorkflow' Closed

Symyx.Workflow.StateMachineTrackingChannel [(null)] - Tracking detail: **** Workflow Instance Completed or Terminated ****

[1288 byte] By [Steve1999] at [2008-1-10]
# 1

you can do multiple things here

1. Handle WorkflowTerminated event on the WorkflowRuntime in the host. WorkflowTerminatedEventArgs property of the handler will contain exception details which caused the workflow to terminate.

2. Enable tracing. This will dump detailed information about execution states of the workflow and the exception information in the log file. Tracing can be enaled by adding following in the app.config

<configuration>
<system.diagnostics>
<switches>
<add name="System.Workflow LogToTraceListeners" value="1" />

<add name="System.Workflow.Runtime.Hosting" value="All" />

<add name="System.Workflow.Runtime" value="All" />

<add name="System.Workflow.Runtime.Tracking" value="All" />

<add name="System.Workflow.Activities" value="All" />

</switches>
<trace autoflush="true" indentsize="4">
<listeners>
<add name="customListener"
type="System.Diagnostics.TextWriterTraceListener"
initializeData="WFTrace.log" />
</listeners>
</trace>
</system.diagnostics>
</configuration>

3. Debug the workflow using VS.

SonaliC at 2007-10-3 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
# 2
Yeah..Trace Output might helps u find the problem. I also suggest you to deploy the workflow MAP in GAC and see u are getting the same error. because, it helped me for one of my state level workflow.
JeevaS at 2007-10-3 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...

Software Development for Windows Vista

Site Classified