server0 exitcode -11113

[former_member207130]

hey guys,

our java stack only system doesnt start the server0 cluster anymore. I think because there a wrong version of the JEE deployment. I cant undeploy/update or something else because server0 ist not running. exitcode -11113 is usually a locked user or memory problem. No users are locked. memory is enough. I didnt find something to "core services not loaded"

We are on 7.01 but the SAP-JEE is on 7.02 dont know how this is possible 😉

std_server0. shows

[Framework -> criticalShutdown] 11 core services not loaded: [connector; userstore; adminadapter; security; file; jmx; deploy; com.sap.security.core.ume.service; jmx_notification; basicadmin; dbpool]. Please check default trace files for details.

Oct 8, 2013 9:53:12 AM              com.sap.engine.core.Framework [Thread[Thread-1,5,main]] Fatal: Critical shutdown was invoked. Reason is: 11 core services not loaded: [connector; userstore; adminadapter; security; file; jmx; deploy; com.sap.security.core.ume.service; jmx_notification; basicadmin; dbpool]. Please check default trace files for details.

  Service memory started. (31 ms).

[Sriram2009]

Hi

Could you refer the SAP KBA 1658911 - J2EE System fails with "exitcode = -11113"

Thanks

Sriram

[Former Member]

Hi,

Please Make sure that the users J2EE_ADMIN, SAPJSF & J2EE_GUEST are not locked. If mention user's are locked, unlock them and then try to start the instance once again.

[Former Member]

Hi ,

As you are deploying Jee you should patch all of them together.

• SAP-JEECOR
• SAP-JEE
• SAP_JTECHS
• SAP_JTECHF  

Due to the highly tight interdependency model of the Java Core, if you apply a patch in any of the main components of the Core, you will have to patch also the other related components.

Use SDM to deploy all the patches. this note tell that you should deploy all of them together.

1893013 - Importing AS Java Core patches for NetWeaver 2004s

Thanks

RishI abrol

[former_member207130]

the users on the connected ABAP System are not locked and on the java system i cant connect to the user management because server0 is down

[former_member207130]

i solved this problem over SDM RemoteGui

sap\<SID>\J<SNR>\SDM\program\ RemoteGui.bat and deployed all JEE Data to 7.02 14 .. now server0 runs

[former_member185239]

Hi Steffan,

You need to raise a message to SAP and asked them to provide the extra mile (batchdeployer tool).

with the help of batch deployer you will able to deploy the patches in offline mode.

With Regards

Ashutosh Chaturvedi

[Reagan]

Hello

Reason is: 11 core services not loaded: [connector; userstore; adminadapter; security; file; jmx; deploy; com.sap.security.core.ume.service; jmx_notification; basicadmin; dbpool]. Please check default trace files for details

Have you checked the default trace file ?

Regards

RB

[former_member185239]

Hi Steffan,

You need to redploy the core components through extramile (batch deployer)

you will get the batchdeployer tool in ../bootstrap/script directory. If you don't have you need to raise a message with SAP.

Batchdeployer is used to deploy the component if your java system is down.

Moreover -11113 is related to UME issue. If it is a dual system or UME used for this system is Abap you need to check the SAPJSF user.

Also paste the logs for default trace for server0 node.

With Regards

Ashutosh Chaturvedi

[former_member207130]

got no bootstrap/script directory ..

------------------------- Loader Info -------------------------

ClassLoader name: [service:runtimeinfo]

Parent loader name: [Frame ClassLoader]

References:

   interface:appcontext

   interface:security

Resources:

   D:\\usr\\sap\\EPO\\JC03\\j2ee\\cluster\\server0\\bin\\services\\runtimeinfo\\runtimeinfo.jar

Loading model: {parent,local,references}

---------------------------------------------------------------

The error occurred while trying to load "com.sap.engine.services.runtimeinfo.RuntimeInfoProvider".

          at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)

          at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)

          at java.lang.Class.forName0(Native Method)

          at java.lang.Class.forName(Class.java:219)

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

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

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

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

#

#1.5 #00155D73B10300020000000300000EBC0004E757AD0C612E#1380263658282#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_27##0#0#Error#1#/System/Server#Java###Core service runtimeinfo failed. J2EE Engine cannot be started.

[EXCEPTION]

{0}#1#java.lang.NoClassDefFoundError: com/sap/tc/logging/interfaces/IRPPublisherExt

------------------------- Loader Info -------------------------

ClassLoader name: [service:runtimeinfo]

Parent loader name: [Frame ClassLoader]

References:

   interface:appcontext

   interface:security

Resources:

   D:\\usr\\sap\\EPO\\JC03\\j2ee\\cluster\\server0\\bin\\services\\runtimeinfo\\runtimeinfo.jar

Loading model: {parent,local,references}

---------------------------------------------------------------

The error occurred while trying to load "com.sap.engine.services.runtimeinfo.RuntimeInfoProvider".

          at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)

          at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)

          at java.lang.Class.forName0(Native Method)

          at java.lang.Class.forName(Class.java:219)

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

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

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

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

#

#1.5 #00155D73B10300020000000500000EBC0004E757AD0C62BE#1380263658282#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_27##0#0#Fatal#1#/System/Server/Critical#Plain###Critical shutdown was invoked. Reason is: Core service runtimeinfo failed. J2EE Engine cannot be started.#

#1.5 #00155D73B1030001000000000000151C0004E757AD773A12#1380263665297#com.sap.engine.core.cluster.impl6.JoinPortListener##com.sap.engine.core.cluster.impl6.JoinPortListener.run()#######SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain###java.io.IOException: Cannot read connection identification byte.#

#1.5 #00155D73B1030001000000010000151C0004E757AD77447C#1380263665297#com.sap.engine.core.cluster.impl6.JoinPortListener##com.sap.engine.core.cluster.impl6.JoinPortListener.run()#######SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain###java.io.IOException: Cannot read connection identification byte.

          at com.sap.engine.core.cluster.impl6.JoinPortListener$SocketProcessor.run(JoinPortListener.java:166)

          at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

          at java.security.AccessController.doPrivileged(Native Method)

          at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

the defaulttrace is very big 8 mb most lines are like this

#1.5 #00155D73B103000000000161000017680004E8360F7DDA9D#1381218792632#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Fatal#1#/System/Server/Critical#Plain###Critical shutdown was invoked. Reason is: 11 core services not loaded: [connector; userstore; adminadapter; security; file; jmx; deploy; com.sap.security.core.ume.service; jmx_notification; basicadmin; dbpool]. Please check default trace files for details.#

#1.5 #00155D73B10300000000015F000017680004E8360F75DABA#1381218792100#com.sap.engine.core.service630.container.ReferenceResolver##com.sap.engine.core.service630.container.ReferenceResolver#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Classload error; cannot load library caf~runtime~uicoupling~api~lib because an error in loading referenced library tc~ddic~ddicruntime occurred.#

the last line

#1.5 #00155D73B103000000000161000017680004E8360F7DDA9D#1381218792632#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Fatal#1#/System/Server/Critical#Plain###Critical shutdown was invoked. Reason is: 11 core services not loaded: [connector; userstore; adminadapter; security; file; jmx; deploy; com.sap.security.core.ume.service; jmx_notification; basicadmin; dbpool]. Please check default trace files for details.#

[Former Member]

Try to deploy the correct version of SAP-JEE component with SDM tool.

[former_member207130]

currently i cant redeploy it because server0 cluster is not running

[Former Member]

Can you provide errors you have received during deployment with SDM?

[sunny_pahuja2]

Could you please look for possible error in default trace files and also, paste here?

Thanks,

Sunny

[Nibu]

Looks  issues with your UME/ dbpool . Check below thread ,hope it ll help

http://scn.sap.com/thread/100173