Troubleshooting AS2


Most issues occur during the initial setup of an AS2 connection. These issues include:

Some issues can occur when a previously working connection no longer works. These issues can include:

Problems Setting Up Your AS2 Identity

If you are having problems setting up your AS2 Identity then the issue could be caused by:

ISSUERESOLUTION STEPS
AS2 Identity, or Name, is not accepted.Make sure you enter a unique Identity, or Name. Check that you haven’t already used the Identity, or Name.
My encryption/signing public certificate is not accepted.

Make sure that the certificate is in PEM or CRT format.

Make sure that the certificate is not expired or revoked.

Make sure that the public certificate corresponds to the private key that you entered.

My encryption/signing private key is not accepted.

Make sure that the key is in PEM or CRT format.

Make sure that the key is not expired or revoked.

Make sure that the private key corresponds to the public certificate that you entered.

Make sure that the private key is not password protected or encrypted. To see if a private key is protected, open the PEM or CRT file in a text editor and look at the first line. If it says -----BEGIN ENCRYPTED PRIVATE KEY----- then the key is password protected or encrypted and cannot be imported.

Problems Setting Up a Trading Partner

If you are having problems configuring a trading partner then the issue could be caused by:

ISSUERESOLUTION STEPS
Trading partner public certificate is not accepted.

Make sure that the certificate is in PEM or CRT format.

Make sure that the certificate is not expired or revoked.

Trading Partner Having Problems Sending to Me

There are several issues that could cause incoming AS2 transmissions from your trading partners to fail:

ISSUERESOLUTION STEPS
Incorrect URL being used.Make sure your trading partner is sending the AS2 transmission to the correct endpoint URL.
Incorrect port being used.Make sure that your trading partner is sending the AS2 transmission to port 443 of your Files.com site.
Incorrect AS2 trading partner Identity being used.

The trading partner is specifying an AS2 Identity that does not match your configuration.

Make sure that the AS2 Identity that the trading partner is trying to use exactly matches the AS2 Identity that you specified for them.

This is also known as the "AS2-From" header setting, which you can view in the AS2 Logs.

Incorrect AS2 Identity being used.

The trading partner has not specified your correct AS2 Identity.

Make sure that the AS2 Identity being used by the trading partner to identify you exactly matches your AS2 Identity.

If you have multiple AS2 Identities, then make sure that your trading partner is using the correct one. Check the configuration for the trading partner and confirm that the AS2 Identity shown in the My AS2 Name/Identity column matches what your trading partner is using.

This is also known as the "AS2-To" header setting, which you can view in the AS2 Logs.

Trading partner is using an incorrect encryption certificate.

The trading partner should be using your public certificate to encrypt AS2 transmissions to you. Make sure that the certificate they are using is exactly the same one as you imported in your AS2 identity.

If you have multiple AS2 Identities, make sure that the trading partner is using the correct corresponding certificate.

Resend the trading partner your correct public encryption certificate and verify that they are using it for AS2 transmissions to you.

You are using an incorrect trading partner signing certificate.

The trading partner will be using their private certificate to sign AS2 transmissions to you. You will have received a corresponding public certificate from your trading partner. Make sure that the corresponding trading partner public certificate that you are using matches the public certificate that they provided you with.

Check with the trading partner that the public certificate that they sent you corresponds to the private certificate that they are using to sign their AS2 transmissions to you.

Problems Sending to a Trading Partner

There are several issues that could cause outgoing AS2 transmissions to your trading partners to fail:

ISSUEResolution Steps
Incorrect URL being used.

Make sure you are sending the AS2 transmission to the correct endpoint URL for your trading partner.

Check with your trading partner that the endpoint URL is correct and not being blocked by firewall rules.

Invalid, expired, or untrusted SSL certificate is being used at the AS2 URL.

SSL certificates should be valid, chained and trusted. Use an online SSL Certificate checker, such as SSL Shopper, to check the trading partner’s AS2 URL and make sure that the SSL certificate being used is valid.

If an invalid, unchained, or self-signed SSL certificate is being used by the trading partner, you can configure Files.com to allow this less secure connection by editing the trading partner entry, and change the Server certificate option to "Allow self-signed, unchained, expired, or non-matching TLS/SSL certificate".

Incorrect AS2 trading partner Identity being used.

You have specified an AS2 Identity that does not match your trading partner’s configuration.

Make sure that the AS2 Identity that you are trying to use exactly matches the AS2 Identity that they provided you with.

This is also known as the "AS2-To" header setting, which you can view in the AS2 Logs.

Incorrect AS2 Identity being used.

You are not using your correct AS2 Identity.

Make sure that your AS2 Identity that you are using with the trading exactly matches the AS2 Identity that you provided to them.

If you have multiple AS2 Identities, then make sure that you are using the correct one. Check the configuration for the trading partner and confirm that the AS2 Identity shown in the My AS2 Name/Identity column matches what you are using.

This is also known as the "AS2-From" header setting, which you can view in the AS2 Logs.

You are using an incorrect partner encryption certificate.

You should be using your trading partner’s public certificate to encrypt AS2 transmissions to them. Make sure that the certificate you imported for the trading partner is the correct one.

The trading partner will have provided you with this certificate. Check with them that you have the correct one.

The trading partner is using an incorrect public certificate.

The trading partner should be using your public certificate to verify the digital signature of your AS2 transmissions to them. You will have provided them with a public certificate that corresponds to your private certificate. Make sure that the public certificate that you sent to the trading partner is the same one as the one you used to configure your AS2 identity.

If you have multiple AS2 Identities, then make sure you sent the trading partner the correct public certificate that corresponds to the AS2 Identity that you are using with them.

Invalid or Badly Formatted MDN

Typically, the content of a returned MDN is formatted as a Multipart MIME, wrapped in an encrypted and signed file.

Files.com AS2 will automatically attempt to decrypt the file and verify its signature. If the decryption succeeds, you will be able to view the contents of the MDN in the AS2 Logs.

A correctly formatted MDN will look like this:

------7F351D7B2DF82DAA639F0F4BAF1126B2
Content-Type: multipart/report; report-type=disposition-notification; boundary="----=_Part_1_20231005223333321"


------=_Part_1_20231005223333321
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

The AS2 message has been received successfully

------=_Part_1_20231005223333321
Content-Type: message/disposition-notification
Content-Transfer-Encoding: 7bit

Reporting-UA: YOUR_AS2_PARTNER
Original-Recipient: rfc822; YOUR_AS2_PARTNER
Final-Recipient: rfc822; YOUR_AS2_PARTNER
Original-Message-ID: <YOUR_AS2_PARTNER-20231005223330@mysite.files.com>
Disposition: automatic-action/MDN-sent-automatically; processed
Received-Content-MIC: WoWTby7qm+yTTydEWhG9Um7llknPrWCTNiSUvnOOROM=, sha-256

------=_Part_1_20231005223333321--

------7F351D7B2DF82DAA639F0F4BAF1126B2
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIHBwYJKoZIhvcNAQcCoIIG+DCCBvQCAQExDzANBglghkgBZQMEAgEFADALBgkq
hkiG9w0BBwGgggPyMIID7jCCAtYCCQCfMq8S3SzAkTANBgkqhkiG9w0BAQsFADCB
uDELMAkGA1UEBhMCVVMxEzARBgNVBAgMCkNhbGlmb3JuaWExETAPBgNVBAcMCFZh
bGVuY2lhMRIwEAYDVQQKDAlGaWxlcy5jb20xEDAOBgNVBAsMB1Byb2R1Y3QxLjAs
BgNVBAMMJWNsYXVkaW9mb3VyLmFzMi5jbGF1ZGlvdGVzdC5maWxlcy5jb20xKzAp
BgkqhkiG9w0BCQEWHGNsYXVkaW8udGlubmlyZWxsb0BmaWxlcy5jb20wHhcNMjMw
NjAxMTg0NTU4WhcNMjQwNTMxMTg0NTU4WjCBuDELMAkGA1UEBhMCVVMxEzARBgNV
BAgMCkNhbGlmb3JuaWExETAPBgNVBAcMCFZhbGVuY2lhMRIwEAYDVQQKDAlGaWxl
cy5jb20xEDAOBgNVBAsMB1Byb2R1Y3QxLjAsBgNVBAMMJWNsYXVkaW9mb3VyLmFz
Mi5jbGF1ZGlvdGVzdC5maWxlcy5jb20xKzApBgkqhkiG9w0BCQEWHGNsYXVkaW8u
dGlubmlyZWxsb0BmaWxlcy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK
AoIBAQC7aBmHVHe5OcaFRPZytBlT4MeC0MW4+twsne+iiW4LZR6PkfNfwRYzVMCi
xDPyvfe6O7alGCXBd5jYgAI8LXTntHJlPDF3TKmQ/x7etQzFOFhaNYKD6r+0FP8l
25fHj59y6GUT9iR3W2JYFApmIle0pd540BTXvnD5mgv5FxWVJ5viB+5bAslXnH9c
Unyfcp0A+6vmmJpRK1KdiS4XTszs4J2DvgEEug3ALysEKay+zq0ysWZQB17EtNM5
/1ePR1qph6wPvyQQY5/o91r17T5gEP3QZj7Qg2O9aTwS1dbhb2JFbUJhEp/hcdbq
H9Qa1kMbQoiL5vVPFO5nWmVVwK8DAgMBAAEwDQYJKoZIhvcNAQELBQADggEBAFRH
fKW1TY5UY90+7ouf6DibX9RtBAfzOIRNrv54+ojBANaqscSMtBl08Wq+5HLrrPzg
EfqD8avf1C2eeHE3pmXACW5tVpT6S/arzx1CRP71sTIzBNhtBcWk6NxqvtwB7XLm
BL7rUMVA2oYxteHndDt6TLN7GVg85oSvz6hDIIb+bPkXf9zc9uXz8mozt4bIxuX6
F9TmcFtvy2LmZ3B8hJylYJK9zGJaT9xAed1vE6lHF0KfEpJSmBp5+nP3impcoD5M
7QCwiWLFjUNYMk1q29BdbUN5ZKbqrR3Rm6zHQgd7yqMu3iKsMWq21MiBXTT8Jq/F
rtiX+dULo0KcENpNQysxggLZMIIC1QIBATCBxjCBuDELMAkGA1UEBhMCVVMxEzAR
BgNVBAgMCkNhbGlmb3JuaWExETAPBgNVBAcMCFZhbGVuY2lhMRIwEAYDVQQKDAlG
aWxlcy5jb20xEDAOBgNVBAsMB1Byb2R1Y3QxLjAsBgNVBAMMJWNsYXVkaW9mb3Vy
LmFzMi5jbGF1ZGlvdGVzdC5maWxlcy5jb20xKzApBgkqhkiG9w0BCQEWHGNsYXVk
aW8udGlubmlyZWxsb0BmaWxlcy5jb20CCQCfMq8S3SzAkTANBglghkgBZQMEAgEF
AKCB5DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0y
MzEwMDUyMjMzMzNaMC8GCSqGSIb3DQEJBDEiBCArw1luHUS6Aagd2G2hU00/FuRp
PePJFvmMNcoQzbExDjB5BgkqhkiG9w0BCQ8xbDBqMAsGCWCGSAFlAwQBKjALBglg
hkgBZQMEARYwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDANBgkqhkiG
9w0BAQEFAASCAQARflZ/TDf8+NNvhqae8/BOyRImwwgXpqXEZ6O3OK6tqtcy8QsZ
IP7qzqjXqv0MJWaUCDLNK2KCw7O97GITBDckQCI0gGctJLlFBkegFIwsk+MTpuaV
5mUxG/pihxx9WFpuwyx3APZxasdKmnzOncWY2qgUpUj4IqoqkynU5OJD2U9R9qi+
ub3LkvreK27WRAn9KjsRl6hTlpoFMHM5+jmyE05o4c8oaTVfjwwBDOOBMIKL4JMY
ttncgV2mgq5TxROQuxyf649bbuV5YySJjjxfOHLzTyAOYT2x2VOGEZzd9Uzryniw
W38Tzmm9oflH6+XdjnO6JptjDYM/YGismxBB

------7F351D7B2DF82DAA639F0F4BAF1126B2--

Any returned processing messages from your trading partner's system should be contained within the first segment of the multipart MIME message.

In the above example, the returned message is:

The AS2 message has been received successfully

This returned message will vary from system to system but as long as it is placed within the above multipart MIME structure then you can treat it as a valid and trusted return receipt from your trading partner.

However, when an error occurs, some AS2 or EDI systems may output their error messages into the MDN.

Instead of being correctly formatted, the MDN will contain the "raw" error message, rather than the expected multipart MIME format.

This "raw" error message can look like any typically cryptic error message that gets written to a log file.

You should send this raw error message to your trading partner so that they can troubleshoot their side of the AS2 connection, or their EDI processing system, to find the cause of the error.

Incorrectly Signed MDN

When a returned MDN can be decrypted successfully but has been signed by an invalid Signing certificate then the AS2 logs will show a MDN indicates a processing failure message.

This effectively means "We received a valid MDN, saying that the file was delivered successfully, but it's signed by someone that we can't verify so we can't trust the MDN's validity."

We provide an option for you to specify the MDN validation level to be performed in order to consider the AS2 transmission to be a success. This option allows you to accept MDNs based on varying levels of validation. Try setting this option to a lower level of validation for the trading partner.

Check with your trading partner to verify that they are signing the MDN using the correct AS2 certificate. The MDN should be signed using the private certificate key that corresponds to the public certificate they provided to you to set up the AS2 partnership.

The returned MDN may include a signature that is encoded in either base64 or binary formats.

If you need to provide the incorrect signature details to your trading partner, it can be found within the MDN contents, usually as the last segment.

PEM Base64 Encoded Signature

A PEM base64 encoded signature looks like this:

------7F351D7B2DF82DAA639F0F4BAF1126B2
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIHBwYJKoZIhvcNAQcCoIIG+DCCBvQCAQExDzANBglghkgBZQMEAgEFADALBgkq
hkiG9w0BBwGgggPyMIID7jCCAtYCCQCfMq8S3SzAkTANBgkqhkiG9w0BAQsFADCB
uDELMAkGA1UEBhMCVVMxEzARBgNVBAgMCkNhbGlmb3JuaWExETAPBgNVBAcMCFZh
bGVuY2lhMRIwEAYDVQQKDAlGaWxlcy5jb20xEDAOBgNVBAsMB1Byb2R1Y3QxLjAs
BgNVBAMMJWNsYXVkaW9mb3VyLmFzMi5jbGF1ZGlvdGVzdC5maWxlcy5jb20xKzAp
BgkqhkiG9w0BCQEWHGNsYXVkaW8udGlubmlyZWxsb0BmaWxlcy5jb20wHhcNMjMw
NjAxMTg0NTU4WhcNMjQwNTMxMTg0NTU4WjCBuDELMAkGA1UEBhMCVVMxEzARBgNV
BAgMCkNhbGlmb3JuaWExETAPBgNVBAcMCFZhbGVuY2lhMRIwEAYDVQQKDAlGaWxl
cy5jb20xEDAOBgNVBAsMB1Byb2R1Y3QxLjAsBgNVBAMMJWNsYXVkaW9mb3VyLmFz
Mi5jbGF1ZGlvdGVzdC5maWxlcy5jb20xKzApBgkqhkiG9w0BCQEWHGNsYXVkaW8u
dGlubmlyZWxsb0BmaWxlcy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK
AoIBAQC7aBmHVHe5OcaFRPZytBlT4MeC0MW4+twsne+iiW4LZR6PkfNfwRYzVMCi
xDPyvfe6O7alGCXBd5jYgAI8LXTntHJlPDF3TKmQ/x7etQzFOFhaNYKD6r+0FP8l
25fHj59y6GUT9iR3W2JYFApmIle0pd540BTXvnD5mgv5FxWVJ5viB+5bAslXnH9c
Unyfcp0A+6vmmJpRK1KdiS4XTszs4J2DvgEEug3ALysEKay+zq0ysWZQB17EtNM5
/1ePR1qph6wPvyQQY5/o91r17T5gEP3QZj7Qg2O9aTwS1dbhb2JFbUJhEp/hcdbq
H9Qa1kMbQoiL5vVPFO5nWmVVwK8DAgMBAAEwDQYJKoZIhvcNAQELBQADggEBAFRH
fKW1TY5UY90+7ouf6DibX9RtBAfzOIRNrv54+ojBANaqscSMtBl08Wq+5HLrrPzg
EfqD8avf1C2eeHE3pmXACW5tVpT6S/arzx1CRP71sTIzBNhtBcWk6NxqvtwB7XLm
BL7rUMVA2oYxteHndDt6TLN7GVg85oSvz6hDIIb+bPkXf9zc9uXz8mozt4bIxuX6
F9TmcFtvy2LmZ3B8hJylYJK9zGJaT9xAed1vE6lHF0KfEpJSmBp5+nP3impcoD5M
7QCwiWLFjUNYMk1q29BdbUN5ZKbqrR3Rm6zHQgd7yqMu3iKsMWq21MiBXTT8Jq/F
rtiX+dULo0KcENpNQysxggLZMIIC1QIBATCBxjCBuDELMAkGA1UEBhMCVVMxEzAR
BgNVBAgMCkNhbGlmb3JuaWExETAPBgNVBAcMCFZhbGVuY2lhMRIwEAYDVQQKDAlG
aWxlcy5jb20xEDAOBgNVBAsMB1Byb2R1Y3QxLjAsBgNVBAMMJWNsYXVkaW9mb3Vy
LmFzMi5jbGF1ZGlvdGVzdC5maWxlcy5jb20xKzApBgkqhkiG9w0BCQEWHGNsYXVk
aW8udGlubmlyZWxsb0BmaWxlcy5jb20CCQCfMq8S3SzAkTANBglghkgBZQMEAgEF
AKCB5DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0y
MzEwMDUyMjMzMzNaMC8GCSqGSIb3DQEJBDEiBCArw1luHUS6Aagd2G2hU00/FuRp
PePJFvmMNcoQzbExDjB5BgkqhkiG9w0BCQ8xbDBqMAsGCWCGSAFlAwQBKjALBglg
hkgBZQMEARYwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDANBgkqhkiG
9w0BAQEFAASCAQARflZ/TDf8+NNvhqae8/BOyRImwwgXpqXEZ6O3OK6tqtcy8QsZ
IP7qzqjXqv0MJWaUCDLNK2KCw7O97GITBDckQCI0gGctJLlFBkegFIwsk+MTpuaV
5mUxG/pihxx9WFpuwyx3APZxasdKmnzOncWY2qgUpUj4IqoqkynU5OJD2U9R9qi+
ub3LkvreK27WRAn9KjsRl6hTlpoFMHM5+jmyE05o4c8oaTVfjwwBDOOBMIKL4JMY
ttncgV2mgq5TxROQuxyf649bbuV5YySJjjxfOHLzTyAOYT2x2VOGEZzd9Uzryniw
W38Tzmm9oflH6+XdjnO6JptjDYM/YGismxBB

------7F351D7B2DF82DAA639F0F4BAF1126B2--

You can also decode the MDN signature using the openssl command line tool.

Save the above MDN segment to a file, then run this command:

openssl asn1parse -i -in /path/to/signature_file.txt

The output will show the details of the certificate that was used to sign the MDN, which you can provide to your trading partner to help them identify and correct this issue.

If the above command fails with an error that says "Error reading PEM file" then the signature might have been signed using an old pre-PEM Base64 format instead. Try this command to decode the signature:

openssl asn1parse -i -inform B64 -in /path/to/signature_file.txt

Binary Signature

Binary format signatures cannot be viewed properly in text editors, but look somewhat like this:

------7F351D7B2DF82DAA639F0F4BAF1126B2
Content-Type: application/pkcs7-signature; name=smime.p7s; smime-type=signed-data
Content-Transfer-Encoding: binary
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

0€	*†H†÷
 €0€10
	`†He�0€	*†H†÷
��1‚=0‚90¦0™100.	*†H†÷
	!10U
192.168.2.1000U
ESM REDACTED
REDACTED–ä±~´F0
	`†He� i0	*†H†÷
	1	*†H†÷
0	*†H†÷
	1
REDACTED/	*†H†÷
	1" ¤¦rm—\Ó:°qÇ
žEXµã~èÅ1ᶥ2Öö0
	*†H†÷
�‚�#Xæhý7SzŽîèþñï`_{nŠmKÀnÉ2´gk¼K¨¹ÍmE¡”ÍæµT-”oN%ô€¸üiò[vÃú*Ð5£Ps¼'<LçTZ¡Czþ2ã?Ÿy¤ß~YÜQÕ5E7þv»/ÄÈE› Å–Iã%l•“ZCÉîx[|ûö=Õà!»»*§ôԏ7¤’a–Ùqïn?Êùo_dn×e8Í»¥ó­ã›ò«wr>ÒÌ<ܪÌk €ˆÿO¸Èn=U¯AûKªJã7F{Tn
…oÏ—™‰
EaÖ}P^‘O›ºÑO§h…œ§~ÞêµyD�ôž‹,½žðTä/1*������
------7F351D7B2DF82DAA639F0F4BAF1126B2--

You can also decode the MDN signature using the openssl command line tool.

Using a binary safe editor, save the above MDN segment to a file. Only save the binary data, starting after the blank line, and do not include any of the header or footer tags. Then run this command on the binary signature file:

openssl asn1parse -i -in /path/to/signature_file.bin --inform DER

The output will show the details of the certificate that was used to sign the MDN, which you can provide to your trading partner to help them identify and correct this issue.

Certificate Purpose

The signing of AS2 messages and MDN receipts uses X.509 Certificates. The structure of these certificates includes fields that specify the purpose that the certificate can be used for.

AS2 allows the use of various types of these certificates including, for example, self-signed certificates. Each of your trading partners will have their own certificate standards and so partner certificates will vary in their configuration.

We provide an option for you to specify the MDN validation level, which provides different levels of validation against these different types of signing certificate.

You can use the following command to display a certificate's purpose:

openssl x509 -in /path/to/as2_partner.pem -noout -purpose

Transmissions from My Trading Partner Have Stopped Working

If a previously working inbound transmission stops working then the cause could be:

ISSUERESOLUTION STEPS
The trading partner has changed something on their side.

Contact the trading partner and find out what they changed.

If they renewed, updated, or changed their AS2 certificates then ask them to send you their new public certificate. Re-import the new public certificate into the trading partner configuration.

You renewed, updated, or changed your AS2 certificates.

Make sure that you sent your trading partner your new public certificate.

Contact the trading partner and verify that they are using your new public certificate for AS2 transmissions.

Transmissions to My Trading Partner Have Stopped Working

If a previously working outbound transmission stops working then the cause could be:

ISSUEResolution Steps
The SSL certificate on the trading partner’s AS2 endpoint URL has expired or is no longer valid.

Contact the trading partner and ask them to renew the SSL certificate on their AS2 endpoint URL. Use an online SSL Certificate checker, such as SSL Shopper, to check the trading partner’s AS2 URL and make sure that the SSL certificate being used is valid.

If an invalid, unchained, or self-signed SSL certificate is being used by the trading partner, you can configure Files.com to allow this less secure connection by editing the trading partner entry, and change the Server certificate option to "Allow self-signed, unchained, expired, or non-matching TLS/SSL certificate".

The trading partner has changed something on their side.

Contact the trading partner and find out what they changed.

If they renewed, updated, or changed their AS2 certificates then ask them to send you their new public certificate. Re-import the new public certificate into the trading partner configuration.

If they changed their AS2 endpoint URL then update the trading partner configuration with the new URL.

You renewed, updated, or changed your AS2 certificates.

Make sure that you sent your trading partner your new public certificate.

Contact the trading partner and verify that they are using your new public certificate for AS2 transmissions.

File size is too big.Outgoing messages are limited to 25MB in size. Files greater than this size will not be transmitted.

Inbound Files Are Overwritten

If a file with a duplicate name is received then your site's Overwrite Behavior setting will determine whether the file is overwritten or not.

Verify that the Overwrite Behavior setting hasn't been changed. You can view the Settings Changes log to see when the setting was changed and by whom.

Get Instant Access to Files.com

The button below will take you to our Free Trial signup page. Click on the white "Start My Free Trial" button, then fill out the short form on the next page. Your account will be activated instantly. You can dive in and start yourself or let us help. The choice is yours.

Start My Free Trial

©2024 Files.com. All right reserved

FILES.COM

  • Start My Free Trial
  • Pricing
  • Docs
  • API and SDKs
  • Contact

CONTACT & SUPPORT

support@files.com

(800) 286-8372

Monday–Friday

9am–8pm Eastern