Skip to Content
avatar image
Former Member

Seeburger AS2: Error on send - illegal MDN - content-type not supported

Hi,

I build up a connection to a partner to send ORDRSP via AS2.

Unfortunately I'm receiving an error in the Seeburger Workbench:

Received illegal MDN - content-type not supported!

I set up the content-type: application/EDI-X12. I have already tested different content types, but I always get the error. The whole conficuration is similar to our other partners.

Do you know, what this error means and give me an advice please.

Thanks a lot

Frank

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Sep 21, 2009 at 02:02 PM

    Hi,

    I tried different content types, but always get the same error.

    application/EDI-X12

    application/octet-stream

    application/xml

    application/edifact

    Does anyone know this? What does the error mean?

    Best regards

    Frank

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      That sounds very odd. Are you sure that the endpoint you are sending to is actually an AS2 server ? It could very well be that you are sending to a generic endpoint which is not returning an MDN. You should check the AS2 manual and enable transmissionDataDump which will dump the message transmitted TO the endpoint as well as the response received FROM the endpoint in the seeburger/AS2... folder (check the manual and masterinstallationguide) for details.

  • avatar image
    Former Member
    Sep 25, 2009 at 01:24 PM

    Hello Frank,

    Not sure, but you can giev a try on the following.

    1. The encrytpion method (RSA, DES..) used on your partner side are the same or not.

    2. The certificates used are upto date and valid. i.e. since you are getting an error during Synchronous MDN, your partner might not be using your correct public key before sending the MDN.

    You should be using only one receiver channel, if you are using synchronous MDN. Separate channels fro MDN are required when you use asynchronous MDN's.

    Check in the Receiver Agreement, if you have mentioned the correct certificates of sender and receiver.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 22, 2009 at 02:52 PM

    The EDI-partner told me the wrong URL. That was all.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 14, 2013 at 11:20 AM

    Hello Frank,

    I'm facing the same error as your "Received illegal MDN - content-type not supported!"

    May I know did you found the solution or root cause of this error?

    Thx & regards,

    Doo

    Add comment
    10|10000 characters needed characters exceeded