- This topic has 3 replies, 1 voice, and was last updated 9 years, 2 months ago by
.
-
Posts
-
-
I am working on how AS2 process happens. I am using my system and another dev system to communicate by exchanging AS2 messages. I am able to receive the file(Non-EDI) sent from my system but along with that, the other system is also receiving a 0kb file. Does any one has any idea that do I have to modify any settings?
-
I know this is an old post, and hopefully has been resolved by now, but I’ll comment just in case it helps someone else. My first thought is that somehow the MDN is being transmitted as a payload. I had a similar issue with receiving an AS2 payload. The file send port that subscribed to the message created two files. One was the AS2 payload, the other was a zero byte file created by the asynchronous MDN. Check the subscription filters on your AS2 ports. The EdiIntAS.IsAs2PayloadMessage property might be helpful.
-
Thanks for your response
I used the same filter to not consider 0kb file for my actual payload process. The problem with that is, I ended up with so many suspended(resumable) messages and full of event logs saying there no port subscribed for these messages.
Finally, I had to create a send port subscribing to the 0kb files and routing them to a folder in the server.
Do we have an option in BizTalk with which we can simply delete messages matching with a particular subscription, without storing any where?
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.