Integrating Integrators – BizTalk, Windows Azure, Windows Workflow, and Beyond

Re: Publishing message

BizTalk 2006

This group is for all content related to BizTalk Server 2006. This includes a forum, samples, videos, labs, and tools. Most of the content here also applies to other versions of BizTalk beyond 2006.

Publishing message

  • rated by 0 users
  • This post has 5 Replies |
  • 1 Follower
  • Hi,

    I have problem with direct Binding in orchestration.

    I receive a message and I have to send it to messagebox. I do this thru direct binding in the send port.
    Here I don't have any other orchestration which subscribes it.

    The main process here just publishing it to messagebox.

    But I am getting error in event log( No errors in HAT)

    \" ErrorInfo The published message could not be routed because no subscribers were found. .

    Failed to publish (send) a message in the batch. This is usually because there is no one expecting to receive this message. The error was The published message could not be routed because no subscribers were found\"

    Since I don't have any subscriber how can I publish the message to messagebox avoiding this error?

    Please help
    Edit
  • That’s not possible. You need to have a subscriber in order to publish a message to the message box.

    What are you trying to accomplish? Why do you just want the message inside the message box?

    Hope this helps.

    Stephen W. Thomas
    http://www.BizTalkGurus.com

  • Thanks Stephen.

    The problem is solved since the other application will pick the message.

    One more question I have. How to check the message is stored in the MessageboxDB? which tables we have to check there?


    Thanks
    Edit
  • It’s been a while since I looked at the message box, but if I remember right the main table is the SPOOL table. The data is stored as a binary image so it’s hard to understand.

    I’d suggest not really digging into the message box. It’s not really a good place to look. Using the BizTalk Admin tool and HAT are much better ways to go.

    Hope this helps.

    Stephen W. Thomas
    http://www.BizTalkGurus.com

  • Can you please how the above problem got solved i think i am facing a similar problem where iam trying to publish to msgbox and there are other orchestration which will pick this but iam still getting this error

    Edit
  • How are you routing?

    Have you set any filters on the Subscribing Orchestration?

    Just check the Context of the suspended message....you will easily see the promoted properties planned to be used for routing.

    Regards,
    NISHIL
    MCT,MCTS | Freelance BizTalk Consultant.
    biztalkconnect.blogspot.com

Page 1 of 1 (6 items)