|
Home > Archive > BizTalk Server Orchestration > April 2006 > pls help! Orchestration dehydaration when Call Orchestatio
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
pls help! Orchestration dehydaration when Call Orchestatio
|
|
| Alex M 2006-04-27, 7:25 am |
| I have a problem when my orchestration tries to call another one. It
dehydrated and never becames active - it's still waiting for called
orchestration,
when orchestration debugger shows that in the called orch. only receive
shape
was initialized and then everything stopped.
I've redesigned called orchestation to activable one and it has worked fine.
Does anyone have any ideas why called orchestration doesn't work and there
are no any recods in HAT / service instances about this orch, only info
about dehydrated caller orch.....
I have one In Message parameter, one Out Message parameter and one out
variable (string) parameter in called orch.
| |
| Lucas R. Vogel 2006-04-27, 7:25 am |
| Are there any errors logged in the Event Log when you try to do this?
--
===========
Lucas R. Vogel
"Alex M" wrote:
> I have a problem when my orchestration tries to call another one. It
> dehydrated and never becames active - it's still waiting for called
> orchestration,
> when orchestration debugger shows that in the called orch. only receive
> shape
> was initialized and then everything stopped.
> I've redesigned called orchestation to activable one and it has worked fine.
> Does anyone have any ideas why called orchestration doesn't work and there
> are no any recods in HAT / service instances about this orch, only info
> about dehydrated caller orch.....
> I have one In Message parameter, one Out Message parameter and one out
> variable (string) parameter in called orch.
>
>
>
>
|
|
|
|
|