FIX: 2-way WCF-BasicHttp receive port does not respond to a WCF client when the "failed message routing" feature is enabled in BizTalk Server 2010 or in BizTalk Server 2013

Article translations Article translations
Article ID: 2813294 - View products that this article applies to.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario:
  • You configure a 2-way WCF-BasicHttp receive port that receives Electronic Data Interchange (EDI) messages from a WCF client in Microsoft BizTalk Server 2010 or in Microsoft BizTalk Server 2013.
  • The 2-way receive port receives an invalid EDI message during the EDI disassemble stage, and an error occurs.
  • An error message is logged in the event log, and a negative 999 acknowledgement is published to the Message Box database.
  • An orchestration obtains the 999 acknowledgement and then publishes the acknowledgement to the Message Box database.
  • You enable the "failed message routing" feature.
In this scenario, you experience the following issues:
  • The Batchcomplete method fails, and you receive the following error message:

    Log Name: Application
    Source: BizTalk Server
    Event ID: 5673
    Task Category: BizTalk Server
    Level: Error
    Keywords: Classic
    Description:
    The Messaging Engine received an error from transport adapter " WCF-BasicHttp" when notifying the adapter with the BatchComplete event. Reason "Value cannot be null. Parameter name: error".
  • The 2-way receive port on the response computer obtains the 999 acknowledgement. However, the 2-way receive port cannot send the acknowledgement back to the WCF client.
  • A suspended receive instance is not displayed on the Group hub page in the BizTalk Server Administration Console.
Note If you do not enable the "failed message routing" feature, a suspended receive instance is displayed on the Group hub page in the BizTalk Server Administration Console. Additionally, the 2-way receive port on a response computer obtains the 999 acknowledgement and then sends the acknowledgement back to the WCF client.

Resolution

Cumulative update information

For BizTalk Server 2013

The hotfix that resolves this issue is included in cumulative update package 2 for BizTalk Server 2013.

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2892599 Cumulative update package 2 for BizTalk Server 2013

For BizTalk Server 2010

The hotfix that resolves this issue is included in cumulative update package 6 for BizTalk Server 2010.

For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2855367 Cumulative update package 6 for BizTalk Server 2010


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More information

For more information about how to enable routing for failed messages, go to the following MSDN website:
General information about how to enable routing for failed messages
For information about the service packs and cumulative update list for BizTalk Server, click the following article number to view the article in the Microsoft Knowledge Base:
2555976 Service pack and cumulative update list for BizTalk Server
For more information about BizTalk hotfixes and cumulative update support, click the following article number to view the article in the Microsoft Knowledge Base:
2003907 Information about BizTalk hotfixes and Cumulative Update support

Properties

Article ID: 2813294 - Last Review: October 31, 2013 - Revision: 2.0
Applies to
  • Microsoft BizTalk Server Branch 2010
  • Microsoft BizTalk Server Developer 2010
  • Microsoft BizTalk Server Enterprise 2010
  • Microsoft BizTalk Server Standard 2010
  • Microsoft BizTalk Server 2013 Branch
  • Microsoft BizTalk Server 2013 Developer
  • Microsoft BizTalk Server 2013 Enterprise
  • Microsoft BizTalk Server 2013 Standard
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2813294

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com