Consider the following scenario:
Biztalk Server tries to send many messages (such as 20 or more messages) through the Applicability Statement 2 (AS2) specification at the same time.
Biztalk Server tracking on the Send port is enabled.
AS2 Sender message tracking on party agreement is enabled.
In this scenario, you may receive an error message that resembles the following:
A message sent to adapter "HTTP" on send port "SEALING_AS2" with URI "http://as2xxxxxxxxxxxxxx" is suspended.
Error details: There was a failure executing the send pipeline: "_COMM.SendPipelineXSLTAS2, _COMM, Version=220.127.116.11, Culture=neutral, PublicKeyToken=849b3f7212ac46ca" Source: "AS2 encoder" Send Port: "SEALING_AS2" URI: "http://as2.xxxxxxxxxxxxxxxxxx"
Reason: Unable to create the entry in the AS2 EDIINT MIC table. This could be caused by duplicate AS2-From, AS2-To and MessageID combinations being written to the table.
Error: Transaction (Process ID 115) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Cumulative update information
The fix that resolves this issue is included in the following cumulative updates for BizTalk Server:
Cumulative Update 6 for BizTalk Server 2013
Cumulative Update 5 for BizTalk Server 2013 R2.
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.