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.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.
The fix that resolves this issue is included in the following cumulative updates for BizTalk Server:
Cumulative Update 5 for BizTalk Server 2013
Note To enable this update, set the PromoteDocSpecName property to False on the ESBDipatcher component.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about service pack and cumulative update list for BizTalk Server.
Learn about BizTalk Server hotfixes and cumulative update support.