Problem with sending 1.7MB files or larger from logic apps AS2 to B2B sterling integrator

Question

Hello,

Our organization, referred to as MKT Inc., we use B2B Sterling Integrator as our AS2 server. Our trading partner, lets call it Contoso, employs Azure Logic Apps for their AS2. We exchange xml files, sending a receiving.

However, we've recently encountered an issue where we are unable to receive files from Contoso's AS2 server. The error message in our B2B system indicates a decryption error. Strangely, we've observed that smaller files are being processed successfully, while larger files (around 1.7MB or slightly more) are not going through.

Numerous files under 1MB continue to be received without any issues.

MKT Inc also has 25 other trading partners and we receive and decrypt large files in a regular basis. One of our trading partner is sending us files, as large as 15MB every hour and B2B AS2 is able to decrypt without any issues.

I asked Contoso to send me the problematic XML file via email attachment. I test using a cloud AS2 gateway, specifically as2gateway.com, I encrypted and transmitted the file from AS2Gateway.com to our B2B AS2 server, resulting in successful decryption.

We're seeking assistance in understanding the root cause of this decryption error and why it appears to be specifically affecting files of certain sizes. Any insights or suggestions you can provide to help us resolve this matter would be greatly appreciated.

Answer 1

@Lumia One Lumia Thanks for reaching out.

The decryption error is occurring only for larger files that are being received from Contoso's AS2 server. This could be due to a number of factors, such as network issues, configuration issues, or even issues with the file itself.

• One possible reason for this issue could be related to the maximum message size limit set on your B2B AS2 server. It is possible that the server is configured to accept messages up to a certain size, and larger messages are being rejected or causing decryption errors. You may want to check the configuration settings on your B2B AS2 server to ensure that the maximum message size limit is set appropriately.
• Another possible reason could be related to the encryption algorithm used by Contoso's AS2 server. It is possible that the encryption algorithm used by Contoso's AS2 server is not compatible with your B2B AS2 server, resulting in decryption errors for larger files. You may want to check with Contoso to ensure that they are using a compatible encryption algorithm.
• It is also possible that there may be network issues or other configuration issues that are causing the decryption errors. You may want to check the logs on your B2B AS2 server to see if there are any error messages or other indications of what might be causing the issue.
• In any case, it would be helpful to gather more information about the specific error message that you are receiving on your B2B AS2 server, as well as any error messages or other indications of issues that you are seeing in the logs. This information can help to narrow down the root cause of the issue and identify potential solutions.

If the above doesn't help to verify the root cause the this would need one on one support to review the logs to assist you further and I will suggest you to engage us over the support request to review it. In case if you don't have the support plan then please let me know.

Answer 2

This problem is solved now. We ask Contoso what was the solution (or how did they fixed it) and here is their response:

We actually don't know. In the call with Microsoft we did a new test and then everything worked perfectly. Now they also have shared a blog post from the 16th of October about the content-type that is recognized as pdf instead of the correct content-type that was expected.   So maybe there was a change pushed from Microsoft to the Azure cloud, but we can't find anything back about that. We did multiple test with messages that went in error in the past with the decryption errors, and now they went through OK

Answer 3

This problem is solved now. We ask Contoso what was the solution (or how did they fixed it) and here is their response:

    We actually don't know. In the call with Microsoft we did a new test and then everything worked perfectly. Now they also have shared a blog post from the 16th of October about the content-type that is recognized as pdf instead of the correct content-type that was expected.   So maybe there was a change pushed from Microsoft to the Azure cloud, but we can't find anything back about that. We did multiple test with messages that went in error in the past with the decryption errors, and now they went through OK