Skip to Content
0
Former Member
Apr 30, 2009 at 09:32 PM

server0 will not start. client 100 does not exist.

144 Views

On my NetWeaver 7.0 system with Solution Mgr 7.0 (build from IDES 600 image) on a HPUX 11.23 IA & Oracle with Java 1.4.2.15 installed, I'm going thru the basic setup steps for configuring MOPZ and get to the step

Following IMG basic install steps (basic settings->SAP Solution Manager System->System Landscape(SLD)->Specify service for comm. w/ SLD in Visual Admin), unable to connect to J2EE engine via Visual Admin.

The dev_server0 log:

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

[Thr 6] **********************************************************************

  • 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.

Std_server0.out log:

===========================================================

Apr 27, 2009 8:14:20 AM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_73] Fatal:

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: Client 100 is not available in this system

I ran JCmon to restart the instance.

  1. cd /usr/sap/SMA/ DVEBMGS00/j2ee/os_lib

  2. jcmon pf= /usr/sap/SMA/SYS/profile/SMA_DVEBMGS00_pax3

20: local Admin.

Restarted instance, but same error, client 100 is not available in this system.

std_server0.out details

===============================================================

Apr 30, 2009 4:24:50 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_97] Fatal: Initialization of ABAP data

source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "Client 100 is not available in this system". This message

is critical if it appears during the startup of the AS Java.

Apr 30, 2009 4:24:50 PM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_97] Fatal:

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: Cli

ent 100 is not available in this system

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:81)

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

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Client 100 is not available in this system

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

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

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

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)

... 6 more

com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Cli

ent 100 is not available in this system

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:81)

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

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Client 100 is not available in this system

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

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

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

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)

... 6 more

[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Apr 30, 2009 4:24:50 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_97] Fatal: Critical shutdown was invoke

d. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

============================================================

Solution maybe obvious, create a client 100. But server0 was running fine on this node when I first installed Solution Mgr, and it is running fine on my ERP / BI system that II built from the same IDES media, ofwhich it does not have a client 100 and Java WebAS is running fine. Also, able to connect to portal via http://host:50000/irj. Only difference is I have java 1.4.2.20 installed on the BI system.

So is there some other reason why server0 will not come up?