Quantcast
Channel: SCN : All Content - Process Integration (PI) & SOA Middleware
Viewing all articles
Browse latest Browse all 7030

User PIXXXXX (client XXX) has no ICF authorization XICACHE for executing /sap/xi/cache

$
0
0

Background:

We recently completed SP Upgrade to our SAP PI7.3 system. Though there were no known issues during SP Upgrade/Post Upgrade Steps,

on activation of Objects in ID resulted in either Cache Update Failure or does not start.

 

Blog1.jpg

 

blog4.JPG

Additionally, more details about this issue can be obtained from Application Server ST11 Trace.

 

From ST11 trace: User PIXXXXX (client XXX) has no ICF authorization XICACHE for executing /sap/xi/cache

 

Reason:

 

Its obvious now it is due to missing authorization issue.

 

Blog3.jpg

 

Solution:

 

          • Make sure that Post Installation Steps are followed after SP Upgrade.

          • Ensure that the user has all the following Roles:

                          1. SAP_BC_WEBSERVICE_PI_CFG_SRV

                          2 SAP_SLD_CONFIGURATOR

                          3. SAP_XI_ID_SERV_USER

                          4. SAP_XI_ID_SERV_USER_MAIN

                          5. SAP_XI_ADMINISTRATOR_J2EE

          • Even after following Post Installation Steps judiciously, if the issue still persists,

                         1. On the Integration Server, execute transaction SUPC for SAP_XI_ID_SERV_USER(in your client) to regenerate possibly changed roles.

                         2. Once done, complete the USER COMPARISON under PFCG.

                             Hint: Make sure that Authorizations Tab and User Tab are in Green.

 

This should resolve the issue. Happy if this blog have helped you.

 

Suggested Links: http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/07/24/cpa-cache-refresh-403-forbidden--no-authorization-with-pidiruser-or-pidirsid#comment-383298

Suggested Notes: 1600539


Viewing all articles
Browse latest Browse all 7030

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>