FIX: Same message is validated inconsistently and randomly fails with a schema exception

Symptoms
In Microsoft BizTalk Server, multiple instances of the same message are dropped in the receive location. If the messages are processed at the same time, an error that resembles the following may be logged in the Application log:

A message sent to adapter "FILE" on send port "SendPortName" with URI "URI" is suspended.

Error details: There was a failure executing the send pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLTransmit, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "XML assembler" Send Port: " SendPortName" URI: "URI" Reason: Type ‘TypeName’ is not declared.

Cause
The issue occurs because multiple threads try to change the same object when they process multiple requests at the same time.
Resolution

Cumulative update information

The fix that resolves this issue is included in Cumulative Update 2 for BizTalk Server 2013 R2.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Properties

Article ID: 3124052 - Last Review: 12/31/2015 17:43:00 - Revision: 1.0

Microsoft BizTalk Server 2013 R2 Branch, Microsoft BizTalk Server 2013 R2 Developer, Microsoft BizTalk Server 2013 R2 Enterprise, Microsoft BizTalk Server 2013 R2 Standard

  • kbqfe kbsurveynew kbfix kbexpertiseinter KB3124052
Feedback