BizTalk Server Orchestration - Problem catching custom exception

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server Orchestration > October 2005 > Problem catching custom exception





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 Problem catching custom exception
larsson76@gmail.com

2005-10-13, 6:00 pm

Hi,

I have coded two custom exceptions wich I use when I get an error when
communicating with a partner. The call chain looks like this:

BTS2004 --wscall--> DMZ Server --wscall--> Outside Partner

It is the DMZ Server that generates the custom error and throws it back
to biztalk using a normal try/catch statement.

However, when trying to catch these specific exceptions in biztalk
nothing happens. My first catch in the orchestrations is set up to
handle the partnercommunicationexception and the other handles all
other exceptions (System.Exception).

The catch-block only catches the outer exception and not the specific
one. When i write the error to the log it says something like
System.Web.Services.Protocols.SoapException -->
MyCommonException.PartnerCommunicationException ...errordescription
goes here...

So, i tried to catch a SoapException instead and then getting the
innerexception (wich should be the partnercommunicationexception that
the webservice threw) but apparently that property is null because i
get a nullreferenceexception when i try to get the exception from the
SoapException.InnerException property.

Can someone help me with this?

//Magnus

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com