|
Home > Archive > BizTalk Server Orchestration > August 2005 > Catching SOAP Exceptions
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 |
Catching SOAP Exceptions
|
|
| anand kumar 2005-08-06, 8:47 pm |
| Hi,
I am trying to catch SOAP exception and have been unsuccessful.
I am consuming a web service inside the orchestration and send port binding
is set to specify later. I have set the Delivery Notification property of the
send port to Transmitted.
Everything is in a long running scope shape. I have 2 exception blocks.
First exception handler catches DeliveryFailureException and the second
exception handler is general exception. I am trying to write a message to
event log from expression shape of exception handler. It is always going to
general exception block instead of going to SOAP exception block. I am
throwing a fake ASMX URL so that I can catch the SOAP exception and nothing
is happening.
Currently I have not upgraded to SP1, which I will do it later.
Any tips or help is greatly appreciated.
Thanks,
Anand
| |
| Stephen W. Thomas 2005-08-08, 5:52 pm |
| Hello.
If I remember correctly, Delivery Notification has a bug
(http://support.microsoft.com/?kbid=840008) that is fixed in SP1.
I have always had the Hotfix so I do not know for sure if you should be able
to catch the exceptions or not.
It sounds like you are doing everything correct though. I’d try installing
SP1 and see if that fixes the problem.
Hope this helps.
Stephen W. Thomas
http://www.biztalkgurus.com
"anand kumar" wrote:
> Hi,
> I am trying to catch SOAP exception and have been unsuccessful.
>
> I am consuming a web service inside the orchestration and send port binding
> is set to specify later. I have set the Delivery Notification property of the
> send port to Transmitted.
>
> Everything is in a long running scope shape. I have 2 exception blocks.
> First exception handler catches DeliveryFailureException and the second
> exception handler is general exception. I am trying to write a message to
> event log from expression shape of exception handler. It is always going to
> general exception block instead of going to SOAP exception block. I am
> throwing a fake ASMX URL so that I can catch the SOAP exception and nothing
> is happening.
>
> Currently I have not upgraded to SP1, which I will do it later.
>
> Any tips or help is greatly appreciated.
>
> Thanks,
> Anand
| |
| anand kumar 2005-08-09, 5:53 pm |
| Thanks Stephen.
Instead of using deliveryFailureException, I used SOAPException inside the
catch exception handler and I was able to handle SOAP exceptions.
Thanks,
Anand
"Stephen W. Thomas" wrote:
[vbcol=seagreen]
> Hello.
>
> If I remember correctly, Delivery Notification has a bug
> (http://support.microsoft.com/?kbid=840008) that is fixed in SP1.
>
> I have always had the Hotfix so I do not know for sure if you should be able
> to catch the exceptions or not.
>
> It sounds like you are doing everything correct though. I’d try installing
> SP1 and see if that fixes the problem.
>
> Hope this helps.
>
> Stephen W. Thomas
> http://www.biztalkgurus.com
>
> "anand kumar" wrote:
>
|
|
|
|
|