jkushiner

Is there anyone out there that is successfully persisting and tracking workflow data on a remote server I've had no problems doing this on my local machine. I'm attempting to point to another database server and am getting this error message:

System.InvalidOperationException: Workflow with id "9ff9b8b7-2243-4dfd-b606-a7daa88d9b16" not found in state persistence store.

I've checked all of the obvious things, remote connections being allowed, DTC turned on and running, etc. I've even opened port 135 through windows firewall and added dtc as an exception.

What am I missing !



Re: Windows Workflow Foundation Persistence Service with Remote SQL Server connection

Angel Azcarraga - MSFT

It doesn't matter to WF whether the database exists locally or remotely. Something fishy's happening here.

A couple things to check:

1) Your connection string - make sure everything's in order there.
2) Try a simple database update/query using ADO.NET and see if you're successful. Usually the problem will bubble up when you try something simple.

Let me know what you find.

Thanks,
Angel






Re: Windows Workflow Foundation Persistence Service with Remote SQL Server connection

Dave Britton - VERTIGO

It sounds like you could be running "old" instances of your workflow that could still be looking for your local machine.

Have you completely stopped your local SQL Server just to make sure Then the next thing I would do is run a Profile on your remote SQl Server to see what you might be getting.

Or, when you configured your services - you made sure that you had all the exact same settings IsTransactional, UnloadOnIdle etc..






Re: Windows Workflow Foundation Persistence Service with Remote SQL Server connection

jkushiner

Hi angel,

I was able to query my table using ADO.NET with no problems. I'm stumped!





Re: Windows Workflow Foundation Persistence Service with Remote SQL Server connection

jkushiner

Well, I ran everything with a fresh copy of the database with the exact same result. And I haven't changed any services or code, just the location of the database.





Re: Windows Workflow Foundation Persistence Service with Remote SQL Server connection

Angel Azcarraga - MSFT

Ok, one more thing - can you please try running one of our persistence samples http://msdn2.microsoft.com/en-us/library/ms741700.aspx

Try it locally (which should work as is), and then point to your remote database and try again.

Something fishy's going on here. : )

Thanks,
Angel






Re: Windows Workflow Foundation Persistence Service with Remote SQL Server connection

brb.1977

I will try that example and see how it goes. I should mention that I am on the beta version. I haven't yet installed .NET 3.0 as we are still working with .NET 2.0

I'll let you know how it works out.





Re: Windows Workflow Foundation Persistence Service with Remote SQL Server connection

Angel Azcarraga - MSFT

You aren't compromising any .NET 2.0 work by installing 3.0. .NET 3.0 is simply a set of libraries (WF, WCF, and WPF) built on top of 2.0. It does not supply any new versions of dll's in 2.0.

It will ensure that you are not running into old WF bugs and will allows us to better help you resolve your issue.

Thanks!
Angel






Re: Windows Workflow Foundation Persistence Service with Remote SQL Server connection

jkushiner

Angel:

I got it. I had been calling instance.TryUnload() to persist the workflow instance. I tried calling Unload() instead and got the exception information returned from the persistence service. Essentially, it came down to a DTC problem. I had to follow the directions in this post here to enable DTC:

http://www.dotnetjunkies.com/Weblog/default.aspx GroupID=371

Once I did that on my local machine as well as the database server, I was back in business.

Thanks for all your help.

John