Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Users gets locked by incorrect logon

Former Member
0 Kudos

Hi All,

One user ID gets locked frequently by incorrect password logon.How Do i find from where somebody is trying to connect with wrong passowrd? If this is happening by any RFC how do I find from which system it is coming ?

Please advice.

Thanks,

Suman

1 ACCEPTED SOLUTION

Bernhard_SAP
Employee
Employee
0 Kudos

Hi Suman,

first step is to identify, if the logon attempts are coming regularly (for instance every day, hour,... at the same time) or after a special event.

If you know, when you expect the next attempt, you need to trace the login. SM20 is not really necessary, but makes it easier to find the workprocess, through which the attempt has been processed.

To trace the login attempt:

[SAP Note 495911|https://service.sap.com/sap/support/notes/495911]

To identify, from which host/system the attempt has been started:

[SAP Note 171805|https://service.sap.com/sap/support/notes/171805]

Good luck!

b.rgds, Bernhard

5 REPLIES 5

Former Member
0 Kudos

Hi Suman,

You might want to look at another approach to resolve this, however this is one option I take to do a quick lookup on RFC's.

If you do not have too many systems, then an easy step you could take is to export table RFCDES and check field U="desired_name" in the field.

"U= " mentions the user name defined in an RFC. By this you can ensure that the user that is getting locked is not defined in an RFC by mistake.

Hope this helps

Abhishek

Former Member
0 Kudos

You will get RFC login information for a user if you have the security audit log activated (SM20). It will also tell when a login is failed due to incorrect password

0 Kudos

Hi Alex,

I have to go through so much pain for system audit not being enabled . Cant do anything too about it.

0 Kudos

Try trx ST03N and imediately switch on Sm19

Bernhard_SAP
Employee
Employee
0 Kudos

Hi Suman,

first step is to identify, if the logon attempts are coming regularly (for instance every day, hour,... at the same time) or after a special event.

If you know, when you expect the next attempt, you need to trace the login. SM20 is not really necessary, but makes it easier to find the workprocess, through which the attempt has been processed.

To trace the login attempt:

[SAP Note 495911|https://service.sap.com/sap/support/notes/495911]

To identify, from which host/system the attempt has been started:

[SAP Note 171805|https://service.sap.com/sap/support/notes/171805]

Good luck!

b.rgds, Bernhard