FIX: You receive an error message when you try to route a published message to multiple solicit-response ports in BizTalk Server 2006 (923632)

SYMPTOMS

When you try to route a published message to multiple solicit-response ports in Microsoft BizTalk Server 2006, you receive an error message that resembles the following. In this error message, receivelocation is the message receive location:Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5753
Description:
A message received by adapter "FILE" on receive location "Receive Location2" with URI "receivelocation" is suspended.
Error details: The message found multiple request response subscriptions. A message can only be routed to a single request response subscription.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft BizTalk Server 2004 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the BizTalk Server service after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File name	File version	File size	Date	Time
Btsmessageagent.dll	3.5.1617.0	690,464	21-Jul-2006	04:13

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

MORE INFORMATION

To enable this hotfix, follow these steps.

Note You must only enable this hotfix if the publishing port is a one-way port. You must not enable this hotfix if the publishing port is a request-response port.

Click Start, click Run, type regedit, and then click OK.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTSSvc$HostName
Note In this registry subkey, HostName is the name of the BizTalk Server host that publishes messages that are routed to multiple request response subscribers.
On the Edit menu, click New, and then click DWORD Value.
Type AllowMultipleResponses, and then press ENTER.
Right-click AllowMultipleResponses, and then click Modify.
In the Value box, type 1, and then click OK.
On the File menu, click Exit.

After you install this hotfix, you can use multiple solicit-response ports to receive a response for a subscription that matches a publication.

By default, you cannot route a message to multiple solicit-response ports because the publishing port cannot process multiple response messages. After you install the hotfix that is described in this article, the publishing solicit-response port still cannot process multiple response messages.

Routing multiple response messages to the publishing solicit-response port may cause suspended service instances because of messages that are not consumed. However, you can enable this hotfix if the response message from the solicit-response port is routed to another component. For example, you can enable this hotfix if a response message is routed to an orchestration or to a send port.