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 pro

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › 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 pro

Viewing 3 reply threads
  • Author
    Posts
    • January 16, 2007 at 5:36 PM #17253
      community-content

         

         Hi All,

        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.

         I am getting this error message again and again in my application. I have done everything as shoul be done. I have also done what the error mesage indicates. Still I get this error message . I feel there is some thing else that causing this problem. Is there anything wrong with Message box DB/Message part table ? I hope lot people might has faced this problem. PLease let me know if there is any clever fix to solve it.

         

        thanks

        Jitendra

         

      • January 17, 2007 at 2:23 AM #17258
        community-content

          Jitendra,

          it seems pretty clear that you are missing a subscription. You can use the BizTalk Administrator tool to look at the subscriptions you have (it's on the group hub tab).

          Has this *ever* worked? Or is this an intermittent problem?

          John D.

          • January 17, 2007 at 9:39 AM #17271
            community-content

              John,

              It has never worked. What ever application I am creating I am getting this error message. I understand this is a subscription issue. It is under group hub tab. But what infermation insubscription will help me to solve this problem ? All the concerned subscription is in started state.What I have to do there ? Please explain me in bit details.

               

              thanks

              Jitendra

               

              • January 17, 2007 at 1:40 PM #17272
                community-content

                  This is a common error. Unfortunately the causes are plenty.  If it has never worked, it is likely a simple configuration problem.

                  In order for anyone to help you, you will likely need to supply more information, such as the scenario you have set up.  Do you have a receive port and send port configured alone?  If so, use a filter on your send port, such as: BTS.ReceivePortName == <Receive Port actual name goes here>. 

                  Are you using an Orchestration that is connected using static ports, dynamic ports, request-response, one-way, etc?  Have you tried simple projects to "black-box" test your problems?  Also, make sure to clear out suspended messages and restart your Host Instance when you make changes to the app or re-deploy.

                  If none of this helps, please supply more information about your current application.

                • January 18, 2007 at 12:57 AM #17281
                  community-content

                    Jitendra,

                    to help you understand subscriptions, and to help your problem in particular, it is a good idea to try setting up a parallel subscription for the same message. Just define a new send port and give it an appropriate filter. For example the one suggested by BizTron. Then change the filter to the one your orchestration is using.

                    John D.

              • August 5, 2009 at 10:22 AM #22970
                community-content

                  I was having this issue recently in one of my applications after i refreshed an application dll.  It turned out to be that the receive pipeline was changed from XMLReceive to PassThru because the wrong pipeline was pre-configured in the orchestration…

                  So check your receive pipeline!!!

                  -Will B.

                  Env: BizTalk Server 2006 R2

                • December 1, 2018 at 9:57 PM #42525
                  Rajkumar

                    It seem very common problem,
                    Just follow below step to solve this problem.
                    1. Double click on your Send port name.
                    2. Go to filter tab
                    3. correctly set your property , operator and value.

                    Restart your send port and done.

                • Author
                  Posts
                Viewing 3 reply threads
                • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.