RFC users locked after system copy in production system

[Former Member]

Hi,

BW_User,MDBTC(RFC users) system users were locked in our BI Production system at the same time system copy activity was running in the Quality system(production to quality) so as per our colleagues concern after system copy they started Quality system with out changing background work-process 0 so some jobs were triggered which were copied from production system.

Is there any cause to lock RFC users in production system for system copy? If there is any other reason where we can check logs

Thanks

Jalandhar Reddy

[Sriram2009]

Hi

I don't think it because of QA refresh. When you are defining rfc after qa refresh it may be problem in the manual entered user id and password in QA system

Regards

s

[Sriram2009]

Hi

If your getting error message "SM21 and found out user locked due to incorrect logins" its 100% in your SM59 RFC defined password was wrong. (its any user id)

Regards

S.

[Former Member]

Hi,

Users were locked only one time 2 days back and we haven't changed any RFC user passwords and now these user are working fine after unlocking.Perhaps users locked due to system copy.

Thanks

Jaandhar

[Sriram2009]

Hi reddy

you can check the log in T code SM21. if the password are not correct it may cause the issue

Regards

S

[Former Member]

Hi.

We have checked in SM21 and found out user locked due to incorrect logins but it is a RFC user(not dialog) no one will try to log-in with directly and we checked SM20,STAD and ST22 logs

We are not able to find our how it was locked

Thanks

[Former Member]

Hi,

Can you please check this SAP Note ...

Note 498889 - Logon locks with background jobs and internal RFCs

Regards

Bhuban

RKFL

[Former Member]

Hi,

As Per SAP Note 498889 Background and RFC password mechanism and corrections are implemented after 6.20 release.Present we are in 701 release.

We are can't find out the root cause of issue.

Thanks

Jalandhar Reddy

[Former Member]

Hi,

Well maybe i am wrong to analyze your problem .

Anyway I faced this issue to in our system before and we found that one background job was running in a system that has basically prompting an RFC connection to another system. In the t.code SM59 and there was wrong password was put in.We just reset the password and it was worked fine.

You can try for this..

Regards

Bhuban

RKFL