- This topic has 3 replies, 1 voice, and was last updated 9 years, 2 months ago by
.
-
Posts
-
-
Other than: "Using BizTalk Server Exception Handling" (http://msdn2.microsoft.com/en-us/library/aa560927.aspx) has anyone either added a Fault Message Direction to a Request-Response (Send-then-Receive) Port, …
OR just added the proper Exception Handler to your scope to capture Oracle/SQL/other exceptions?
I've followed a few suggestions and have come up empty. I'll be checking the newest books over the holiday break but would appreciate any suggestions on the topic. My most recent attmept using the aforementioned help left me in the same state I was in without attempting to catch the exception…Event log entries and a suspended message.
BizTron.
-
I’ve always just used exception handling inside scope shapes.
Although for SQL, WS, probably Oracle Adapters the error messages are not very good. In some cases, I’ll just make the call inside a .net component called from an Orchestration. That way I have better control over the errors – but I lose all the benefits of the adapter framework.
-
A brief update. After allowing a database exception to suspend several records, I found that eventually I did see the exception logged correctly when handled within the Scope shape exception handler. Since I can detect an Error, now I can at least inform someone there was a generic DB error so that the message(s) can be reprocessed later. I just need to find a way to cleanly handle each specific situation based on the exception message contents or exception type.
BizTron.
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.