|
Home > Archive > BizTalk Server Applications Integration > July 2004 > BTS 2004 SQL adapter 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 |
BTS 2004 SQL adapter exceptions
|
|
|
| If an error occurs during stored procedure execution, the exception returned to orchestration is a general (SOAP) exception, with no specific information notifying the real cause of error. (Although a warning is logged by BTS in event log, which contains
the actual error), I need to know is it possible to get the actual error message within the orchestration? Apparently, no fault message schemas are generated at design time, and no message is sent back if an exception occurs. SOAP exception thrown too, do
esnt contain the real error!
| |
| Deniz Erkan [MSFT] 2004-07-01, 5:52 pm |
| Can you try putting your Send shape in a transaction and add a catch block that
catches a DeliveryFailureException. The InnerException property of the
caught exception will be a SoapException that has this detailed
information. Make sure that your send port in the orchestration is
Binding->Specify Later and Delivery Notification->Transmitted.
--------------------
>Thread-Topic: BTS 2004 SQL adapter exceptions
>thread-index: AcRSLpz+BI0Aa8LTTsSTQw0aoGWdjA==
>X-WBNR-Posting-Host: 202.125.140.213
>From: =?Utf-8?B?QWxp?= <Ali@discussions.microsoft.com>
>Subject: BTS 2004 SQL adapter exceptions
>Date: Mon, 14 Jun 2004 09:42:42 -0700
>Lines: 1
>Message-ID: <E070132D-08DF-4502-BE55-C59B3AF717CE@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.biztalk.appintegration
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 127.0.0.1
>Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.appintegration:6819
>X-Tomcat-NG: microsoft.public.biztalk.appintegration
>
>If an error occurs during stored procedure execution, the exception returned to orchestration is a general (SOAP)
exception, with no specific information notifying the real cause of error. (Although a warning is logged by BTS in event log,
which contains the actual error), I need to know is it possible to get the actual error message within the orchestration?
Apparently, no fault message schemas are generated at design time, and no message is sent back if an exception
occurs. SOAP exception thrown too, doesnt contain the real error!
>
Deniz Erkan
Microsoft BizTalk Server Messaging Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
|
|
|
|
|