Solution manager server0 has stopped

[Former Member]

Hi,

Solution manager 4.0 java process table server0 is stopped.

Please suggest what should I do.

Server0 log;-

1}#2#profile#D:
usr
sap
SOL
SYS
profile
SOL_DVEBMGS00_solman#

#1.5 #00151762D2F40000000000080000112C0004AD9619C4F457#1316760095879#/System/Server##com.sap.engine.core.locking.impl3.LockingManagerImpl.initInternal(Properties)#######Thread[Thread-1,5,main]##0#0#Info#1#com.sap.engine.core.locking.impl3.LockingManagerImpl#Java###Value of is #2#enqHost#solman# #1.5 #00151762D2F40000000000090000112C0004AD9619C4F4D6#1316760095879#/System/Server##com.sap.engine.core.locking.impl3.LockingManagerImpl.initInternal(Properties)#######Thread[Thread-1,5,main]##0#0#Info#1#com.sap.engine.core.locking.impl3.LockingManagerImpl#Java###Value of is #2#enqPort#3201# #1.5 #00151762D2F400000000000A0000112C0004AD9619C4F553#1316760095879#/System/Server##com.sap.engine.core.locking.impl3.LockingManagerImpl.initInternal(Properties)#######Thread[Thread-1,5,main]##0#0#Info#1#com.sap.engine.core.locking.impl3.LockingManagerImpl#Java###Value of is #2#enqServerName#EnquServerNo.1#

#1.5 #00151762D2F400000000000B0000112C0004AD9619C4F668#1316760095879#/System/Server##com.sap.engine.core.locking.impl3.LockingManagerImpl.initInternal(Properties)#######Thread[Thread-1,5,main]##0#0#Info#1#com.sap.engine.core.locking.impl3.LockingManagerImpl#Java###Value of is #2#number of connection#1# #1.5 #00151762D2F400000000000C0000112C0004AD9619C56B28#1316760095910#/System/Server##com.sap.engine.core.locking.AbstractLockingManagerImpl.init(properties)#######Thread[Thread-1,5,main]##0#0#Info#1#com.sap.engine.core.locking.AbstractLockingManagerImpl#Java### started successfully#1#LockingManager#

#1.5 #00151762D2F400000000000D0000112C0004AD9619C56BF4#1316760095910#/System/Server##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Info#1#com.sap.engine.core.Framework#Plain###LockingManager started for 47 ms. #

#1.5 #00151762D2F400000000000E0000112C0004AD9619C5D481#1316760095941#/System/Server##com.sap.engine.core.configuration#######Thread[Thread-1,5,main]##0#0#Info#1#com.sap.engine.core.configuration#Plain###ConfigurationManager: found jar for secure store

solman
sapmnt
SOL
SYS
global
security
lib
engine
iaik_jce.jar#

#1.5 #00151762D2F400000000000F0000112C0004AD9619CFC35E#1316760096597#/System/Server##com.sap.engine.core.configuration#######Thread[Thread-1,5,main]##0#0#Info#1#com.sap.engine.core.configuration#Plain###ConfigurationManager: added jars in directory for secure store to Core-Lib classloader

solman
sapmnt
SOL
SYS
global
security
lib
engine#

#1.5 #00151762D2F40000000000100000112C0004AD9619D9F9E8#1316760097285#/System/Server##com.sap.engine.core.configuration#######Thread[Thread-1,5,main]##0#0#Info#1#com.sap.engine.core.configuration#Plain###OpenSQLDataSource successfully created with secure store.#

#1.5 #00151762D2F40000000000120000112C0004AD9619DECC02#1316760097597#/System/Server##com.sap.engine.core.configuration#######Thread[Thread-1,5,main]##0#0#Info#1#com.sap.engine.core.configuration#Plain###Building the specialized statements with hints for SQLServer.#

#1.5 #00151762D2F40000000000130000112C0004AD9619DF9642#1316760097660#/System/Server##com.sap.engine.core.configuration#######Thread[Thread-1,5,main]##0#0#Info#1#com.sap.engine.core.configuration#Java### started successfully#1#ConfigurationManager#

#1.5 #00151762D2F40000000000140000112C0004AD9619DF9735#1316760097660#/System/Server##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Info#1#com.sap.engine.core.Framework#Plain###ConfigurationManager started for 1750 ms. #

#1.5 #00151762D2F40000000000150000112C0004AD9619DFF3A0#1316760097675#/System/Server##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Info#1#com.sap.engine.core.Framework#Plain###LicensingManager started for 15 ms. #

#1.5 #00151762D2F40000000000160000112C0004AD9619E1A77B#1316760097800#/System/Server##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Info#1#com.sap.engine.core.Framework#Plain###CacheManager started for 125 ms. #

#1.5 #00151762D2F40000000000170000112C0004AD9619EFE727#1316760098753#/System/Server##com.sap.engine.core.service630.container.LoadContainer#######Thread[Thread-1,5,main]##0#0#Error#1#com.sap.engine.core.service630.container.LoadContainer#Plain###interface tc_lmctc_culinterface_sda - null jars, incorrect DTD is used .#

#1.5 #00151762D2F40001000000000000112C0004AD9619FD9920#1316760099660#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_52##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service cross started. (63 ms).#

#1.5 #00151762D2F40002000000000000112C0004AD9619FDA34A#1316760099660#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_22##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service file started. (63 ms).#

#1.5 #00151762D2F40003000000000000112C0004AD9619FDB820#1316760099675#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_21##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service memory started. (78 ms).#

#1.5 #00151762D2F40004000000000000112C0004AD9619FDCB95#1316760099675#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_63##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service timeout started. (78 ms).#

#1.5 #00151762D2F40005000000000000112C0004AD9619FE0A04#1316760099691#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_81##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service runtimeinfo started. (47 ms).#

#1.5 #00151762D2F40006000000000000112C0004AD9619FE8807#1316760099722#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_73##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service trex.service started. (94 ms).#

#1.5 #00151762D2F40007000000000000112C0004AD9619FEE8EE#1316760099753#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_10##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service userstore started. (15 ms).#

#1.5 #00151762D2F40008000000000000112C0004AD9619FF2F89#1316760099769#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_72##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service jmx_notification started. (16 ms).#

#1.5 #00151762D2F40009000000000000112C0004AD9619FFE9E3#1316760099816#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_47##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service p4 started. (125 ms).#

#1.5 #00151762D2F4000A000000000000112C0004AD961A002D90#1316760099831#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service classpath_resolver started. (15 ms).#

Thanks,

Abha

[Former Member]

I have the same issue but i did nothing other than changing the client from 100 to 200. The user name and password are the same in the other client as well but my server is not coming online and showing me error in dev_server0. When I revert it back to client 100 it came online fine. The user in both clients have same name/password/roles. What else I am missing.

Thanks in advance for all your help.

[Former Member]

Hi Sukhan,

If you have same password/roles in both clients, it should work fine without any issues.

Please cross check that in both client SAPJSF has same password.

Thanks,

Siva Kumar

[Former Member]

Hi,

SAPJSF password is wrongly updated or it got expired.

Please update the correct password of SAPJSF in UME in config tool.

Thanks,

Siva Kumar

[blanca_serrano]

Hello Abha,

What is the content of ume.r3.connection.master.user parameter? Is SAPJSF?

Please, tell me the results of connecting to ABAP backend system client which J2EE engine connects with the user specified in ume.r3.connection.master.user.

If you can connect, please, go to ume.r3.connection.master.passwd and rewrite the password used when entered in ABAP system and save changes.

Regards,

Blanca

[Former Member]

check datasource xml file in config.

just try to change it from dataSourceConfiguration_database_only.xmol to dataSourceConfiguration_abap.xml and restart again.

Thanks

[blanca_serrano]

Hi Abha,

If ABAP is running then the reason of the error can be that the ABAP communication user that the J2EE Engine uses to connect to the ABAP system with is trying to logon with the wrong

password. What is the java system version?

Please do the following steps carefully in order to check why the user/password is not correct:

- Log on to the ABAP system with a administrator user and go to SU01;

- Ensure that the sapjsf user is not locked, and that the user can authenticate to the ABAP system with the currently defined password;

If not, reset the password:

- Ensure that the password that the J2EE Enigne is using is correct and sysnched with that defined in the ABAP system;

- Open Config Tool and go to cluster-data -> Global Server Configuration -> Sevices -> com.sap.security.ume.service;

- Select the property ume.r3.connection.master.passwd and setup the proper password there;

- Save the changes;

- After that please go to cluster-data -> instance_IDxxxxxx -> server_IDxxxxxx50 -> Sevices -> com.sap.security.ume.service

- You should not see any Local configurations there;

- But if any configuration incidently occurs there, please select it and press the button "Restore to global";

- Also can you confirm that password for sapjsf is synchronized in both the ABAP system and in the global UME properties in the J2EE Engine?

- Please also start the configtool, switch to configuration editor mode

- Then expand cluster_data -> server -> cfg -> services -> Propertysheet.com.sap.security.core.ume.service - click on this and check if there is a value specified for

ume.r3.connection.master.passwd

If there is a value specified, ensure that this is the correct value also.

I hope this helps you.

Regards,

Blanca

[Former Member]

Hi Blanca,

Thanks for the reply.

but it didnt work.

Thanks,

Abha

[blanca_serrano]

Hello Abha,

Can you please provide the std_server log with the traces that show that server stops?

Thanks and regards,

Blanca

[Former Member]

hi Banca,

Please see the below logs

STD_SERVER0

service com.sap.security.core.ume.service ================= ERROR =================

Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Name or password is incorrect (repeat logon)

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)

at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)

at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)

at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)

at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:440)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)

at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)

TRACE:-

[Thr 5332] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver

[Thr 5332] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI

[Thr 4444] JLaunchIExitJava: exit hook is called (rc = -11113)

[Thr 4444] **********************************************************************

• ERROR => The Java VM terminated with a non-zero exit code.

• Please see SAP Note 943602 , section 'J2EE Engine exit codes'

• for additional information and trouble shooting.

**********************************************************************

[Thr 4444] JLaunchCloseProgram: good bye (exitcode = -11113)

Thanks,

Abha