SLDDSUSER Getting Frequently Locked

[former_member188073]

Hi Team,

I know a lot of discussions are there about this very same topic. I still couldn't find why for my landscape.

Our NWDI is on 7.3 with all track having 7.01 BI Java systems. I am not able to zero in the source system causing the lockouts. Would it be the NWDI system itself, the runtime systems or the SLD??

Regards,

Varun

[Former Member]

Hi Varun,

unfortunately it may happen due to many reasons. one of the famous reason is due to some of the background programs which changes the tables resulting in some strange changes like yours.

you can try to figure out how your SLDDUSER is frequently getting locked by doing the following

go to transaction>>SE38 and

execute program RSUSR100N

in standard selection area

USER = SLDDUSER

specify the date range

in output area

select CHANGE HISTORY LIST(default option)

in selection criteria >> under user attributes

select ADMINISTRATOR LOCK SET

EXECUTE

hope this will give you a clue. if not try with option "technical view" in output area.

Regards,

Nag.

[former_member188073]

My SLDDS User is getting locked on the NWDI. So, would it be becuase of the ABAP Backend, as you suggested or the Portal Runtime systems??

[former_member188073]

infact the backend does not have any user with such name (SLDDSUSER)

[former_member264034]

Hi,

Please change/check the following connections (on the Solution Manager
and the connected systems) for the new passwords.

ABAP: SLDAPICUST
ABAP system, transaction SLDAPICUST

J2EE: SLD DATA SUPPLIER
VisualAdmin, Service SLD Data Supplier

J2EE: JCo RFC Provider
VisualAdmin, Service Jco RFC Provider

DIAGNOSTIC AGENT
Script smdsetup with arguments

- 1650035 SLDDSUSER locked due to incorrect logon to SLD

Regards,

Aidan

[former_member188073]

Is there no way to find out from some log or something that what/who is locking this user??

[ErvinSzolke]

Hello Varun,

the note related to this topic that crosses my mind is this:
#1493272 -- A user gets locked automatically

http://service.sap.com/sap/support/notes/1493272

Java security is not exactly the area of my expertise so as far as I understood this note it won't exactly tell you who and why locking your user, but at least you can figure out which client (IP) is sending the request, and having this information you will know at least where to look for the problem.

I hope this helps to narrow down the problem a bit.

Best Regards,
Ervin

[former_member264034]

Hi,

You could enable http tracing.
Please check note: 724719
This note describes how traces of HTTP requests and responses can be
obtained.

The recommendation of SAP Note 724719 is to
set the value of property "HttpTrace" = "enableHeaders".
This should help us in identifying the source IP of the incorrect
HTTP request.

Then you should look at the trace in:
\usr\sap\<SID>\J<NR>\j2ee\cluster\server<x>\log\system\httpaccess
search for the FIRST occurrence of return code 401 (or 403?).

Regards,

Aidan