none
Envelope debatching and validation problem after BTS 2010 CU7 update RRS feed

  • Question

  • Hi

    Hoping someone can help.

    We've been having some problems validating debatched messages in a receive pipeline, using XmlDisassembler, since implementing BizTalk 2010 CU7.
    We previously were at CU5.

    An Envelope message is passed in and if Validate Document is set to False then it debatches OK.
    However, if Validate Document is set to True then we get one of two types of error...

    With Multiple Body messages

    There was a failure executing the receive pipeline: "<Pipeline Name>"
    Source: "XML disassembler"
    Receive Port: "<Receive Port Name>"
    URI: "<Input Folder>\*.xml"
    Reason: The document failed to validate because of the following error:
    "Could not find schema information for the element '<namespace>:<root node>'." . 

    Note: this is document schema (which is deployed correctly)

    With Single Body message

    An output message of the component "XML disassembler" in receive pipeline "<Pipeline Name>" is suspended due to the following error:
         Could not find schema information for the attribute 'Value'. .
     The sequence number of the suspended message is 1. 
     
    Note: the only place Value appears as an attribute is in a section defined using an <Any> node (so shouldn't fail validation at all)
     
    If the individual Body messages in the error are copied
    then they successfully validate against the schema in VS 2010

    If CU7 is then removed validation (and debatching) work OK.

    Does anyone know why this is happening and, more importantly, how to fix it please?

    (We need CU7 and it allows .Net Framework 4.5.1 to be used on the server without host instances falling over intermittently)

    Thanks

    Nick

    Monday, May 11, 2015 10:56 AM

Answers

  • Thanks for replying

    You're probably right, will do so

    A work around was to use the XmlValidator component for validation instead (that works Ok with CU7)

    Thanks again

    Nick

    • Marked as answer by nick_b Wednesday, May 13, 2015 9:29 AM
    Wednesday, May 13, 2015 9:29 AM

All replies

  • According to your description above, you need consider contacting Microsoft support, they will help you look into it further.
    Wednesday, May 13, 2015 8:14 AM
  • Thanks for replying

    You're probably right, will do so

    A work around was to use the XmlValidator component for validation instead (that works Ok with CU7)

    Thanks again

    Nick

    • Marked as answer by nick_b Wednesday, May 13, 2015 9:29 AM
    Wednesday, May 13, 2015 9:29 AM