The published message could not be routed

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › The published message could not be routed

Viewing 1 reply thread
  • Author
    Posts
    • February 23, 2006 at 5:55 PM #14378
      community-content

        Hello!

        I am receiving the following error when attempting to Receive an xml schema from a WebService.

        \”The Messaging engine failed to process a message submitted by adapter:SOAP
        Source URL:/ReceiveOrder/service.asmx. Details:The published message could not be routed because no subscribers were found. This error occurs if the subscribed orchestration schedule or send port has not been started, or if some of the message properties necessary for subscription evaluation have not been promoted.\”

        I found out that you can do a search for ‘Subscriptions’. After running the query, I found the ‘Activate’ subscription accociated with my Application.
        Inside of the Subscription Details -> Expression, i found the follow
        Properties.

        http://schemas.microsoft.com/BizTalk/2003/system-properties.MessageType == http://CompanyName.OrderProcessing.Schemas.PurchaseOrder#PurchaseOrder
        AND
        http://schemas.microsoft.com/BizTalk/2003/system-properties.ReceivePortID ==
        {93559EA5-5DA8-4C64-A7F0-B7B0EAEA72EA}
        AND
        http://schemas.microsoft.com/BizTalk/2003/system-properties.InboundTransportType != SOAP
        OR
        http://schemas.microsoft.com/BizTalk/2003/soap-properties.MethodName == Operation_1
        AND
        http://schemas.microsoft.com/BizTalk/2003/system-properties.ReceivePortID == {93559EA5-5DA8-4C64-A7F0-B7B0EAEA72EA}

        the one line inparticular that looks like my problem ‘InboundTransportType != SOAP.
        (seeing as I am using a webservice to make the call this seems quite wrong)

        – Inside the BT Admin Console, my receive location Transport Type is set to ‘SOAP’ and I have even early bound the port inside the Orchestration with Type \”SOAP:

        Does anyone know if i am travelling down the right path?
        Is thier any way that i can chance the ‘InboundTransportType’ to = SOAP for the active substription?

        Thanks Kindly
        — Steven

      • February 23, 2006 at 8:39 PM #14379
        community-content

          Hey Stephen, just wanted to say thanks.

          Your suggestion worked. I was previously using the Web Service Publishing Wizard, but i was using the ‘Publish Schemas as Web Services’ – which wasn’t working…

          With your suggestion, i changed it to ‘Publish BizTalk orchestrations as a Web Service’ – which seems to be the right method.

          Thanks Again,
          — Steven

          • February 23, 2006 at 6:59 PM #14380
            community-content

              I have not seen problems in subscriptions that were not related to something I did. So, I would guess something else is actually causing the problem. Based on the And and Or logic that could be correct I wouldn’t focus on the subscription at this point.

              What I have done in BizTalk 2004 is use late bound ports and have the Web Service Publishing Wizard create the Receive Port for me. I’d try that first. The only problem I have had with that was when I changed the schema

              If that doesn’t work, always try redeploying, restarting hosts, and making sure you recreate the web service projects using the wizard.

              Hope this helps.

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