cancel
Showing results for 
Search instead for 
Did you mean: 

PIRWBUSER getting locked repeatedly

Former Member
0 Kudos

Hi Experts,

We are facing a very peculiar problem . The service user PIRWBUSER is getting locked again and again . We have thoroughly checked with all the places where the service user is used and all those places are having the right entry . Still the user is getting locked . Kindly let us know where exactly is this user being used which has gone unoticed or there is some other problem .

We have checked with all the possible notes related to this problem and checked with the PIRWBUSER in sm59, PMI store of J2EE admin and all such related places where actually this service user is in use .

Please help .

Regards

Nishant Kumar Singh

Accepted Solutions (0)

Answers (5)

Answers (5)

0 Kudos

Hi!

Check the notes below according to the version you have to mantain the

user passwords accordingly:

999962 - PI 7.10: Change passwords of PI service users

936093 - XI 7.0: Changing the passwords of XI service users

721548 - XI 3.0: Changing the passwords of the XI service users

Regards,

Caio

madhusudana_reddy2
Contributor
0 Kudos

Hi,

The problem problem may be due to some PI users that were locked on the J2EE part of XI, and therefore they could not onnect to the SLD. Unlock them through VA 's, Security Provider service.

thanks,

madhu

Former Member
0 Kudos

Hi,

If you used the PIRWBUSER in several non-standard places like component monitoring rfc's, the user may get locked while components try to update their monitoring status. Check where-used lists for the user.

I recommend you to also check your RFC connections to see if you have used PIRWBUSER in any of them. Also, re-enter the password in exchange profile for this user and also in the PMISTORE in Visual Admin.

Note 999962 - PI 7.10 Change passwords of PI service users

Regards,

Shitij

Former Member
0 Kudos

Hi Shitij,

I am sure we have checked the places where PIRWBUSER is used and the following service user is having the password properly set both at the java as well as the abap stack level.

We have never changed the password for the service user after the installation.

Regards

Nishant Kumar Singh

Former Member
0 Kudos

Hi Shitij,

Could you please elaborate how to see all the where used lists for the user PIRWBUSER ???

Regards

Nishant Kumar Singh

former_member181962
Active Contributor
0 Kudos

Check these discussions if you have no done already:

Regards,

Ravi

former_member185881
Active Participant
0 Kudos

Hi Nishant

If it is getting locked you can do the unlock thing right in SU01.

Regards

Dheeraj Kumar <removed>

Edited by: Prateek Raj Srivastava on May 11, 2010 4:23 PM

Former Member
0 Kudos

Hi Dheeru,

I have already done that and the moment it is unlocked , again after five minutes it goes to locked state ....

Regards

Nishant

former_member185881
Active Participant
0 Kudos

Hi Funnu

This is a service user type right na.

Are you using any RFC??

In RFC you have given password and the password is changed for this user in SU01 then this problem comes. (Password mismatch condition). Due to this RFC will try to login with the old password and it will fail and RWBUSER will be locked.

Hope it will help.

Regards

Dheeraj Kumar

prateek
Active Contributor
0 Kudos

Have you changed the password of this user recently? If yes, have you changed it according to SAP Note 936093/999962?

Regards,

Prateek

Former Member
0 Kudos

Hi Prateek,

I have not changed the password for the user.

Regards

Nishant

former_member181962
Active Contributor
0 Kudos

Do you have another PI system pointing to the same SLD which is using the same user id?

Regards,

Ravi

Former Member
0 Kudos

Hi Ravi,

We have three different environments for XI i.e. xidev , xiqa and xiprod and all the systems have got seperate SLD instances , so each XI server has its own sld instance .

Regards

Nishant Kumar Singh

Former Member
0 Kudos

Hi Ravi,

The symtoms in our case is quite similar to the one mentioned in the following link :-

which u have mentoned but the difference is we are not having any PI instance pointing to the SLD of the current system into picture ...

Regards

Nishant Kumar Singh