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

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.