Hotfix informationA 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.
PrerequisitesNo prerequisites are required.
Restart requirementYou must restart the BizTalk Server service after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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|
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$HostNameNoteIn 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.
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.
Article ID: 923632 - Last Review: Jan 16, 2015 - Revision: 1