PipleLine error

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › PipleLine error

Viewing 1 reply thread
  • Author
    Posts
    • September 20, 2006 at 2:31 PM #15765
      community-content

        Hi,

        I am new to BizTalk.
        I am geting following 4 error messages in event viewer when I try to send
        the xml files.
        1)
        There was a failure executing the receive pipeline:
        "Microsoft.BizTalk.DefaultPipelines.XMLReceive" Source: "XML disassembler"
        Receive Location:
        "C:\Excercise\BizTalk\CactusActivityInBound_Test\CACIN_Drop\Input\*.xml"
        Reason: Finding document specification by message type
        "CactusActivityInBound" failed. Verify that the schema is deployed properly.

        2) The Messaging Engine encountered an error publishing a batch of "1"
        messages to the Message Box database for the transport adapter "FILE". Please
        refer to Health and Activity Tracking tool for more detailed information on
        this failure and check the endpoint bindings are correctly configured.

        3) The "FILE" adapter is suspending a message coming from Source
        URL:"C:\Excercise\BizTalk\CactusActivityInBound_Test\CACIN_Drop\Input\*.xml".
        Details:"Error in accessing the part data or one of its fragments. The part
        or fragment may not exist in the database. ".

        4) The Messaging Engine has suspended "1" message(s) from adapter "FILE" due
        to failures in message processing. Please refer to Health and Activity
        Tracking tool for more detailed information on this failure.

        When I deploy the project by right  click -> select deploy in solution
        window, its says:  Deploy: 1 succeeded, 0 failed, 0 skipped.

        What is the reason for this error? Could any one help me to fix this?
        (I already have BizTalk 2004 SP1 in my machine )

      • September 20, 2006 at 9:22 PM #15773
        community-content

          This could be caused by one of the following:

          –         your schema isn’t deployed (ie you have an unrecognized message type – namespace#rootnodename)

          –         you have two schemas deployed anyplace on your system with the same message type

           

          If you don’t know what message type is, it’s one of the main keys BizTalk uses to route message, map messages, and identify data.  It’s made up of the namespace, a #, and the root node name. 

           

          If these are not unique throughout your system, you will need a custom pipeline for any message receiving those messages.  Also, by default using the Xml Receive pipeline BizTalk doesn’t allow unrecognized message.  This too is a setting you’ll need a custom pipeline for if you want to change it.

           

          Hope this helps.

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