none
The document type does not match any of the given schemas. batching RRS feed

  • Question

  • I am aggregating messages(batching) in Orchestation by calling pipeline. I have send pipeline where I have standard assemble component and custom pipeline in encode to assign some values .

    When I test it I get following error There was a failure executing the send pipeline: "Zones._870.Pipeline.Send870Pipeline, Zones.870, Version=1.0.0.0, Culture=neutral, PublicKeyToken=51b3a99d8425ff5a" Source: "ZonesAssignGUID" Send Port: "SendToAX870" URI: "C:\File_Out\Ingram\870\%MessageID%.xml" Reason: The document type "http://schemas.microsoft.com/dynamics/2011/01/documents/Message#Envelope" does not match any of the given schemas.  

    Can somebody help me how to resolve this issue? 

    Wednesday, July 16, 2014 9:55 PM

Answers

All replies

  • I am aggregating messages(batching) in Orchestation by calling pipeline. I have send pipeline where I have standard assemble component and custom pipeline in encode to assign some values . When I test it it get suspended with above error. I was think from orchestration I should give back envelope message as output . I tried it by Message Assignment assigning something like

    EnvelopeMsgVar = XMLDocVar where XMLDocument veriable is aggregated pipeline output.

    But no luck still same error. .In above error ZonesAssignGUID is first custom pipeline component at encoder .

     Can somebody help me to understand what could be wrong. 

    Wednesday, July 16, 2014 10:39 PM
  • ""http://schemas.microsoft.com/dynamics/2011/01/documents/Message#Envelope" does not match any of the given schemas.  "

    Either that schema is not deployed or you have configured some Document schemas on Xml Assembler and this is not one of them.

    Thursday, July 17, 2014 3:43 AM
    Moderator

  • You can check BT_DocumentSpec table in BizTalk management DB for schema  type deployed or  any duplicate instance having same message type  .You can fire a select Query as

    select * from BT_DocumentSpec where msgtype like '%http://schemas.microsoft.com/dynamics/2011/01/documents/Message#Envelope%'

    Thanks

    Abhishek

    Thursday, July 17, 2014 4:13 AM
  • Yes this is configured schema as envelope schema. This one is deployed in biztalk . I tried whatever suggest below query and return one record. Not sure but looks like error message misguiding here.
    select * from BT_DocumentSpec where msgtype like '%http://schemas.microsoft.com/dynamics/2011/01/documents/Message#Envelope%'
    Thursday, July 17, 2014 3:08 PM
  • There is only one instance in this table
    Thursday, July 17, 2014 3:09 PM
  • The best way to check if a Schema is Deployed is to look in the Schema folder of the <All Artifacts> Application.

    Do you have a Document schema set on the Assembler component?  You probably don't need one.

    Thursday, July 17, 2014 3:41 PM
    Moderator
  • I can see envelope schema under all artifacts->schemas. Yes I have document schema set on assembler component. Let me try removing it and will update you,if it makes difference?

    Thursday, July 17, 2014 3:51 PM
  • I try to remove document schema from assemble . No change suspended with same reason
    Thursday, July 17, 2014 3:58 PM
  • No, not from the Assembly, from the Xml Assembler Pipeline Component.
    Thursday, July 17, 2014 4:23 PM
    Moderator
  • Yes I removed it from XML assembler component in custom pipeline as well kept DocumentSpecNames empty from pipeline properties in send port. Only difference I saw in suspended messages context that earler it use to promote http://schemas.microsoft.com/dynamics/2011/01/documents/Message#Envelope as MessageType. Now it did not. 
    Thursday, July 17, 2014 4:29 PM
  • As mentioned only change that message type not get promoted but still suspended. I come across this link

    http://adventuresinsidethemessagebox.wordpress.com/2012/09/03/the-document-type-does-not-match-any-of-the-given-schemas-encountered-in-an-xml-disassemblerassembler-based-scatter-gather-scenario/#comment-1438

    but I guess setting DocumentSpecNames  wmpty on send pipeline is same what this pipeline do . So no luck. Any thing else do you think I should look. One thing I like to mention my orchestartion send port is map to document schema nor enevelope schema. Do you think any thing there could be issue. 

    Thursday, July 17, 2014 7:06 PM
  • some how after restart it is working .Not sure what was exact issue
    • Proposed as answer by vittalaranga Friday, July 18, 2014 9:24 AM
    • Marked as answer by Pengzhen Song Wednesday, July 23, 2014 1:22 PM
    Thursday, July 17, 2014 9:26 PM
  • This answer should be given to John. 

    My Technet Articles

    If you like this or another reply, vote it up!
    If you think this or another reply answers the original question, mark it or propose it as an answer.


    Mauricio Feijo
    www.mauriciofeijo.com

    Monday, March 19, 2018 2:53 PM