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.

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


View products that this article applies to.

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.

↑ Back to the top


Cause

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

↑ Back to the top


Resolution

Cumulative update information

The fix that resolves this issue is included in Cumulative Update 2 for BizTalk Server 2013 R2.

↑ 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: kbqfe, kbsurveynew, kbnotautohotfix, kbfix, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 3124052
Revision : 1
Created on : 1/7/2017
Published on : 12/31/2015
Exists online : False
Views : 378