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

Van toepassing: BizTalk Server 2013 BranchBizTalk Server 2013 DeveloperBizTalk Server 2013 Enterprise

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.

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.

Status


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