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.

[ Post a follow-up to this message ]

Hi Alex,
Are you using the "Call orchestration" or the "Start orchestration" shape?

--
Regards,

Leonid Ganeline
BizTalk Solution Developer
===================================
BizTalk Blog -- http://geekswithblogs.net/leonidganeline
"Alex M" <er4forums@mail.ru> wrote in message
news:OzgEsV8YGHA.1352@TK2MSFTNGP05.phx.gbl...
>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.
>
>
>

[ Post a follow-up to this message ]

I remember seeing such behavior about a year ago, but if I remember it
correctly, it was caused by inconsitency of deployed assemblies on BTS
server. (I.e. one of the asseblies was compiled and deployed with a new
version of shared component, while as another assembly were still using old
version of shared component - or samething like that).
I believe we solved this problem by redeploying the solution...

-Valery.
http://www.harper.no/valery

"Alex M" <er4forums@mail.ru> wrote in message
news:OzgEsV8YGHA.1352@TK2MSFTNGP05.phx.gbl...
>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.
>
>
>

[ Post a follow-up to this message ]