cancel
Showing results for 
Search instead for 
Did you mean: 

Error while refreshing the XI runtime cache ?

former_member270261
Participant
0 Kudos

Hi Experts,

Today we are facing below error and bcoz of all messages are strucked in smq2.

================================================

Integration Engine: General Error:<SAP:AdditionalText>No RFC authorization for user R3PIUSER0.</SAP:AdditionalText>

  <SAP:Stack>Error while refreshing the XI runtime cache</SAP:Stack>

=============================================================

can any one please tell me if you're facing similer probelm and how to overcome this issue?

Thanks

Narendra

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Any way, if you add the following roles to the user used, you should be able to execute the cache refresh, but it's recomended to use PIDIRUSER

  • 1.     SAP_SLD_CONFIGURATOR
  • 2.     SAP_XI_ID_SERV_USER
  • 3.     SAP_XI_ID_SERV_USER_MAIN
  • 4.     SAP_BC_WEBSERVICE_PI_CFG_SRV

Regards.

former_member270261
Participant
0 Kudos


Hi Can,

can i ask basis to provide the above roles to R3PIUSER0,then it will be work as PIDIRUSER.

can  apporach this way,is it okay.

Thanks

Narendra

Former Member
0 Kudos

Yes, I guess that it's the same, PIDIRUSER has the roles but you can add them to any user.

Regards.

Former Member
0 Kudos

Hi Narendra,

You can check once from where this user R3PIUSER0 is getting generated. I feel this user might be getting generated dynamically via some JMS property. My suggestion will be to check once the module tab of JMS channel (if used).

OR

You can also check if this user is locked just as Roberto has suggested.

Regards,

Souvik

Former Member
0 Kudos

Hi mates,

      I guess that you should use PIDIRUSER, not R3PIUSER0 in

http://sys:port/CPACache/refresh?mode=full

Regards.

giridhar_vegi
Participant
0 Kudos

Hi Narendran,

mostly you can use the PIDIRUSER to refresh as can vill said.

Thanks

Girihdar

rcsegovia
Active Participant
0 Kudos

Hi Narendra,

Check user is not locked if It was working before. If not looks like authoritation problems.

regards,

Roberto.