Document Type does not match any of the given schemas

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Document Type does not match any of the given schemas

Viewing 0 reply threads
  • Author
    Posts
    • #21643

      Ok, my company is new to biztalk and we are having some issues.  I receive a batch message in biztalk and capture some of the header information and insert it into a db and receive back the inserted primary key.  Next I construct a copy of the original message and set the value of a node to the returned primary key.  Next I need to debatch the message, so I transform the copied message into a new message type for debatching.  I then call a receive pipeline from within my orchestration to parse apart the message into individual messages tied to an envelope schema.  We have this within an Atomic scope and have declared a local variable and local message of type envelope schema for the pipeline.  We have added the appropriate reference and have the following line of code in an expression shape to call the pipeline.

      RcvPipeOutput = Microsoft.XLANGs.Pipeline.XLANGPipelineManager.ExecuteReceivePipeline(typeof(CriticalChangePipelines.DebatchCriticalChangeAttributes),CriticalChangeAttributesContainerMsg);

      The pipeline does have the proper document and envelope collection set.  My problem is that the pipeline component is giving an error of Document Type does not match any of the given schemas.  Below is the container schema that gets passed into the pipeline and below that is the envelope schema.  Have we by chance not understood how to de-batch a message and screwed up our host and envelope schemas?

        <?xml version=”1.0″ encoding=”utf-16″ ?>
      – <xs:schema xmlns:b=”http://schemas.microsoft.com/BizTalk/2003” xmlns=”Graebel.Schemas.CriticalChange.CriticalChangeAttributeDocument” targetNamespace=”Graebel.Schemas.CriticalChange.CriticalChangeAttributeDocument” xmlns:xs=”http://www.w3.org/2001/XMLSchema“>
      – <xs:element name=”CriticalChangeAttributes”>
      – <xs:annotation>
      – <xs:appinfo>
        <b:recordInfo rootTypeName=”CriticalChangeAttributes” xmlns:b=”http://schemas.microsoft.com/BizTalk/2003” />
        </xs:appinfo>
        </xs:annotation>
      – <xs:complexType>
      – <xs:sequence>
        <xs:element name=”AttributeName” type=”xs:string” />
        <xs:element name=”AttributeOldValue” type=”xs:string” />
        <xs:element name=”AttributeNewValue” type=”xs:string” />
        <xs:element name=”CreatedBy” type=”xs:string” />
        <xs:element name=”CriticalChangeId” type=”xs:int” />
        </xs:sequence>
        </xs:complexType>
        </xs:element>
        </xs:schema>

      and here is the envelope schema:

      <?xml version=”1.0″ encoding=”utf-16″ ?>
      – <xs:schema xmlns:ns0=”Graebel.Schemas.CriticalChange.CriticalChangeAttributeDocument” xmlns:b=”http://schemas.microsoft.com/BizTalk/2003” xmlns=”http://CriticalChangeSchemas.CriticalChangeAttributeDocumentEnvelope” xmlns:ns1=”http://CriticalChangeSchemas.PropertySchema.PropertySchema” targetNamespace=”http://CriticalChangeSchemas.CriticalChangeAttributeDocumentEnvelope” xmlns:xs=”http://www.w3.org/2001/XMLSchema“>
        <xs:import schemaLocation=”.\criticalchangeattributesdocument.xsd” namespace=”Graebel.Schemas.CriticalChange.CriticalChangeAttributeDocument” />
      – <xs:annotation>
      – <xs:appinfo>
        <b:schemaInfo is_envelope=”yes” xmlns:b=”http://schemas.microsoft.com/BizTalk/2003” />
      – <b:imports>
        <b:namespace prefix=”ns1″ uri=”http://CriticalChangeSchemas.PropertySchema.PropertySchema” location=”.\propertyschema.xsd” />
        </b:imports>
      – <b:references>
        <b:reference targetNamespace=”Graebel.Schemas.CriticalChange.CriticalChangeAttributeDocument” />
        </b:references>
        </xs:appinfo>
        </xs:annotation>
      – <xs:element name=”CriticalChangeIndividualAttribute”>
      – <xs:annotation>
      – <xs:appinfo>
        <b:recordInfo body_xpath=”/*[local-name()=’CriticalChangeIndividualAttribute’ and namespace-uri()=’http://CriticalChangeSchemas.CriticalChangeAttributeDocumentEnvelope’%5D&#8221; />
      – <b:properties>
        <b:property name=”ns1:CriticalChangeId” xpath=”/*[local-name()=’CriticalChangeIndividualAttribute’ and namespace-uri()=’http://CriticalChangeSchemas.CriticalChangeAttributeDocumentEnvelope’%5D/*%5Blocal-name()=’CriticalChangeAttributes&#8217; and namespace-uri()=’Graebel.Schemas.CriticalChange.CriticalChangeAttributeDocument’]/*[local-name()=’CriticalChangeId’ and namespace-uri()=”]” />
        </b:properties>
        </xs:appinfo>
        </xs:annotation>
      – <xs:complexType>
      – <xs:sequence>
        <xs:element ref=”ns0:CriticalChangeAttributes” />
        </xs:sequence>
        </xs:complexType>
        </xs:element>
        </xs:schema>

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