Microsoft KB Archive/928405

= FIX: Error message when BizTalk Server 2006 submits a message to a non-SOAP receive location: &quot;The published message could not be routed&quot; =

Article ID: 928405

Article Last Modified on 11/15/2007

-

APPLIES TO


 * Microsoft BizTalk Server 2006 Developer Edition
 * Microsoft BizTalk Server 2006 Enterprise Edition
 * Microsoft BizTalk Server 2006 Standard Edition

-



SYMPTOMS
Consider the following scenario in Microsoft BizTalk Server 2006:
 * You use a receive port and two receive locations.
 * One receive location is a SOAP receive location. The other is a non-SOAP receive location.
 * You enlist the receive port to an orchestration.
 * BizTalk Server delivers a message of type System.Xml.XmlDocument.

When BizTalk Server submits the message to the non-SOAP receive location, the message is suspended. Additionally, an error message that resembles the following is logged in the Application log:

A message received by adapter &quot;FILE&quot; on receive location &quot;testenlistment_1.0.0.0_testenlistment.MainOrch_Port_1_f25c2a319cf80ee9_ReceiveLocation&quot; with URI &quot;drive:\cases\testenlistment\in2\*.*&quot; is suspended. Error details: The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration or send port has not been enlisted, or if some of the message properties necessary for subscription evaluation have not been promoted. Please use the Biztalk Administration console to troubleshoot this failure. MessageId: {F0E34053-15A1-47BC-8602-1680874410D1} InstanceID: {A7A279AB-9B00-47AC-BAA2-04F4CB41EEC7}



CAUSE
The receive port generates a subscription for the SOAP receive location. However, the receive port cannot generate a subscription for the non-SOAP receive location. Therefore, a routing failure occurs when BizTalk Server submits the message to the non-SOAP receive location.



Hotfix information
A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

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

Prerequisites
No prerequisites are required

Restart requirement
You must restart the server after you apply this hotfix.

Registry information
To fix this problem, you must create a RouteSoapOnMessageType registry entry after you apply this hotfix. To do this, follow these steps:  Click Start, click Run, type regedit, and then click OK. Locate and then click to select the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\3.0\Administration

 On the Edit menu, point to New, and then click DWORD Value. Type RouteSoapOnMessageType, and then press ENTER. Right-click RouteSoapOnMessageType, and then click Modify. In the Value data box, type 1, and then click OK. On the File menu, click Exit to exit Registry Editor.</li></ol>

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 this file may contain additional files.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Keywords: kbexpertiseadvanced kbfix kbpubtypekc kbhotfixserver kbqfe KB928405

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.