Sometimes MDN is generated, but it can't send to partner. So the log is updated the status of this message as error on partner side.
Why MDN can't send to parnter? How can I prevent this situation happened? Or is there any report can see this error?
Sometimes MDN is generated, but it can't send to partner. So the log is updated the status of this message as error on partner side.
Why MDN can't send to parnter? How can I prevent this situation happened? Or is there any report can see this error?
vivian_hw,
are you talking about async MDN? It is possible that the transmitted URL of the sender is wrong. Could you please post the transactions log?
Regards
Heller
vivian_hw,
I had a similar problem recently. Checking th logging of the m-e-c AS2 solution I realized an HTTP 403 from the remote side whenever I sent an (async) MDN to the sending party.
The reason was, that my AS2 instance was not configured as a "sending station" on the remote side at all. They only configured my system as a receiver.
After full configuration of my station for both (receiver role and sender role) everthing worked fine. I could easily send async MDN to the other system.
Hope that helps.
Kind regards,
Giso
Hi all, I am having the same issue with MEC AS2 build 25. Messages are received in batch from the Trading Partner (TP) and MDNs are generated and sent, however sometimes one (or several) MDN will be generated but NOT sent. These are all to the same TP/destination for the same batch of messages, all the same message type.
I have attached the log that we get for the failed message. As you can see the MDN is generated, but there are no further steps in the log (usually it will say that the MDN has been sent).
[Apr 29, 2009 10:20:20 AM] ... : Incoming transmission is a AS2 message, raw message size: 2.00 KB.
[Apr 29, 2009 10:20:20 AM] ... : AS2 message is encrypted.
[Apr 29, 2009 10:20:20 AM] ... : The data has been decrypted using the key "LX".
[Apr 29, 2009 10:20:20 AM] ... : AS2 message is signed.
[Apr 29, 2009 10:20:21 AM] ... : The sender used the algorithm SHA1 to sign the message.
[Apr 29, 2009 10:20:21 AM] ... : Using certificate "MDev2011" to verify signature.
[Apr 29, 2009 10:20:21 AM] ... : Digital signature verified successful.
[Apr 29, 2009 10:20:21 AM] mec_as2-1240968021193-43@LX_M_DEV: Outgoing MDN has been signed with the algorithm "SHA1".
[Apr 29, 2009 10:20:21 AM] mec_as2-1240968021193-43@LX_M_DEV: MDN created, state set to [processed].
Again, this was a batch transfer. 72 messages were successful and 1 was not, for this test.
I looked for the "sender/receiver" setting that giso mentioned but could not find it.
Some other info:
System running MEC AS2: Windows XP, 2GHz CPU dual core with 2GB mem.
MES AS2: 1.1 build 25
Any help is greatly appreciated.
moodlniv,
was this sync or async MDN?
Regards
Heller
Hi heller,
The MDN is set to ASYNCH.
moodlniv,
in async case your partner sends the URL where to expect the MDN in the message. Could you please ensure that receiving MDN on this URL works fine?
Regards
Heller
Hi heller,
The URL is correct. As I said, 1 message in 100 will fail. They are all going to the same TP and therefore getting the same MDN URL.
We did some connectivity tests and there does not seem to be any issues with the connection between us and the TP. The link is stable and operates without any dropped packets.
However, when we use a SYNC connection then we are able to transfer all messages without any issues.
moodlniv,
we made some stress test regarding this issue and could not reproduce it. Any idea to reproduce the problem?
Regards
Heller