SLDDSUSER keeps locking every 2 hours via SAPJSF user

[Former Member]

This is causing a problem for my JCO connections since the sld data suppliers are using this ID also. The message I am getting in Solution Managers log is:

Dialog work process - User SAPJSF - localhost - Program SAPMSSY1

08:32:24 DIA 000 600 SAPJSF US 1 User SLDDSUSER locked due to incorrect logon

I have no idea where to look to resolve this password problem

As a work around I have tried to change the SLD DATA SUPPLIER to use another ID but the connection does not work for any other ID other then the SLDDSUSER.

In ABAP on solution manager I copied the SLDDSUSER id to another user id then signed into UME and made sure it had the same roles in the UME as SLDDSUSER. The ID's are identical but when I change the user id in Visual Administrator to the new one it still fails.

Can anyone help with either of these problems I figured if the slddsuser keeps locking out then I should eliminate all of the SLD data suppliers (and also at least my JCO connections would stay up)

[marksmyth]

Hello Gayle

If you don't use XI/PI, then perhaps the XI/PI forum is the wrong place to post?? We will forward this thread to the Solution Manager forum.

Regards

Mark Smyth

XI/PI Moderator

[former_member4985]

Hello!

Ensure that you follow the note regarding the passwords for your specific system:

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

Maintain the passwords of all the service users in order to avoid this kind of lock problem.

Regards,

Caio.

[Former Member]

We don't use XI or PI

[former_member264034]

Hi,

If this user is getting locked it means that the credentials maintained

for it in the SU01 are different than the ones maintained in the UME

service in configtool.

Please check that if your SLDDUSER is called with the wrong password in

one of the following locations:

- SLD data supplier Java (in 70 in Visual Admin -> SLD Data Supplier

Service first tab)

- SLD HTTP client ((in 70 in Visual Admin -> SLD Data Supplier Service

second tab)

- SLD ABAP data supplier (transaction RZ70)

- SLD ABAP client (transaction sldapicust)

Regards,

Aidan

[Former Member]

We already check all of those and they were fine

[former_member264034]

Hi,

I assume there are different systems updating the Solution Manager

SLD with this same user. Please identify which system has the incorrect

password, this could be any system within his landscape that is sending

information to the sld.

You need to enable http tracing.

Then you should look at the trace in:

\usr\sap\<SID>\J<NR>\j2ee\cluster\server<x>\log\system\httpaccess

They will see the IP addresses of the various clients. They have to

search for the FIRST occurrence of return code 401 (or 403?).

In addition you should try to use different users for the individual

systems/landscapes for logging on to the SLD.

Regards,

Aidan

[p330068]

Hi Gayle,

If you used SLDDSUSER, it might happen when SAPJSF user using the JCO connection then SLDDSUSER user locked due to incoorect password.

Please check the SLDDSUSER user's password has changed...and update it SLD Data Supplier in visual admin...

If you do SLDDSUSER as service user, then i think SLDDSUSER user will not locked.

Search for SLDDSUSER user required properties....

Hope it helps

Regards

Arun

[Former Member]

Hi,

Enable auditing on user SAPJSF in SM19 and see from which system/ to find the source because of which the user gets locked. And update the password in source, it will resolve your issue.

Regards,

Gowrinadh

[Former Member]

I did this but the info did not help I get the following:

User Terminal Program Security Audit Log message text

SAPJSF localhost SAPMSSY1 Password check failed for user SLDDSUSER in client 600

SAPJSF localhost SAPMSSY1 Logon Failed (Reason = 1, Type = U)