cancel
Showing results for 
Search instead for 
Did you mean: 

HTTP_RESP_STATUS_CODE_NOT_OK -403 Forbidden

Former Member
0 Kudos

Hi,

In my RFC-Jbdc scenario. I got the following error:

<b><SAP:Stack>HTTP response contains status code 403 with the description Forbidden Error when sending by HTTP (error code: 403, error text: Forbidden)</SAP:Stack>

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>

<SAP:P1>403</SAP:P1>

<SAP:P2>Forbidden</SAP:P2></b>

I tried to look into the previous threads, not of much use.

403 error means, not activated, so I looked into my SICF/defaulthost/sap/xi/engine, maintained XISUPER uID and Pwd.

That didnt help anything.

So, any SAP Notes and help?

Thanks,

Raj.

Accepted Solutions (1)

Accepted Solutions (1)

sam_raju
Contributor
0 Kudos

Hi Raj,

It looks like you have authorization problems with your XISUPER. In the visual administrator and in ABAP SU01, make your XISUPER has all the necessary(SAP_SLD* and SAP_XI*) roles assigned to it. If not, try to assign these and see if this can be of any help.

Rgds,

Sam Raju

Former Member
0 Kudos

Hi Sam and Abhy,

I checked in SU01, these are the roles that I missed.

SAP_XI_APPL_SERV_USER.

SAP_XI_DISPLAY_USER_J2EE.

SAP_XI_IR_SERV_USER.

SAP_XI_IS_SERV_USER.

Abhy, I havent created any http destinations in R/3. I have created one RFC DEST of type TCP/IP. Thats all I did. Do I still need to create an http destination?.

Thanks,

Raj.

sam_raju
Contributor
0 Kudos

Hi Raj,

Also check the roles on J2EE for the user XISUPER using Visual Administrator.

Rgds,

Sam Raju

Former Member
0 Kudos

Hi Raj -

In additon to Sam's suggestions, check on the XIAFUSER. I assume that you're seeing this error in SXMB_MONI and the error is being triggered on your call to the adapter. Check that XIAFUSER is not locked as well.

Also, in a browser, check the following link:

http://<xiserver>:<j2ee-http-port>/MessagingSystem/receive/AFW/XI

to see if you get the same error.

Regards,

Jin

Former Member
0 Kudos

Jin,

XIAFUSER is not locked. But when I try to access that URL, I am getting same error '403 forbidden'.

Thanks for the help.

Best Regards,

Raj.

Former Member
0 Kudos

Hi Raj -

Using Visual Admin, make sure the adapter related services (e.g. SAP XI*) are up, especially, SAP XI AF Messaging. Given that it's a 403, and not 503, it should be.

I know that these were discussed earlier, but confirm that the following users have the following roles:

XIISUSER SAP_XI_IS_SERV_USER_MAIN

XIAFUSER SAP_XI_AF_SERV_USER_MAIN

and that their profiles are properly generated. As Sam mentioned earlier, the 403 indicates an authorization related problem.

Regards,

Jin

Former Member
0 Kudos

Hi Jin,

I checked both XIISUSER AND XIAFUSER has both the roles u mentioned and I could see the Green Light. I will now need to add the roles that I missed, and check in Visual Admin.

Thanks-a-lot.

Best Regards,

Raj.

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Raj,

Just check the mentioned possibilities for your error one by one:

1.Did you maintain Client, userid, password, and lang information in SICF transaction -> sap/xi/engine? Double click on service and check whether you have entered correct information.

2.Then you might check the roles of the XIISUSER in SU01. In some case there are some double roles, i.e., two times the role SAP_XI_IS_SERV_USER assigned. One might have the date of the last update, the other one might have apparently the older version. Delete the older roles manually and the error should disappear.

3.to send messages to xi you need a service id / pwd which is specific to your landscape usually its xiappluser. Contact your basis group for password.

4.

- Activated all services on the r3 system.

- Create HTTP connection to XI from r3

sm59-> http connetons to r3

- let us say you have created a HTTP connection in the integrationserver_XI, make sure in its settings the prefix path is set to /sap/xi/engine?type=entry. Also check its log on credentials, you can use xiappluser.

- IN Integration builder, receiver communication channel make sure you have entered proper

host service number

path = /sap/xi/enigne?type = receiver.

5. can you also try the following;

Visual Admin -> start the service,

"com.sap.aii.af.ms.app".

Please go through the followings links also :

http://help.sap.com/saphelp_nw04/helpdata/en/82/f4993c03e0cd37e10000000a11405a/content.htm

/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions

http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm

I hope the info provided help you solve your error.

Regards,

abhy

NOTE: reward the helpful.