could not be routed because no subscribers on direct bound orchestration port

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › could not be routed because no subscribers on direct bound orchestration port

Viewing 2 reply threads
  • Author
    Posts
    • #20094

      Ok, here’s the scenario thats been causing me a bit of heart ache. I am sure I am just looking past the issue, but… Here’s the architecture, I receive a XML flat file in a particular drop folder, this is picked up by a receive port which has a custom pipeline.

      This pipeline reads the message body, and breaks the incoming message into numerous new messages. So, my receive port get’s a file based on XSD1 and converts it into several new messages based on XSD2. After the pipeline has completed I should have x messages within the message box. And this is the case, as I can see them as activities within the message flow in HAT. They come up as Unparsed Interchange, and if I try to save the messages all I get out is the incoming XML (XSD1) and its context. If I look at it in Group Hub, then I can see x failed instances, and I can see the context (but not the body) of each of my generated messages. The only body XML I can see is the one that originally came in. Anyway, I have a direct bound receive port in my orchestration, which has a filter which should correlate to the items I can see in the context of what I can see within Group Hub.

      However, if I look in the event viewer I get “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. ” If I create a send port, and put the same filter within it, the send port picks up the messages.

      Any ideas?

       Confused.

    • #20095

       In your orchestration, is the receive port tied to a particular type of message?  If so, then it adds an additional filter of message type.  You need to have an XML disassembler component in your pipeline for BizTalk to apply a message type.  One way to tell for sure is to open a new query in the group hub, and then select to query for subscriptions.  You should be able to find the subscriptions for your orchestration and send port based on the service name.  You will be able to see the actual filter expressions BizTalk is using.  Hope this helps!

    • #20096

      I would second Ruselw’s comments; one thing I do to ease my development pain when working with de-batched messages is to hook a Send Port upto the Receive Location doing the de-batching to capture some of the debatched messages. Then hook a temp Receive Port/Location upto the orchestration and push the individual de-batched messages into it – you can then tell whether the orchestration accepts these messages, rather than having to figure out whether its a problem with de-batching.

      Hope this helps, Nick.

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