cancel
Showing results for 
Search instead for 
Did you mean: 

SEEBURGER AS2: 403 Forbidden #

Former Member
0 Kudos

Hi ALL

We are encountering the following error for SEEBURGER AS2: 403 Forbidden # .... while the vendor is trying to send a file thru AS2 adapter.

Please, let us know if you a have encountered this problem and have a solution to fix it.....

Delivery of the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 403 Forbidden # , SEEBURGER AS2: 403 Forbidden # : javax.resource.ResourceException:

We did check on the following ( all of the below have been validated in our scenario):

a) You or your partner has entered an incorrect AS2 ID for

b) A valid sender agreement is missing. c) There are more then one AS2 sender agreements with the

d) The corresponding inbound channel is set to inactive.

Your help is greatly appreciated!!

Thank you,

Patrick

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Patrick,

Reason might be any one of the following.Please go through into them once again.

1. You or your partner has entered an incorrect AS2 ID

- Please check the AS2ID's very clearly. The ID's are case sensitive.Make sure you and your partner has entered exactly the same AS2ID in the configuration.

2. A valid sender agreement is missing.

You need to select Virtual receiver in the sender agreement and provide your receiver party and service name as well. This is very important for identifying the AS2 ID's.

3. There are more then one AS2 sender agreements.

Make sure that you created only one sender agreement for your sender and receiver party. Your business service may change but make sure you have created only one sender agreement for your sender and receiver party.

4. The corresponding inbound channel is set to inactive.

Make sure your channel is active.

lemme know once you check.

Thanks

Deepthi.

Answers (4)

Answers (4)

Former Member
0 Kudos

Another reason for a 403 is that the inbound message subject does not match any subject configured in the sender channels/agreements !

prateek
Active Contributor
0 Kudos

Another possible reason could be incorrect adapter module configuration in channel. Also make sure that the used certificates in agreements are proper.

Regards,

Prateek

sunil_singh13
Active Contributor
0 Kudos

Hi Patrick,

Generally 403 error comes when the corresponding service is not available(Deactive),

I am not sure about the services required for your requirment.

You can go to SICF transaction if required service is ACTIVE. It will solve your problem.

Thanks

Sunil Singh

markangelo_dihiansan
Active Contributor
0 Kudos

Hi,

Have you checked the firewall if the ports have been opened?

Regards,

Former Member
0 Kudos

Hi Mark,

This is not a port problem. If the port is not opened then the error will be different like 401 authentication error.

Thanks

Deepthi.