Re: BizTalk Orchestration terminated Suddenly

Home Page Forums BizTalk 2004 – BizTalk 2010 BizTalk Orchestration terminated Suddenly Re: BizTalk Orchestration terminated Suddenly

#20328

[quote user="gmk51080"]

I’m integrating BizTalk with K2, the Normal flow of the WorkFlow consists that BizTalk creates a Task in K2 and then K2 Must send a response to BizTalk in order to continue the workflow. In the time BizTalk is waiting the response in K2, the Orchestration is dehydrated. the problem occuring is that when the Task in K2 in created, and once K2 Reponse reachs BizTalk, Routing Failure error take please because the orchestration that should be in the “Dehydrated” status is no long existing in the administration Console, This is how i know that the Biztalk Orchestration in terminated suddenly and without being able to trace it .

[/quote]

How do you have your BizTalk Orchestration configured to wait for the response from K2? I have a similar process where I have to wait for 3 files that make up an invoice before continuing the Orchestration. I use the Listen shape to accomplish this. It sounds like your orchetration is sending a  message to K2 and then dehydrating before it gets a response back. If you’re not using a listening shape, try that.

Can you break the orchestration up? Can you have 1 orchestration send a message to K2, then terminate and have a second orchestration that listens for response message from K2?