How to catch the failed message in orchestration

first, have searched forums' history, , seems topic have been discussed before, still not answer need, ask question again.

i have catch failedmessage application. know configure send port filter errorreport.errortype=failedmessage in biztalk adminstration console can , route failed message, not enough me, because failed message, need failed message error description.

i try in orchestration in such ways scope, catch exception, not catch/get failed message or error desctiopn in catch exception block, seems guys have said failed message , error description not got @ catch block, i'm not sure that, can confirm it?

i know that, using receive shape filter errorreport.errortype=failedmessage  failed message, have set activate property true, know, there 1 receive shape's activate property can set true in 1 orchestration, , in orchestration, there 1 receive shape set true, used recive edi message, not add receive shape ture property of activate.

so there else ways catch failed message , error description in orchestration?

thanks.

hi

it seems have couple of things mixed up.

first of all, failed message routing feature not intended such used in orchestrations. sounds have message going out , reply might failing, in case want have inside orchestration. not doable.

what can failed message routing message failing in receive port gets published messagebox. since failed, wont have messagetype promoted or pretty else. can create either send port or orchestration deals failed messages. bear in mind orchestration orchestration handling of failed messages , nothing else. not part of existing orchestration.

for biztalk failed message existing orchestration, form of correlation needed, difficult, since correlation based upon promoted properties coming form messages, , wont there because message failed in receive port.

in short: catch exception applies if there occurs exception during execution of orchestration. incoming message goes through receive port hasn't reached orchestration yet, , therefor, orchestration not aware of existence. if need existing orchestration message, need new orchestration gets failed messages, inspects them , publishes them messagebox properties set can used filtering , correlation in existing orchestration.

hoep helps... rather big subject , difficult down hort answer on forums...

---

eliasen, representing himself , not company works for.
three times mvp , 3 times mcts in biztalk.
blog: http://blog.eliasen.dk

BizTalk Server  >  BizTalk Server General