solman_admin getting locked

[dominik_koop]

Hello,

after I changed the password of the user solman_admin via transaction SU01 and providing new password in the system preparation in solman setup the user gets locked frequently.

Is there any possibility to find out how the user gets locked?

System: Solman 7.1 SPS 11

Regards and thanks in advance,

Dominik

[former_member182967 · Accepted solution]

Hi Dominik,

Why not consider to change it back the privious one.

Regards,

Ning

[dominik_koop · Accepted solution]

Hi Ning,

thank you for replying.

It was a known standard password created at installation, so I had to change it.

I already checked every managed systems configuration if the correct password for solman_admin was maintained and connection is possible. Still I can't figure out why the user is getting locked due to incorrect logons.

Regards,

Dominik

[manish_singh13 · Accepted solution]

Hi Dominik,

Could you please check below config steps in Agent Administration:

1. Navigate to Application Configuration

2. Select property at left pane window "com.sap.smd.agent.application.global.configuration"

3. Drop down Scope and select managed system entries one by one

4. Check if any of the managed system is using SOLMAN_ADMIN under BW/user

5. Update new password for the proper and save.

6. Update the same password in <Global> scope also and save

Check afterwards if user is still getting locked.

Thanks,

Manish

[daniel_nicol · Accepted solution]

Hi Dominik,

You can check in the /smd/AgentAdmin URL in the Solution Manager, tab agent credentials, if any agent is connected with SOLMAN_ADMIN. But likely you will not find the cause of the issue here, because this user could have been used anywhere.

What you can do in cases like this is to try to trace where the call is coming from, for that, follow this wiki: https://wiki.scn.sap.com/wiki/x/iwOEEQ .

If you know where the call is coming from, you can access the source system and export the content of table RFCDES, then do a text search for "SOLMAN_ADMIN" to check if any RFC is using this particular user. Or you can try to perform a direct select on this table, the one below, in this case:

SELECT RFCDEST FROM "RFCDES" WHERE RFCOPTIONS LIKE '%SOLMAN_ADMIN%'.

Kind regards,

Daniel.

[dominik_koop · Accepted solution]

Hi Manish,

thanks for your reply. I will try it and give an update on this issue.

Regards,

Dominik

[dominik_koop · Accepted solution]

Hi Manish,

unfortunately it didn't work.

Regards,

Dominik

[former_member182967 · Accepted solution]

Hi Dominik,

Some hints may help you (sorry, I do not change it before)

In system preparation, step 6.1 Select SLD -> setup local SLD. Have you already changed the solman_admin password?

In basic configuration, step 2.2 setup credentials, Have you already change the password?

Regards,

Ning

[dominik_koop · Accepted solution]

Hi Ning,

I maintained the user with new password in system preparation in setup of SLD and in basic configuration, but user still gets locked.

Regards,

Dominik

[daniel_nicol · Accepted solution]

Hi Dominik,

Please try the solution I described previously, this user could have been used anywhere in an RFC, which won't be changed by changing the credentials via SOLMAN_SETUP, you have to find out where the call is coming from, and then change the credentials.

Kind regards,

Daniel.

[dominik_koop · Accepted solution]

Hi Daniel,

I'm still trying your solution, but for now I didn't get any result. I will keep working on it.

Thanks and regards,

Dominik

[daniel_nicol · Accepted solution]

Let me know if you have any question then.      

[dominik_koop]

Hi,

it looks like the problem is solved.

Since I updated the credentials of one SMD-Agent last thursday the user has not been locked anymore.

Nevertheless, thank you for your help!

Regards,

Dominik

[Former Member]

Hi Dominik!

We are facing the same issue...

Please can you explain exactly how you did it (Setting the credentials)?

Thanks a lot!

Regards

Peter

[dominik_koop]

Hi Peter,

I changed the credentials of the diagnostics agent by using smdsetup script as per following note:

1907909 - How to connect Diagnostics Agent to Solution Manager system directly by using smdsetup scr...

Of course it requires that you know which agent causes the locking of the user.

Regards,

Dominik

[Former Member]

Hi Dominik!

Our problem was solved by adjusting the pw for the BI user following the info by Manish.

Thank you in any case!

Regards

Peter