Issue in SOLMAN SLD

[former_member201800]

Hi,

I am not able to login to SLD of solman system. I am able to open the link of SLD. Also, I am not able to login to UME or system info also. It is giving wrong user name of password issue.

I have checked the rfc SAPSLDAPI and its working fine.

Also, in SLDAPICUST, check is getting failed with below error:

An exception has occurred:

Exception in SLD client: AbapSLDRequestHandler.ping(): server connection *** failed *** on Fri Jun 17 05:30:26 EDT 2016

Connection to SLD does not work

In SLDCHECK, I am able to open the link, but not able to login to the SLD. Giving the wrong user name and password error.

Please suggest.

Regards,

Shyam Kumar

[Johan_sapbasis · Accepted solution]

Hi,

If you logon to solman ume/sld you would be using j2ee_admin the administrator user for dual stack systems.

So logon to ABAP and go to su01 see if your user j2ee_admin is locked there? If j2ee_admin is locked you will need to unlock it and change the password.

Also in the sldapicust of your other system connecting to solman what user/host details are maintained there? And what are the details of your solution manager system?

Kind Regards,

[former_member201800 · Accepted solution]

Hi Nicolaas,

Thanks for the reply. I checked user j2ee_admin in abap, and its working fine. I am not able to login to the sld by any user. This is happening after restarting the system yesterday.

Also, in sldapicust, sldapiuser  user is used and the host is solman host.

The port we are using is 8000.

Kind Regards,

Shyam

[Johan_sapbasis · Accepted solution]

Hi,

Is the sldapiuser locked?

What is configured in the rfc's for SLD_UC and SLD_NUC should match your your RZ70 details is this the case?

Perhaps give a screenshot? Double check that your sapjsf in abap is not locked.

Kind Regards,

[former_member201800 · Accepted solution]

Hi Nicolaas,

No, sldapiuser is not locked. Also both the rfc are running fine.

Also, sapjsf is not locked.

Regards,

Shyam

[Johan_sapbasis · Accepted solution]

Hi,

At this point I would recommend you look at your java logs to see what is going on there.

/usr/sap/<SID>/DVEBMGS<InstNo>/j2ee/cluster/server0/log

Check your defaultTrace.*.trc log in detail

Check your applications.*.log log in detail

Go to subfolder /usr/sap/<SID>/DVEBMGS<InstNo>/j2ee/cluster/server0/log/system

In here is a security log if you say you can logon here and default trace is where I would check first.

server.*.log

security.*.log

Kind Regards,

[former_member201800 · Accepted solution]

Hi Nicolaas,

Please find the below logs:

Default trace:

#/Applications/Scheduler#Plain#SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot get connection for 120 seconds. Possible reasons: 1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine), 2) The pool size of adapter "SAPSR3DB" is not enough according to the current load of the system or 3) The specified time to wait for connection is not enough according to the pool size and current load of the system. In case 1) the solution is to check for cached connections using the Connector Service list-conns command, in case 2) to increase the size of the pool and in case 3) to increase the time to wait for connection property. In case of application thread, there is an automatic mechanism which detects unclosed connections and unfinished transactions. com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot get connection for 120 seconds. Possible reasons: 1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine), 2) The pool size of adapter "SAPSR3DB" is not enough according to the current load of the system or 3) The specified time to wait for connection is not enough according to the pool size and current load of the system. In case 1) the solution is to check for cached connections using the Connector Service list-conns command, in case 2) to increase the size of the pool and in case 3) to increase the time to wait for connection property. In case of application thread, there is an automatic mechanism which detects unclosed connections and unfinished transactions.###

Security log:

#1.5 #000D3A00CC6A005D00006E53000036380005357964A6B660#1466170380429#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#J2EE_GUEST#0##5AF8866F348D11E685E30000007247AA#5af8866f348d11e685e30000007247aa-0#5af8866f348d11e685e30000007247aa#SAPEngine_Application_Thread[impl:3]_33##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.FAILED

User: N/A

Authentication Stack: service.naming

Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details

1. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   SUFFICIENT  ok          false                 false     

2. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false                 true      

3. com.sap.engine.services.security.server.jaas.ClientCertLoginModule      SUFFICIENT  ok          false                 false     

4. com.sap.security.core.server.jaas.CreateTicketLoginModule               SUFFICIENT  ok          false                 true      

5. com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule    SUFFICIENT  ok          exception             true       Received no SAP Authentication Assertion Ticket.

6. ...om.sap.engine.services.security.server.jaas.SecuritySessionLoginModulSUFFICIENT  ok          exception             true       Authentication did not succeed.#

#1.5 #000D3A00CC6A006D00006CA6000036380005357964C31BC8#1466170382289#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#J2EE_GUEST#0##A3B15406348F11E6C5890000007247AA#a3b15406348f11e6c5890000007247aa-0#a3b15406348f11e6c5890000007247aa#SAPEngine_Application_Thread[impl:3]_5##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.FAILED

User: N/A

Authentication Stack: service.naming

Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details

1. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   SUFFICIENT  ok          false                 false     

2. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false                 true      

3. com.sap.engine.services.security.server.jaas.ClientCertLoginModule      SUFFICIENT  ok          false                 false     

4. com.sap.security.core.server.jaas.CreateTicketLoginModule               SUFFICIENT  ok          false                 true      

5. com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule    SUFFICIENT  ok          exception             true       Received no SAP Authentication Assertion Ticket.

6. ...om.sap.engine.services.security.server.jaas.SecuritySessionLoginModulSUFFICIENT  ok          exception             true       Authentication did not succeed.#

[Johan_sapbasis · Accepted solution]

Hi,

is it possible for you you to do restart of java only? If you are allowed smicm-> j2ee-> global-> hard -> shutdown -> with restart

then wait for java to restart depending on system give it 10 to 15 minutes.

lets see what a clean restart does, if issue persists i would suggest then to look at visual administrator and increase the connection pool for sapsr3db.

kind regards,

johan

[former_member201800 · Accepted solution]

Hi,

I resolved the issue. But now, i am facing issue in SLD and LMDB sync.

Job SAP_LMDB_LDB_0000000001 running successfully, but it is not updating.

Below is the job log:

Job started

Step 001 started (program AI_LMDB_R_SYNC_RUNNER, variant LDB_0000000001, user ID SOLMAN_BTC)

Starting synchronization for target namespace active

Starting synchronization from destination: LMDB_SyncDest1 (SLD and LMDB sync)

Source URL: http://XXXX.XXXX.AAAA.com:8000/sld/cimom, source namespace: sld/active

Starting incremental synchronization phase...

Current number of pending changes: 0

Incremental sync. summary: 0 changes, 0 filtered, runtime 449s

Content synchronization finished successfully

Job finished

Also, due to this, i am not able to complete system preparation in Solman_setup.

Step: Setup LMDB

Please suggest.

Thanks

Shyam

[Johan_sapbasis · Accepted solution]

Hi Shyam,

That is a seperate thread which I recommend you start in the SAP Solution Manager space and not in sap netweaver administrator.

Johan