本文介绍了无法在AS2 EDIINT MIC表中创建条目的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在BizTalk 2010中使用AS2同时发送少量消息(比如10个以上)时,我收到事件ID为5720的错误消息,并且消息仍然是发送队列有错误。如果手动我"恢复实例",则在没有
的情况下发送消息任何问题。


系统日志中的完整错误消息是:



执行发送管道失败:" xxx.BizTalkPipelines.Pipelines.PipeSendAs2Edi,xxx.biztalk.BizTalkPipelines,Version = 1.0.0.0, Culture = neutral,PublicKeyToken = 91ce7d1d964faf86"来源:"AS2编码器"发送端口:"SP1"
URI:" http://xxx.xx.xxx.xxx/prod/as2"原因:无法在AS2 EDIINT MIC表中创建条目。这可能是由写入表中的重复AS2-From,AS2-To和MessageID组合引起的。 错误:事务(进程ID 64)
在另一个进程的锁资源上死锁,并被选为死锁牺牲品。重新运行该事务。



我认为AS2-From和AS2-To没有任何问题(没有重复),因为在恢复实例时,消息发送没有任何变化。


有没有人有解决这个问题的线索?


谢谢

解决方案

when sending simultaneously a few messages (say more then 10) using AS2 in BizTalk 2010, I get error message with event ID 5720, and messages remain it the send queue with error. If manually I "resume instance", messages are sent without any problem.

The full error message in system log is:

There was a failure executing the send pipeline: "xxx.BizTalkPipelines.Pipelines.PipeSendAs2Edi, xxx.biztalk.BizTalkPipelines, Version=1.0.0.0, Culture=neutral, PublicKeyToken=91ce7d1d964faf86" Source: "AS2 encoder" Send Port: "SP1" URI: "http://xxx.xx.xxx.xxx/prod/as2" 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 64) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

I believe that there is nothing wrong with the AS2-From and AS2-To (no duplicates) because when resuming the instance, the messages are sent without any change.

Does anyone have a clue to solve this problem?

Thank you

解决方案


这篇关于无法在AS2 EDIINT MIC表中创建条目的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-18 18:51