none
Document type "http://XSD.***.net/Get***/V1#RESULT" does not match any of the given schemas. RRS feed

  • Question

  • Dear Experts,
    Below error is shown up when I tried to use my custom pipeline. BizTalk is receiving messages through schema "http://XSD.***.net/Get***/V1#RESULT" when I use 'Receive XML'.
    I have to de-batch the incoming RESULT, that is response of orchestration request.
    Single messages are coming successful but I want to de-batch incoming message.
    Kindly help me in this regard

    There was a failure executing the response(receive) pipeline:
    "GSOC002001.Production.Biztalk.GetData.ReceiveResponsePipeline,
    GSOC002001.Production.Biztalk, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f6fdc96bd71c9803" Source: "XML disassembler" Send Port:
     "SendReqToGetHajDataSendPort" URI: "http://******/Integration/EST/GetData?wsdl"
    Reason: Document type "http://XSD.***.net/Get***/V1#RESULT" does not match any of the given schemas.

    Regards,
    Muhammad Masood

    Wednesday, August 26, 2015 6:21 AM

Answers

  • Hi Muhammad,

    Reason: Document type "http://XSD.***.net/Get***/V1#RESULT" does not match any of the given schemas.

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

    The best way to check if a Schema is Deployed and you can find it Schema folder of the <All Artifacts> Application.


    Thanks, If my reply is helpful please mark as answer or vote as helpful.

    Wednesday, August 26, 2015 9:43 AM
    Moderator
  • Masood, it looks like you custom pipeline is not promoting the message type, either you need to promote the message type in your custom pipeline like given below 
    
    // promote MessageType and Schema SchemaStrongName
        // in order to the Biztalk to have a unique key
        // for evaluating subscription
        // As an example for Namespace#Root= http://TestCustomPipeline.Schema1#roottagName
          outMsg.Context.Promote("MessageType", 
          "http://schemas.microsoft.com/BizTalk/2003/system-properties",
          "Namespace#Root");
    
    or use XML Disassembler pipeline component in your custom pipeline in the Disassemble stage
    
    This component takes care of promoting context properties, thus also the message type property. If you only have your own pipeline component in the pipeline, then the context properties will not get promoted
    
    
    Thanks,
    Chandra Kumar

    Wednesday, August 26, 2015 1:22 PM

All replies

  • Hi Muhammad,

    Can you verify is the document schema( http://XSD.***.net/Get***/V1#RESULT) exists in BizTalk Management DB.

    You can also validate it through BizTalk admin console Schema node .

    Or try Querying

    select * from BT.DocumentSpec where msgtype like '%Namespace#rootNode( Your debatched messagetype) %'

    Thanks

    Abhishek


    Wednesday, August 26, 2015 6:31 AM
  • Dear Abhishek,

    I have verified above query, document schema is there in bt_documentspec table and id having only 1 record.

    Please advise something else

    -Muhammad

    Wednesday, August 26, 2015 7:02 AM
  • You can verify if the MessageType is promoted on the suspended message or not. If it is not then the issue could arise if in your custom pipeline you do not use the XML Disassembler or if you're using a custom disassembler and NOT Promote MessageType. If you use the XML Disassembler then it does the MessageType promotion for you.

    Regards.

    Wednesday, August 26, 2015 7:08 AM
  • Dear Shankycheil,

    m using XML Disassembler, this error occur in 2 conditions, when I use custom pipeline or when I use Passthrough, rest it is okay with XML receive.

    -Muhammad

    Wednesday, August 26, 2015 7:37 AM
  • Then ur custom pipline is not promoting the message type.

    You can add a xmldisassembler in ur custome pipeline or promiote the messagetype in ur pipeline component code.


    Regards &lt;br/&gt; When you see answers and helpful posts,&lt;br/&gt; please click Vote As Helpful, Propose As Answer, and/or Mark As Answer

    Wednesday, August 26, 2015 7:45 AM
    Answerer
  • Hi Muhammad,

    Reason: Document type "http://XSD.***.net/Get***/V1#RESULT" does not match any of the given schemas.

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

    The best way to check if a Schema is Deployed and you can find it Schema folder of the <All Artifacts> Application.


    Thanks, If my reply is helpful please mark as answer or vote as helpful.

    Wednesday, August 26, 2015 9:43 AM
    Moderator
  • Masood, it looks like you custom pipeline is not promoting the message type, either you need to promote the message type in your custom pipeline like given below 
    
    // promote MessageType and Schema SchemaStrongName
        // in order to the Biztalk to have a unique key
        // for evaluating subscription
        // As an example for Namespace#Root= http://TestCustomPipeline.Schema1#roottagName
          outMsg.Context.Promote("MessageType", 
          "http://schemas.microsoft.com/BizTalk/2003/system-properties",
          "Namespace#Root");
    
    or use XML Disassembler pipeline component in your custom pipeline in the Disassemble stage
    
    This component takes care of promoting context properties, thus also the message type property. If you only have your own pipeline component in the pipeline, then the context properties will not get promoted
    
    
    Thanks,
    Chandra Kumar

    Wednesday, August 26, 2015 1:22 PM