• Stephen W. Thomas
  • Azure Integration Gurus
BizTalkGurus
  • Home
  • Blogs
    • Stephen’s BizTalk and Integration Blog
    • BizTalk Community Blogs via Syndication
  • Forums
  • Downloads
  • Videos
  • Training
    • Online Training
    • Classroom Training
Select Page

Re: Handling message delivery error in Send Pipelines

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Handling message delivery error in Send Pipelines › Re: Handling message delivery error in Send Pipelines

March 21, 2007 at 3:02 PM #18089
community-content

    Hi,

    There is a new great error-handling facility in BTS 2006 – Failed Message Routing.

    You can handle errors in send/receive port, adapters, pipeline, routing. It's simple and powerful. Find details in the  article on MSDN (link is here). I found another good sample of Failed Orchestration Routing in the Matt Meleski's blog. Both were very useful for me.

    Nick 


    Search this Site:


    Recent Posts

    • Logic App Consumption deployment: The secret of KeyVault parameter cannot be retrieved. Http status code: ‘Forbidden’. Error message: ‘Access denied to first party service
    • BizTalk Server Visual Studio project: attempted re-targeting of the project has been canceled.
    • BizTalk Oracle Adapter error: The assembly required for type mapping not found.
    • PowerShell script to identify all SQL V1 actions and triggers inside Logic Apps Consumption
    • Friday (funny) Fact: There is no size limit for the Logic App parameter name

    Tweets by AzureIntGurus

    Recent Topics

    • Evaluating on the amount of items returned in a message
    • Send and Receive ports problem
    • How to config/costom a WS Security to SOAP header
    • Email attachments – POP3 adapter
    • Calling ASP page from Biztalk Orchestration

    • Home
    • Blogs
    • Forums
    • Downloads
    • Videos
    • Training
    • Facebook
    • X
    • RSS
    @BizTalkgurus.com