Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. "Document type does not match any of the given schemas" error message after you apply Cumulative Update 4 for BizTalk Server 2013

"Document type does not match any of the given schemas" error message after you apply Cumulative Update 4 for BizTalk Server 2013

View products that this article applies to.

Symptoms

After you apply Cumulative Update 4 for Microsoft BizTalk Server 2013, your BizTalk application starts failing and returns a "Document type does not match any of the given schemas" (XmlDasmException) error message. For example, the error message that you receive resembles the following:

Microsoft.XLANGs.Pipeline.XLANGPipelineManagerException: There was a failure executing pipeline "Contoso.BizTalk.Pipelines.Rcv_xxx.Rcv_xxx". Error details: "Document type "http://xxxxxxxxx" does not match any of the given schemas. ". --->Microsoft.BizTalk.Component.XmlDasmException
at Microsoft.BizTalk.Component.XmlDasmReader.CreateProcessor(String docType)
at Microsoft.BizTalk.Component.XmlDasmReader.ShiftState(Boolean readState)
at Microsoft.BizTalk.Component.XmlDasmReader.Read()
at Microsoft.BizTalk.Component.XmlDasmComp.Disassemble2(IPipelineContext pc, IBaseMessage inMsg)
at Microsoft.BizTalk.Component.XmlDasmComp.Disassemble(IPipelineContext pc, IBaseMessage inMsg)
at Microsoft.BizTalk.PipelineOM.DisassemblingParserStage.Disassemble(IBTMPipelineContext pc, IBaseMessage inMsg, Int32 dasmStageIndex)
at Microsoft.BizTalk.PipelineOM.ReceivePipeline.Execute(IBaseMessage msgIn)
at Microsoft.BizTalk.PipelineOM.PipelineManager.ExecuteReceivePipeline(ReceivePipeline receivePipeline, IBaseMessage msg, IResourceTracker& rt)
at Microsoft.XLANGs.Pipeline.XLANGPipelineManager.ExecutePipeline(ReceivePipeline p, XLANGMessage inMsg)

This issue is seen only when an Envelope message is transformed by using ESBTransform and submitted to XMLDASM.

↑ Back to the top

Resolution

The fix that resolves this issue is included in the following cumulative updates for BizTalk Server:

Cumulative Update 2 for BizTalk Server 2016

Cumulative Update 6 for BizTalk Server 2013 R2

Cumulative Update 5 for BizTalk Server 2013

Note To enable this update, set the PromoteDocSpecName property to False on the ESBDipatcher component.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

Keywords: kb, kbqfe, kbsurveynew, kbfix, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 3194297
Revision : 4
Created on : 5/15/2017
Published on : 5/26/2017
Exists online : False
Views : 470