hi,

We already made an orchestration with correlation wich works, so the biztalk
config should not be in cause.
Problem is, we tried to recreate it, and the same (apparently) shapes fail
to initialize the correlation set, because messages get stuck before
arriving in the first receive shape. The HAT shows the messages as "Routing
failure report", and that's all.

We had one occurence when changing the receive pipeline type and restarting
made the orchestration work, but redeploying immediatly afterwards broke
again the orchestration (internal soap failure, routing failure).

here's the modus operandi we follow, we badly need help on this to know if
it's accurate :
(the port is public req/resp. set as specify now, and points to the asmx
generated by the web service wizard)

'-- after any modification on the orchestration O :

O. is unenlisted.
O. is re-deployed
web service wizard is launched, anonymous & replace site is checked, not
create receives (already done by deploiement)
O. is enlisted
O. is started

we write a simple C# client which adds a web reference to the proxy and
calls the operations. first call breaks with "internal soap error", message
stuck.

please help, we're stuck since several days. cannot debug or view the
message to see if it's correct, but it should, since it worked at least
once. 

Setup :

the orchestration is basic, we got theID message, contains a promoted
string, and theResponse, contains a normal string.
two operations on a port are set as request/receive, request is theId type,
response is theResponse type.
first operation arrives on receive shape with activate and init correlation
then send back a response, second has its own receive shape with following
(seems basic)

Windows2003 server sp1, biztalk 2004 sp1...

[ Post a follow-up to this message ]

Are you getting a message in the event log? is it saying "no subscriptions
found"?
Check if the incoming message matches the subbscription of the port, mainly
make sure all the elements that participate in the correlation exist (and
have a value) if one of them is missing or empty the correlation cannot be
initialized and the message routing will fail.

Yossi Dahan

"Emmanuel Issaly" <nospam@thanks.com> wrote in message
news:42e4d837$0$29942$626a14ce@news.free.fr...
> hi,
>
> We already made an orchestration with correlation wich works, so the
> biztalk config should not be in cause.
> Problem is, we tried to recreate it, and the same (apparently) shapes fail
> to initialize the correlation set, because messages get stuck before
> arriving in the first receive shape. The HAT shows the messages as
> "Routing failure report", and that's all.
>
> We had one occurence when changing the receive pipeline type and
> restarting made the orchestration work, but redeploying immediatly
> afterwards broke again the orchestration (internal soap failure, routing
> failure).
>
> here's the modus operandi we follow, we badly need help on this to know if
> it's accurate :
> (the port is public req/resp. set as specify now, and points to the asmx
> generated by the web service wizard)
>
> '-- after any modification on the orchestration O :
>
> O. is unenlisted.
> O. is re-deployed
> web service wizard is launched, anonymous & replace site is checked, not
> create receives (already done by deploiement)
> O. is enlisted
> O. is started
>
> we write a simple C# client which adds a web reference to the proxy and
> calls the operations. first call breaks with "internal soap error",
> message stuck.
>
> please help, we're stuck since several days. cannot debug or view the
> message to see if it's correct, but it should, since it worked at least
> once. 
>
> Setup :
>
> the orchestration is basic, we got theID message, contains a promoted
> string, and theResponse, contains a normal string.
> two operations on a port are set as request/receive, request is theId
> type, response is theResponse type.
> first operation arrives on receive shape with activate and init
> correlation then send back a response, second has its own receive shape
> with following (seems basic)
>
> Windows2003 server sp1, biztalk 2004 sp1...
>

[ Post a follow-up to this message ]

thanks for the response,

we have no error messages in the event log.
The error occurs before the first receive shape, so the subscription isn't
even created 

the message looks correct and contains a string, "1", before the web proxy
call.
the invoke fails with "internal soap error", and we get a routing error. no
instance is created.



"Yossi Dahan" <yossi.dahan@sabratech.co.uk> a écrit dans le message de news:
%230WaAfRkFHA.3144@TK2MSFTNGP12.phx.gbl...
> Are you getting a message in the event log? is it saying "no subscriptions
> found"?
> Check if the incoming message matches the subbscription of the port,
> mainly make sure all the elements that participate in the correlation
> exist (and have a value) if one of them is missing or empty the
> correlation cannot be initialized and the message routing will fail.
>
> Yossi Dahan
>
> "Emmanuel Issaly" <nospam@thanks.com> wrote in message
> news:42e4d837$0$29942$626a14ce@news.free.fr... 
>
>

[ Post a follow-up to this message ]

to be very precise, if we use a send/receive wich inits a correlation it
works.
IF we add another operation with a "following" on its receive, it breaks.

so far update method is as follow :

add operation (with promoted field included in type)
add receive shape, construct & send
refresh Bt explorer
unenlist
redeploy
refresh Bt explorer
enlist
start
launch web wizard
create proxy & receive port

test -> broke

tried doing iisreset, start/stop again, emptying failed messages, rebooting
even.

orchestration #1 works
this one doesnt.

thanks for any help on this :S

(ps just for info : i hope deployment & debugging is really better in BTS
2006, because the competitors software i tried recently was light years
ahead of this on these points... )


"Emmanuel Issaly" <nospam@thanks.com> a écrit dans le message de news:
42e4e51d$0$8586$626a14ce@news.free.fr...
> thanks for the response,
>
> we have no error messages in the event log.
> The error occurs before the first receive shape, so the subscription isn't
> even created 
>
> the message looks correct and contains a string, "1", before the web proxy
> call.
> the invoke fails with "internal soap error", and we get a routing error.
> no instance is created.
>
>
>
> "Yossi Dahan" <yossi.dahan@sabratech.co.uk> a écrit dans le message de
> news: %230WaAfRkFHA.3144@TK2MSFTNGP12.phx.gbl... 
>
>

[ Post a follow-up to this message ]