Problems with Tutorial Lab03/Ex02/Task02

Did what you suggested. Dropped the 2 DBs, created them and ran the scripts from the directory you listed using QueryAnalyzer. Re-built the code using static string connectionString = "Initial Catalog=TrackingStore;Data Source=localhost\\Tutorial; Integrated Security=SSPI;"; and ended up with the same results, hanging on waitHandle.WaitOne();.

Everytime I run the app, I see a new entry in TrackingStore.WorkflowInstance, so I know that data is going in. I don't see any data being inserted into the other tables on a per run basis, only first run data like in the table: Type.

I downloaded all Runtimes, SDKs, Labs on this past Monday. Here is the versions

Add/Remove Programs - Support Info
Labs for WWF Beta 2 - v1.0.0
VS 2005 Extenstions WWF - v3.0.3603.4
WinFX Runtime Components 3.0 - Beta 2

Webbert at 2007-9-3 >

The Completed\Excerise2 works for me as well. The problem with that is that it is Task 03 and not Task 02 which is where my problem is. In Task 03 the waitHandle.WaitOne() is removed. This is where I am hanging.

I opened up the Completed\Excercise2 and made the following changes which effectively takes it back to Task 02 and ran the program again which caused the problem that I am describing.

static string connectionString = "Initial Catalog=TrackingStore;" +

"Data Source=localhost\\Tutorial; Integrated Security=SSPI;";

static void Main(string[] args)

{

WorkflowRuntime workflowRuntime = new WorkflowRuntime();

//workflowRuntime.AddService(new SharedConnectionWorkflowTransactionService(connectionString));

workflowRuntime.AddService(new SqlTrackingService(connectionString));

//workflowRuntime.AddService( new SqlWorkflowPersistenceService( connectionString, true, new TimeSpan( 0, 0, 0, 10, 0 ), new TimeSpan( 0, 0, 0, 10, 0 ) ) );

//workflowRuntime.AddService( new DefaultWorkflowSchedulerService() );

AutoResetEvent waitHandle = new AutoResetEvent(false);

workflowRuntime.WorkflowCompleted += delegate(object sender, WorkflowCompletedEventArgs e) {waitHandle.Set();};

workflowRuntime.WorkflowTerminated += delegate(object sender, WorkflowTerminatedEventArgs e)

{

Console.WriteLine(e.Exception.Message);

waitHandle.Set();

};

// =================================

// ADDED

// =================================

WorkflowInstance instance = workflowRuntime.CreateWorkflow( typeof( DefaultSQLServices.SimpleWorkflow ) );

instance.Start();

instance.Suspend( "Reason we are suspending the workflow." );

instance.Resume();

waitHandle.WaitOne();

GetInstanceTrackingEvents( instance.InstanceId );

Console.WriteLine( "Workflow Completed - press ENTER to continue" );

Console.Read();

// =================================

// REMOVED

// =================================

//workflowRuntime.WorkflowLoaded += new EventHandler<WorkflowEventArgs>(workflowRuntime_WorkflowLoaded);

//workflowRuntime.WorkflowIdled += new EventHandler<WorkflowEventArgs>(workflowRuntime_WorkflowIdled);

//workflowRuntime.WorkflowPersisted += new EventHandler<WorkflowEventArgs>(workflowRuntime_WorkflowPersisted);

//workflowRuntime.WorkflowUnloaded += new EventHandler<WorkflowEventArgs>(workflowRuntime_WorkflowUnloaded);

//for (int workflowCount = 0; workflowCount < 5; workflowCount++)

//{

// WorkflowInstance simpleWorkflowInstance = workflowRuntime.CreateWorkflow(typeof(DefaultSQLServices.SimpleWorkflow));

// simpleWorkflowInstance.Start();

//}

//System.Threading.Thread.Sleep(new TimeSpan(0, 0, 20));

// =================================

// END CHANGES

// =================================

Console.WriteLine("Workflow Completed - press ENTER to continue");

Console.Read();

}

Webbert at 2007-9-3 >

If you are using the sqltracking and sqlpersistence together and they use the same database, then you should use the SharedConnectionWorkflowCommitWorkBatchService. Then you should make sure the two services are using the same connection string and that they match the connection string for this service.

If you are not using the same database for the persistence and tracking services, then use the DefaultWorkflowCommitWorkBatchService (the default if you don't configure one) and configure the connection strings independently on the two services.

Matt

MattMilner-Pluralsight at 2007-9-3 >