| Author |
sql adapter exceptions
|
|
|
| Is there a way to catch exceptions from the sql adapter in an orchestration?
I have a receive port that polls a database.
In order to generate an error,
I changed the stored procedure to reference a table with an invalid
column name.
My orchestration is inside a scope object and
the scope object is set to a long running transaction.
I have added exception handlers for SoapException, SystemException,
ComException.
My exception handlers trap the exception and write
the exception to the event log.
The only problem is when i look at the event log
I see that biztalk logged the exception to the event log with a 'Warning'
and my exception handlers were bypassed.
| |
| Greg Forsythe 2006-03-25, 11:36 am |
| Your problem is the orchestration is never started so your exception code
will never be run.
The orchestration is only instantiated when a message is published to the
MessageBox.
The error you are seeing occurs in the Adapter so no message is ever
generated or published.
Greg
"mwr" <mwr@discussions.microsoft.com> wrote in message
news:15D35879-D963-40A8-9366-E7D75D8936D0@microsoft.com...
> Is there a way to catch exceptions from the sql adapter in an
> orchestration?
> I have a receive port that polls a database.
>
> In order to generate an error,
> I changed the stored procedure to reference a table with an invalid
> column name.
>
> My orchestration is inside a scope object and
> the scope object is set to a long running transaction.
> I have added exception handlers for SoapException, SystemException,
> ComException.
>
> My exception handlers trap the exception and write
> the exception to the event log.
>
> The only problem is when i look at the event log
> I see that biztalk logged the exception to the event log with a 'Warning'
> and my exception handlers were bypassed.
>
>
>
>
>
| |
|
| Hey Greg,
I ran into the same issue on another port after my orchestration
had already been started. I have another port in my orchestration
that calls a store procedure using the sql adapter. The stored proceedure
updates a status flag.
When i change the procedure to reference and invalid column name. I wasnt
able to trap the exception in my exception handler.
Mike
"Greg Forsythe" wrote:
> Your problem is the orchestration is never started so your exception code
> will never be run.
> The orchestration is only instantiated when a message is published to the
> MessageBox.
> The error you are seeing occurs in the Adapter so no message is ever
> generated or published.
>
> Greg
>
>
> "mwr" <mwr@discussions.microsoft.com> wrote in message
> news:15D35879-D963-40A8-9366-E7D75D8936D0@microsoft.com...
>
>
>
| |
| Greg Forsythe 2006-03-25, 11:36 am |
| You will need to use Delivery Notification
http://msdn.microsoft.com/library/d...g_orch_pxnj.asp
Greg
"mwr" <mwr@discussions.microsoft.com> wrote in message
news:A7A5F919-FA16-421C-9DC6-0A24C51FB5F0@microsoft.com...[vbcol=seagreen]
> Hey Greg,
>
> I ran into the same issue on another port after my orchestration
> had already been started. I have another port in my orchestration
> that calls a store procedure using the sql adapter. The stored proceedure
> updates a status flag.
>
> When i change the procedure to reference and invalid column name. I wasnt
> able to trap the exception in my exception handler.
>
> Mike
>
> "Greg Forsythe" wrote:
>
|
|
|
|