Orchestration Error

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Orchestration Error

Viewing 1 reply thread
  • Author
    Posts
    • August 29, 2006 at 10:02 PM #15489
      community-content

        Greg, you were right on about my previous schema problem. For some reason it doesn’t like having elements and then an element definition format.

        Now on to my next issue:

        I’ve got the app deployed and it’s picking up files from my Receive location. But it gets this error when attempting to write to the Send Location. I,m simply reading and writing the file thru a transformation with no processing just a map. Promoted the fields to be moved but still get this error. All the ports appear to be enabled. Any thoughts?

        THanks

        A message received by adapter \”FILE\” on receive location \”Receive Location_ReceiveReq\” with URI \”C:\\BizTalkTest\\ReceiveLocation\\*.xml\” is suspended.
        Error details: 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.

      • August 30, 2006 at 3:17 PM #15490
        community-content

          Well tried a number of thing s and it still has the smae subscriber error.

          How would I go about checking the subscription for the BTS values? It seems pretty straighforward. A receive port, a transformation, and a send port in the orchestration. THe Pipeline has a flat file assembly. Recieve port is XMLREceive and the SendPort uses the Pipeline.

          Rookie here!

          Thanks

          • August 30, 2006 at 10:37 PM #15491
            community-content

              Thanks. I finally got it to work by dropping the transform piece of the orchestration and recreating it. This forced me to reconfigured the Orchestration on the server, it then worked ok.

              Will continue on!

              Thanks

              • August 29, 2006 at 10:19 PM #15492
                community-content

                  The receive port publishes the message to the Messagebox and looks for a subscriber. If no subscriber can be found you get this error.

                  A subscriber can be an orchestration or a send port.
                  If it is a send port you need to set a filter by specifying promoted properties and their values. Like BTS.ReceivePortName = \”youreceiveportname\”.

                  If you are using an orchestration the subscription is created when you bind the orchestration port to the receive port. This sets up a subscription filter:
                  BTS.ReceivePortID = <receive port id>
                  AND
                  BTS.MessageType = <messagetype on orchestration receive shape>

                  The BTS.MessageType property is set in the pipeline usually by one of the disassemblers (Xml or Flat File).
                  The default Passthru pipeline does not set the BTS.MessageType property.

                  If you are receiving an Xml message you will need to set the receive pipeline on the receive location to be XmlReceive.
                  And ensure all orchestrations and send ports are enlisted and started

                  • August 30, 2006 at 8:02 PM #15493
                    community-content

                      To view the subscriptions:
                      [url]http://www.winterdom.com/weblog/PermaLink,guid,9141d901-b0e6-4fd7-bb17-d9f086ae26e3.aspx[/url]

                      You can then check the message context values from the failing message to find the mismatch

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