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.

The published message could not be routed because no subscribers were found


View products that this article applies to.

Source: Microsoft Support

↑ Back to the top


Rapid publishing

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

↑ Back to the top


Symptom

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.

↑ Back to the top


Cause

BizTalk is working in Pub-Sub mode and server will process the documents which should be having the subscriber for it. This error is occurring when BizTalk application could not find the subscriber. This will resulted in suspending the associated message in BizTalk server 2006 /2006 R2.

↑ Back to the top


Resolution



This can be resolved by checking the basic setup of the application deployed in the server, for this please follow below steps:
  1. Verify the Send ports/Orchestrations are enlisted and started.
  2. Whenever the content based routing is implemented, make sure the Filter entries are correct especially check for space/some extra characters.
  3. Compare the Filter values with the file which got suspended, this will easy the step 2.
  4. Verify the Receive Location set up especially the pipeline selected. Whenever the custom pipeline massage the data in to another format where the output data may not match the one waiting by the subscriber.


Many a time, Step 2 and step 4 would be the reason for this error.

↑ Back to the top


Disclaimer

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE �MATERIALS�) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

↑ Back to the top


Keywords: KB969221, kbnomt, kbrapidpub

↑ Back to the top

Article Info
Article ID : 969221
Revision : 1
Created on : 3/18/2009
Published on : 3/18/2009
Exists online : False
Views : 369