cancel
Showing results for 
Search instead for 
Did you mean: 

J2EE Admin is locked by SAPJSF every hour

Former Member
0 Kudos

Hello,

i have changed the pass of J2EE_ADMIN in SU01.

The UME of my J2EE is ABAP. I have changed the pass in the secure store in configtool, too. (Note 870445)

But every hour the J2EE_ADMIN is locked by localhost request with wrong password.

p51a004 is the localhost.

The System is a Solution Manager 4.0.

Audit Log


|Date      |Time    |User Name |Terminal    |TCode          |Program      |Security Audit Log message text                                                   |
--------------------------------------------------------------------------------------------------------------------------------------------------------------
|21.10.2008|08:51:32|SAPJSF    |p51a004     |               |SAPMSSY1     |Password check failed for user J2EE_ADMIN in client 100                           |
|21.10.2008|08:51:32|SAPJSF    |p51a004     |               |SAPMSSY1     |Logon Failed (Reason = 1, Type = U)                                               |
|21.10.2008|08:51:32|SAPJSF    |p51a004     |               |SAPMSSY1     |Password check failed for user J2EE_ADMIN in client 100                           |
|21.10.2008|08:51:32|SAPJSF    |p51a004     |               |SAPMSSY1     |Logon Failed (Reason = 1, Type = U)                                               |
|21.10.2008|08:51:32|SAPJSF    |p51a004     |               |SAPMSSY1     |Password check failed for user J2EE_ADMIN in client 100                           |
|21.10.2008|08:51:32|SAPJSF    |p51a004     |               |SAPMSSY1     |Logon Failed (Reason = 1, Type = U)                                               |
|21.10.2008|08:51:33|SAPJSF    |p51a004     |               |SAPMSSY1     |Password check failed for user J2EE_ADMIN in client 100                           |
|21.10.2008|08:51:33|SAPJSF    |p51a004     |               |             |Logon Failed (Reason = 1, Type = U)                                               |
|21.10.2008|08:51:33|SAPJSF    |p51a004     |               |SAPMSSY1     |Password check failed for user J2EE_ADMIN in client 100                           |
|21.10.2008|08:51:33|SAPJSF    |p51a004     |               |SAPMSSY1     |User J2EE_ADMIN Locked in Client 100 After Erroneous Password Checks              |
|21.10.2008|08:51:33|SAPJSF    |p51a004     |               |SAPMSSY1     |Logon Failed (Reason = 1, Type = U)                                               |
|21.10.2008|08:51:33|SAPJSF    |p51a004     |               |SAPMSSY1     |Logon Failed (Reason = 53, Type = U)                                              |
|21.10.2008|08:51:33|SAPJSF    |p51a004     |               |SAPMSSY1     |Logon Failed (Reason = 53, Type = U)                                              |
|21.10.2008|08:51:33|SAPJSF    |p51a004     |               |SAPMSSY1     |Logon Failed (Reason = 53, Type = U)                                              |

SLD Data Suplier is using the SLDDSUSER.

JCo Connections all using DDIC.

there are other places where I must change password or the J2EE_ADMIN is used?!?

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

solved!

An incomplete config of BI-Java configuration template of a BW system in our landscape was the problem.

After completed the template of the BI-Java with the correct passwords we have no more lock.

Former Member
0 Kudos

the change of the parameter rfc/signon_error_log to 2 has no effect. no dump will be written and in the dev_w* files are only the follow entry...


M Thu Oct 23 09:51:02 2008
M  ***LOG US1=> Login, Wrong Password (J2EE_ADMIN ) [sign.c       4494]

need help plz!