locked
Workflow Foundation 4.5 change deployment server for running instances RRS feed

  • Question

  • Hello

    I'm facing a really big trouble.....this is what's happening, I hope you guys could help me.

    Using SSIS I'm starting new instances of a state machine workflow with instance store. but the endpoint for the workflow (actually it's expose through a workflow service) is my development machine, so in the service deployment table is addressing my development machine, but the application server is actually reading that database and trying to continue excecuting those intances, but I always get and error when i try to continue excecuting a workflow who started though the development machine, however if I start a new instance using the application server and try to continue excecuting that particular instance it works.......

    I try to change directly in the database in the instance table in order to use the other ServiceDeploymentId (of the application server) and it doesn´t work.

    In summary what I'm trying to do is using SSIS starting instances (in my development machine) and then in the application server continue with the excecution of those instances.....this is for a migration of data, but later I'll have to export the data to the produccion server.....so what I can see is that I can't continue executing a instance if that instance wasn't created in the same application server where is the workflow service hosted. Is there a way to adjust the data in the persistence store, to point to the server I wanna continue running the state machine workflow?

    Thanks a lot

    Friday, January 25, 2013 3:41 AM

All replies

  • Hi,

    Do you means you want to change the SQL workflow instance store ? If so, you could use SqlWorkflowInstanceStoreBehavior, a service behavior that allows you to conveniently change the SQL Workflow Instance Store properties through XML configuration. For WAS-hosted workflow services, use the Web.config file.

    Reference on: http://msdn.microsoft.com/en-us/library/ee395773.aspx

    Best Regards,


    Chen Yu
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Monday, January 28, 2013 8:10 AM
  • Hello

    Thank your for your response, but that's not what I mean, I've just discovered, that the problem is that the calculated correlation key is different........I don't know why is calculated different in each server..........the correlation that I'm using is query correlation.....

    Tuesday, January 29, 2013 11:38 PM