Default Receive Pipeline

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Default Receive Pipeline

Viewing 1 reply thread
  • Author
    Posts
    • August 21, 2006 at 8:57 AM #15382
      community-content

        The message has passed thru the pipeline and Biztalk is attempting to publish it to the message box, but can find not subscriber.

        What component’s do you have in your custom pipeline?
        Is there a send port or orchestration subscribing to this message?
        Is the BTS.MessageType cntext property being set in the pipeline?

      • August 21, 2006 at 7:19 PM #15383
        community-content

          The Xml Disassembler component sets the BTS.MessageType property based on the message received.

          The orchestration subscribes to the the MessageType of the message defined in the Activate receive shape. You do not have to set any additional filters.

          Have you enlisted and started the orchestration?

          • August 20, 2006 at 6:07 PM #15384
            community-content

              Hi,

              I have added a default receive pipeline in my solution and using this in my orchestration instead xmlreceive. I get the following error.

              [b:e646a9d0d3]There was a failure executing the receive pipeline: \”LearnOrches.ReceivePipeline1, LearnOrches, Version=1.0.0.0, Culture=neutral, PublicKeyToken=92d0bc0261c862c8\” Source: \”Unknown \” Receive Port: \”LearnOrches_1.0.0.0_LearnOrches.BizTalk_Orchestration1_TestRecvPrt_92d0bc0261c862c8\” URI: \”D:\\Documents and Settings\\Administrator\\Desktop\\Recv Marks\\*.xml\” Reason: Failed to get pipeline: LearnOrches.ReceivePipeline1, LearnOrches, Version=1.0.0.0, Culture=neutral, PublicKeyToken=92d0bc0261c862c8. Please verify that the pipeline strong name is correct and that the pipeline assembly is in the GAC[/b:e646a9d0d3]

              If I’m using xmlreceive I don’t have any problem.
              Have I missed anything?[/b]

              • August 21, 2006 at 6:27 AM #15385
                community-content

                  Hi,

                  I have solved the above problem. It was a strong name key pair problem.

                  But still I have not succeeded in the task. I use a default receive pipeline. It has a xml dissassembler with doc schema property set to req schema.

                  If I use xmlreceive pipeline my orchestration is through. if i use the above said default recv pipeline I get the following error.

                  [b:aeb2213844]The Messaging engine failed to process a message submitted by adapter:FILE Source URL:D:\\Documents and Settings\\Administrator\\Desktop\\r\\*.xml. 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[/b:aeb2213844]

                  When I checked thru HAT, I got the above err msg. ReceivePipeline state is started and there is no end time.

                  Kindly help

                  • August 21, 2006 at 11:34 AM #15386
                    community-content

                      Hi,

                      1.

                      I am using recv pipeline with xml disassembler component. I have also mentioned the doc schema for the same.

                      2. In the orchestration I have 2 shapes a)Receive and b) Send. Both has message type set correctly. How to set message type in the Send Port ?

                      3. Is the BTS.MessageType cntext property being set in the pipeline

                      where to set this?
                      [i:f11a9c831c][b:f11a9c831c]
                      Do I need to set anything in the Recv shape’s Filter Expression property in orchestration. I have just set the Message Property[/b:f11a9c831c][/i:f11a9c831c]

                      Thanks

                • July 25, 2010 at 8:50 PM #25364
                  community-content

                    I had similar problem and all i did was remove old assembly from GAC, change assembly version and reploy… all worked  [:)]

                  • July 25, 2010 at 8:50 PM #25365
                    community-content

                      I had similar problem and all i did was remove old assembly from GAC, change assembly version and reploy… all worked  [:)]

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