bts.messagetype problem

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › bts.messagetype problem

Viewing 2 reply threads
  • Author
    Posts
    • October 28, 2008 at 2:31 PM #21069
      community-content

        Hi,

         

        i may be missing something really basic, but in my send port filter, when i choose the property bts.messagetype == schemaname#root, the message is not recognized… But the schema is published… What possible reasons can exist for this?

         

        Gustavo

         

        Description:
        A message received by adapter “FILE” on receive location “MK.All.Sonaecom.File” with URI “D:\Projects\BizDirect.eTrade\Debug\Sonaecom-MK\*.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. 
         MessageId:  {30760FF6-51C9-408D-88A4-93C8C0A39E5F}
         InstanceID: {DDCCF160-D708-4E11-92ED-EF872FB8F807}

        For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

      • October 28, 2008 at 3:25 PM #21070
        community-content

          The message type property is is constructed as targetnamespace#root

          Are you using the XmlReceive pipeline, it is the Xml Disassembler that promotes the BTS.MessageType property
          You might like to check the the message context of the suspended message to and use the actual value of the BTS.MessageType

           

          • October 29, 2008 at 8:33 AM #21078
            community-content

              Yes, on the receive port i was using the passthrureceive pipeline. That’s why the message could not be processed. Using XmlReceive pipeline it works fine.
              But, i created this port to test the message processing for this specific message type. Now, i have the same problem now, but i’m using an AS2 receive port. And i’m using both an AS2 disassembler and a XML disassembler in the pipeline. And it doesn’t work… Biztalk can’t recognize the message type? Why could it be?
              Gustavo

          • October 29, 2008 at 3:45 AM #21074
            community-content

              Gustavo,

              Whenever I have subscription issues, I change the Send Port subscription to work on BTS.ReceivePortName, re-enlist but do not start the Send Port.

              Run a message through and it will suspend (resumable); open the message in the Admin Console and look at the context properties for the MessageType – copy and paste the proptery value and use that in your BTS.MessageType filter (remembering to take the receive port name filter off).

              Rgds, Nick.

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