Calling Orchestration

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

Viewing 2 reply threads
  • Author
    Posts
    • November 7, 2006 at 10:13 AM #16350
      community-content

        Hi,

                I am trying to call another orchestration from my orchestration and here is the error I am seeing the event viewer log. Any ideas what is going wrong in here ?

        A message received by adapter "FILE" on receive location "CallOrchestration_1.0.0.0_CallOrchestration.receivePO_IncomingPOPort_a7c3c1c570380ef7_ReceiveLocation" with URI "C:\CallOrchestration\In\*.xml" is suspended.
         Error details: There was a failure executing the receive pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "XML disassembler" Receive Port: "CallOrchestration_1.0.0.0_CallOrchestration.receivePO_IncomingPOPort_a7c3c1c570380ef7" URI: "C:\CallOrchestration\In\*.xml" Reason: No Disassemble stage components can recognize the data.  
         MessageId:  {248DC3B4-BF55-4ED1-A62B-B6F98F5CC626}
         InstanceID: {F9E5D3F9-0665-488B-A835-D9A228890CFE}

        Thanks in advance

        Josh P

         

      • November 7, 2006 at 9:30 PM #16354
        community-content

          Seems there is some problem with the sample xml file been dropped in the folder

          C:\CallOrchestration\In\*.xml

          Validate the xml against the schema.Are you using any Namespace in the xml file?

           

          Hope you find it helpful.

        • November 8, 2006 at 6:54 AM #16360
          community-content

            Can you copy the suspended message out to the filesystem and run the flat file disassembler on it?  If the encoding specified in the xml doesn't match the encoding of the file that can cause problems.

            Looks like if that's your problem and you need to handle unicode here's a few pointers:

            http://coditsam.blogspot.com/

            http://blogs.msdn.com/csdcustomerexperience/archive/2006/01/24/517228.aspx

             

            • November 8, 2006 at 12:24 PM #16362
              community-content

                Yes, BOM ( byte order mark) was creating the problem. I was modifying the input instance xml file in textpad and interestingly enough when I save the file, textpad removes preceding BOM (0xff, 0xfe) from the file and Biztalk was throwing exception because of missing BOM. Though there is a work around in textpad to fix this, I would recommend using notepad for modifying the input instance xml.

                Thanks a lot for the help guys.

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