BizTalk Server General - Error Handling in Orchestration

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server General > March 2006 > Error Handling in Orchestration





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Error Handling in Orchestration
TimG

2006-03-25, 11:37 am

Hi

I have an orchestration which sends xml messages to sharepoint form
libraries and gets xml from sql server databases

For error handling I am using one exception handler block (System.Exception)
to call all errors. However for an sql error (non existent stored proc) the
message ex.Message is pretty uninformative (An error occurred while
processing the message, refer to the details section for more information).

How does one get to the details which is displayed in the application log

Regards

Tim
Tomas Restrepo \(MVP\)

2006-03-25, 11:37 am

Tim,

>
> I have an orchestration which sends xml messages to sharepoint form
> libraries and gets xml from sql server databases
>
> For error handling I am using one exception handler block
> (System.Exception)
> to call all errors. However for an sql error (non existent stored proc)
> the
> message ex.Message is pretty uninformative (An error occurred while
> processing the message, refer to the details section for more
> information).
>
> How does one get to the details which is displayed in the application log


Basically, what you're getting is a SoapException, which has a Details
property with an XML fragment which contains extra information. So just cast
your exception to SoapException, and then use an expression shape to extract
the rest of the information.


--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com