User locked but SU01 showing it's not locked

[Former Member]

One of our user can not login to SAP - getting user lock message but in SU01 or SUIM we couldn't see him locked. It's a normal dialog user. We are not using CUA. What could be the issue ? How to unlock this user ?

Please suggest.

[Former Member]

sapman,

What does it show for the uflag field in table usr02. This is the table/field that shows the lock status.

Cheers,

Ben

[Former Member]

UFLAG filed shows 0 not 128 or 64.

Please how can we allow this user to login

[Former Member]

Also be sure the password has not been inactivated.

If that is not the case answer the following:

If the user is copied into another user is it able to logon? Also what is the exact error message?

Cheers,

Ben

[Former Member]

Lock and Unlock the user, and ask the user to logoff and login again. When the user is logged off check for any open session running with this user ID

[Former Member]

I'll try to find answers to that ASAP.

But how to check whether password inactivated or not ?

TIA

[Former Member]

Yes benjamin. I checked that login/password_expiration_time is over for this user. BCDA1 field date is over. Now whether his password can be now reset using simple SU01 ? or delete/create this id is required. In some notes I read that "expired password can not be reset" - not sure whether that is true with this prof parameter or not ?

Our security team says they tried to unlock & also reset password but user still can't login. Thats why I'm asking whether delete/create of this id required to enable him login ?

[Former Member]

I would reset the user's password and ask them to try to relogon.

You can find if a password is deactivated in SU01 in the "logon data" tab.

[Former Member]

Hi

I am not sure what version you are runnig gbut The profile paramters

login/password_max_new_valid and login/password_max_reset_valid should not be used. This causes issues with users. I had the same issue where by I had to delete and recreate,I then took these parms out and never had the issue agaain

[Former Member]

Ensure that the users account is with in the "validity" period. eg Vaild from / to period in SU01.

[WolfgangJanzen]

@Moods: yes - have a kind look on <a href="https://service.sap.com/sap/support/notes/450452">SAP Note 450452</a>: refrain from using login/password_max_new_valid and use login/password_max_new_valid with care.

[WolfgangJanzen]

Advice: start transaction SE37 and test-drive function module SUSR_USER_PASSWORD_STATUS_GET.

Worse-comes-worse: use the tracing approach described in <a href="https://service.sap.com/sap/support/notes/495911">SAP Note 495911</a> to analyse the problem (which seems to be reproducable).

Cheers, Wolfgang