- 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:
Error details: There was a failure executing the send pipeline: "_COMM.SendPipelineXSLTAS2, _COMM, Version=18.104.22.168, 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.
Article ID: 3202751 - Last Review: 14 Nov 2016 - Revision: 1