Skip to Content
0
Aug 18, 2011 at 12:59 PM

SLD User gets locked; four unsuccessful logons every 15 minutes

455 Views

I have a landscape with a PI with the SLD on it. I defined a user with the name SLDUSER and the appropriate authorizations. The PI is a Unicode system, like all systems in the landscape.

There were already some application servers (CRM, Banking Services, Composition Environment) connecting to this SLD and everything went fine.

Now I added another application server, an ERP, for FI-CAx (NW 7.02). As the business partners are distributed via XI through the PI system, the ERP needs to connect to the SLD, too.

I set it up as usual:

- sldapicust: host, port, SLDUSER, password. (What is weird is that there is no test button as in all the other systems ... maybe that depends on the installed EhPs.)

- This generated the destinations (type T = TCP/IP) SLD_UC and SLD_NUC automatically.

- I created destinations SAPSLDAPI and LCRSAPRFC manually in sm59, type T = TCP/IP, set them to Unicode, entered the same (two different) Registered Server Programs that are used in these destinations on all the other servers (CRM, PI, BaS).

- I ran rz70, entered the host and gateway, activated, executed the data collection.

SLDCHECK runs successfully on the ERP system!

The technical system for the BS1 showed up in the SLD as expected.

- I configured the clients / business systems on the SLD.

Now begins the problem. The SLDUSER is now getting locked all the time! It's definitely the ERP system causing it - when I prevent it from accessing the PI (by changing the hosts file on the operating system), the problem stops.

I activated everything critical related to logons and RFCs in sm19 and looked at the logs in sm20. This is what it looks like:

-


17.08.2011 19:40:04 BNK_RFC ilbnkpi1 SAPMSSY1 Password check failed for user SLDUSER in client 001

17.08.2011 19:40:04 BNK_RFC ilbnkpi1 SAPMSSY1 Logon Failed (Reason = 1, Type = U)

17.08.2011 19:40:04 BNK_RFC ilbnkpi1 SAPMSSY1 Password check failed for user SLDUSER in client 001

17.08.2011 19:40:04 BNK_RFC ilbnkpi1 SAPMSSY1 Logon Failed (Reason = 1, Type = U)

17.08.2011 19:40:04 BNK_RFC ilbnkpi1 SAPMSSY1 Password check failed for user SLDUSER in client 001

17.08.2011 19:40:04 BNK_RFC ilbnkpi1 SAPMSSY1 Logon Failed (Reason = 1, Type = U)

17.08.2011 19:40:04 BNK_RFC ilbnkpi1 SAPMSSY1 Password check failed for user SLDUSER in client 001

17.08.2011 19:40:04 BNK_RFC ilbnkpi1 SAPMSSY1 Logon Failed (Reason = 1, Type = U)

17.08.2011 19:55:04 BNK_RFC ilbnkpi1 SAPMSSY1 Password check failed for user SLDUSER in client 001

17.08.2011 19:55:04 BNK_RFC ilbnkpi1 SAPMSSY1 User SLDUSER Locked in Client 001 After Erroneous Password Checks

17.08.2011 19:55:04 BNK_RFC ilbnkpi1 SAPMSSY1 Logon Failed (Reason = 1, Type = U)

17.08.2011 19:55:04 BNK_RFC ilbnkpi1 SAPMSSY1 Logon Failed (Reason = 53, Type = U)

17.08.2011 19:55:05 BNK_RFC ilbnkpi1 SAPMSSY1 Logon Failed (Reason = 53, Type = U)

17.08.2011 19:55:05 BNK_RFC ilbnkpi1 SAPMSSY1 Logon Failed (Reason = 53, Type = U)

-


And it goes on like this. So what happens is this: Every 15 minutes, at :10, :25, :40, :55, there are four unsuccessful logons with SLDUSER. With the fifth logon it gets locked.

Again:

- This stops when I make the PI inaccessible to the ERP.

- SLDCHECK still works completely fine in ERP - until the SLDUSER is locked, of course; then it stops working in all connected systems. It does not result in unsuccessful logons on the PI.

- When I run rz70 on the ERP and run the data collection this also reports success and does not create unsuccessful logons on the PI.

- I have not used the SLDUSER in any other locations besides sldapicust.

So what the hell is wrong with this system?!