cancel
Showing results for 
Search instead for 
Did you mean: 

RFC Dest from ECC to PI 7.4 is failing with 403 forbidden error

former_member193393
Participant
0 Kudos

Dear All,

Though this error has been posted several times in the community, I couldn't find a solution for mine and hence repeating the same discussion.

We are facing issue with the RFC Dest from ECC to PI 7.4 as it is failing with 403 forbidden error.

Our current PI 7.11 system was upgraded to PI 7.4 SP06. Post up-gradation activities were done and the system was up & running fine. Created a type G Rfc dest: PI_AAE in ECC system for connecting to the upgraded PI 7.4 system.

But the above PI_AAE rfc destination is failing with 403 forbidden error. The Target Host, Service No & Path Prefix were all mentioned correctly.

The user: PIAPPLUSER used in the above rfc dest has the required roles i.e., SAP_BC_WEBSERVICE_PI_CFG_SRV, SAP_SLD_CONFIGURATOR, SAP_XI_AF_SERV_USER_MAIN, SAP_XI_APPL_SERV_USER. Also provided SAP_ALL & SAP_NEW profiles to the user: PIAPPLUSER and tried but still facing the same 403 forbidden error.

Post up-gradation of the system, roles were adjusted as instructed in the upgrade guide using su25 i.e., 2a, 2b & 2c were executed successfully.


Can someone suggest how to get rid of 403 forbidden error..?



Br,

Saiganesh.

Accepted Solutions (1)

Accepted Solutions (1)

former_member193393
Participant
0 Kudos

Dear All,

Issue got solved. Issue is with the DNS. PI system HTTP url was added in the DNS and then got rid of 403 forbidden error. Now the RFC from ECC to PI 7.4 was working fine and hence closing the thread.

Br,

Saiganesh.

Answers (1)

Answers (1)

former_member182455
Active Contributor
0 Kudos

Hi,

pls go through the below SDN artical.

http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/07/24/cpa-cache-refresh-403-forbidden--...

Kindly check, If you have correct Target system details of Target Host,path and service number, and then you can check the user you have for that  RFC Destination.

Check if that user is locked if any in SU01 tr.

Regards

Srinivas

former_member193393
Participant
0 Kudos

Hello Srinu,

Already referred mentioned blog but that didn't help. PIAPPLUSER is not locked. Chked that already while providing SAP_ALL & SAP_NEW profiles to the user.

Br,

Saiganesh.

former_member182455
Active Contributor
0 Kudos

Hi,

kindly check the below steps.

 

 

1 ) Path sap/xi/engine not active

 

2 ) Activate the service engine in transaction SICF

as described

pls go through the below troubleshoot ing guide link.

https://websmp203.sap-ag.de/~sapidb/011000358700005909032005E/PI70-701_Trouble.pdf

Regards

Srinivas

former_member193393
Participant
0 Kudos

Hello Srinu,

Already went thru PI 7.3 Troubleshooting Guide & engine service under sicf is already active and a test service returns below message:

<SAP:Category>XIProtocol</SAP:Category>

<SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>

<SAP:P1/>

<SAP:P2/>

<SAP:P3/>

<SAP:P4/>

<SAP:AdditionalText/>

<SAP:Stack>Empty HTTP query received; message processing not possible </SAP:Stack>

Br,

Saiganesh.