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

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:

By default, you cannot publish a message and then route that message to multiple solicit-response ports in BizTalk Server 2006.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

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.Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

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.

1. Click Start, click Run, type regedit, and then click OK.
2. 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.
3. On the Edit menu, click New, and then click DWORD Value.
4. Type AllowMultipleResponses, and then press ENTER.
5. Right-click AllowMultipleResponses, and then click Modify.
6. In the Value box, type 1, and then click OK.
7. 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.

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

For more information, click the following article number to view the article in the Microsoft Knowledge Base: