solman_admin password changes results in errors during managed system setup

[former_member310674]

Hello all,

I am trying to get Solman 4.0 EHP 1 to work, but get numberous problems.

Currently I have 6 messages at SAP, but no solution yet.

Situation:

Solman 4.0

SAP_BASIS 701 0003

SAP_ABA 701 0003

ST-PI 2008_1_700 0000

PI_BASIS 701 0003

SAP_BW 701 0003

CRMUIF 500 0001

SAP_AP 700 0014

BBPCRM 500 0013

CPRXRPM 400 0014

BI_CONT 704 0002

ST 400 0019

ST-A/PI 01L_CRM570 0000

ST-ICO 150_700 0016

ST-SER 701_2008_2 0002

So, it is uptodate.

The problem:

Changing the solman_admin password results in errors during connecting a managed system.

In the inital setup the solman_admin is created with a pasword.

After the basic setup I setup some managed systems.

In the meantime I had to change the password of solman_admin

I am logged in with solman_admin and do solman_setup to setup the managed system.

During the setup a process tries to logon back to the solman using solman_admin and the incorrect password.

This is the logging:

Step SSO Details

Found SID for SSO ACL entry : MSD

Found login.ticket_client for SSO ACL entry : 000

The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc_{webadministrator}solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar

The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (823 bytes)

A failure occured while connecting to ABAP stack on localhost sys=70 client=300 user=SOLMAN_ADMIN

!! Exception : Password logon no longer possible - too many failed attempts

A failure occured while importing ABAP SSO ticket certificate in ABAP stack

!! Exception : java.lang.NullPointerException

Java SSO ticket certificate of MSD was imported in ABAP PSE of kswv024.mob.local (client 300)

The Java SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=MSD LoginTicketClient=000)

Anyone else has this problem?

gr

Sander

[rkresha · Accepted solution]

Just for clarification it's Solman 7.0 EHP1 correct?

Also you may want to unlock the following user:

localhost sys=70 client=300 user=SOLMAN_ADMIN

Then if you navigate (in solution manager) to TCode solman_workcenter -> "Root Cause Analysis" tab ->"Agent Administration" menu item on the left -> "Applications Configuration" tab -> under the Agent Applications - Configuration menu on the left select "com.sap.smd.agent.application.global.configuration" -> Change the "Scope" drop down in the frame to the right to the SMD agent that you are using for "localhost sys=70 client=300" -> Click the "edit" button to the right of the Scope drop down box -> now find the entry below that lists "SOLMAN_ADMIN" as the user and find the corresponding password entry and update it with the new password that you changed it to -> click save and try the managed setup again.

Hope this helps, please let me know and we can go from there.

[changzheng_zhao · Accepted solution]

This is really helpful. Thanks to Rob!

[Former Member · Accepted solution]

After resetting the password in "com.sap.smd.agent.application.global.configuration", do we need to restart the JAVA to effect the parameter?

[Former Member · Accepted solution]

After resetting the password in "com.sap.smd.agent.application.global.configuration", do we need to restart the JAVA to effect the parameter?

[Former Member]

Please check that in trabsaction Strustsso2 you have entry of Portal in the ACl in Client 300.

Check that the certificate have valid date.

Please explain when are you getting the Error message.

Thanks Rishi Abrol

[former_member310674]

HI

There is no Portal in this setup.

The only thing that I do is try to connect a managed system in solman diag solman_setup.