Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Error message when you use a Request-Response receive location in BizTalk Server 2006 R2


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You use a Request-Response port to receive messages and to send responses in BizTalk Server 2006 R2.
  • You use two orchestrations to process the received messages.
  • You use the Request-Response port to communicate between the two orchestrations. Additionally, you specify "Direct" as the binding type for the port.
  • You receive a message in the receive location.
In this scenario, a response message is routed to two subscribers. One copy of the response is received successfully, and the other copy is suspended. Because of this behavior, the following error message is logged in the Application log:
Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5813

Description:
A response message for two-way receive port "port_name" is being suspended as the messaging engine could not correlate the response to an existing request message. This usually happens when the host process has been recycled.
Note This issue may occur in BizTalk Server 2009.

↑ Back to the top


Cause

This problem occurs because BizTalk Messaging Engine routes the response message from the second orchestration to both the first orchestration and the original Request-Receive port.

↑ Back to the top


Resolution

The hotfix that resolves this problem is included in cumulative update package 1 for BizTalk Server 2006 R2 Service Pack 1.

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:
982061 Cumulative update package 1 for BizTalk Server 2006 R2 Service Pack 1

↑ Back to the top


Status

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

↑ Back to the top


More information

For more information about how to work with direct bound ports in orchestrations, visit the following Microsoft Developer Network (MSDN) Web site: For more information about Message Context properties, visit the following MSDN Web site: For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
2003907 Information about BizTalk Server hotfixes

↑ Back to the top


Keywords: kbbiztalk2006r2presp2fix, kbbiztalk2006presp1fix, kbexpertiseinter, kbtshoot, kbfix, kberrmsg, kbbug, kbsurveynew, kbprb, kbbtsmessaging, KB979095

↑ Back to the top

Article Info
Article ID : 979095
Revision : 2
Created on : 4/28/2010
Published on : 4/28/2010
Exists online : False
Views : 262