Biztalk 2004 Integration Experiences

Wednesday, January 12, 2005

Handling Error in Orchestration

The most fascinating part of Biztalk 2004 Orchestration compared to Biztalk 2000/2002 Xlang to me is Error Handling in Orchestration. In the recent implementation I was able to come up with a central Error handling mechanism.

All the actions in my orchestrations are wrapped under a common Scope with two Exceptional handlers


. . . }

Catch1 (System.Exception)
build Error message
Call Orchestration ErrorHandler
Catch2 (General Exception)
{ build Error message
Call Orchestration ErrorHandler

The important thing to note above is you should use System.Exception and not System.SystemException as the Catch Error object (Which is a common mistake)


  • At 6:57 AM, Anonymous Anonymous said…

    why general exception is "larger" in scope than System.Exception???

    Why are they different?
    Is is not enough just to catch System.Exception?


Post a Comment

<< Home