none
Xml disassembler failing with reason start element does not match end element RRS feed

  • Question

  • Hi,

    I'am using a WCF-WSHttp adapter to send a very simple message to a WCF service from BizTalk. The service can return a response or throw a BusinessFault or a SystemFault.

    I get the responses and faults returned and captured most part of the time . But one in a hundred message fails with the below error when a BusinessFault or a SystemFault is thrown . They are SOAP faults

    There was a failure executing the response(receive) pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "XML disassembler" Send Port: "xy.Integration.customapplication.CustomService" URI: "https://xyz.xyz.co.xy/CustomService/CustomService.svc" Reason: Start element 'nz/Faults/201' does not match end element 'Reason'. Line 1, position 677.

    I use the below Xpath for the Inbound BizTalk Message Body

    /*[local-name()='Fault']/*[local-name()='Detail' or local-name()='detail']/* | /*[not(local-name()='Fault')]

    My node encoding is Xml.

    I have enabled the Service Trace on the Biztalk server to capture the incoming message and noticed that the messages are not broken .

    Beleive this is one of the item that Microsoft has fixed for BizTalk 2009 in CU 1. But I couldnt notice a similar one for BizTalk 2010 http://support2.microsoft.com/kb/981422

    Any tips would be very much appreciated.

    Thanks

    Suresh

    Sunday, October 5, 2014 6:49 PM

Answers

  • Use a PassThruReceive Pipeline instead of the XMLReceive Pipeline.

    Examine the output from the Adapter, and verify that the output is in fact valid XML.

    Morten la Cour

    • Proposed as answer by Angie Xu Thursday, October 9, 2014 1:47 AM
    • Marked as answer by Angie Xu Monday, October 13, 2014 1:35 AM
    Monday, October 6, 2014 9:12 AM

All replies

  • Could you post the XML message where this error occurs here please?
    Because that error usually occurs when you receive invalid XML. 


    Glenn Colpaert - MCTS BizTalk Server - Blog : http://blog.codit.eu

    Monday, October 6, 2014 6:33 AM
  • The error occurs when your response does not match to the schema specified .Try iterating through your response message xpath can validate whether xpath is returning somesomething .

    Thanks

    Abhishek

    Monday, October 6, 2014 6:52 AM
  • Hi Suresh,

    Have you enabled the “Propagate fault message” option?

    Rachit

    Monday, October 6, 2014 7:21 AM
    Moderator
  • Use a PassThruReceive Pipeline instead of the XMLReceive Pipeline.

    Examine the output from the Adapter, and verify that the output is in fact valid XML.

    Morten la Cour

    • Proposed as answer by Angie Xu Thursday, October 9, 2014 1:47 AM
    • Marked as answer by Angie Xu Monday, October 13, 2014 1:35 AM
    Monday, October 6, 2014 9:12 AM