JAVA Engine Error

Former Member · ‎01-03-2013

Hey experts,

we have installed SAP EHP 1 for SAP Solution Manager 7.0 in windows with DB MaxdB last week after performing an import of a CR in the SLD the MMC shows:

disp+work message server connection ok, Dialog queue time: 0.00 sec, AS Java: Connecting to message server in Yellow

and the Java its down the system does not have sld or mls and in the MMC in the JAVA Process table it is all disable, I've been reading but have not found the solution.

this is the Developer trace:

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

trc file: "dev_disp", trc level: 1, release: "720"

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

sysno 00

sid SOM

systemid 562 (PC with Windows NT)

relno 7200

patchlevel 0

patchno 300

intno 20020600

make multithreaded, Unicode, 64 bit, optimized

profile D:\usr\sap\SOM\SYS\profile\SOM_DVEBMGS00_veccs0004

pid 5020

kernel runs with dp version 134000(ext=119000) (@(#) DPLIB-INT-VERSION-134000-UC)

length of sys_adm_ext is 588 bytes

*** SWITCH TRC-HIDE on ***

***LOG Q00=> DpSapEnvInit, DPStart (00 5020) [dpxxdisp.c 1315]

Thu Jan 03 13:51:13 2013

shared lib "dw_xml.dll" version 300 successfully loaded

shared lib "dw_xtc.dll" version 300 successfully loaded

shared lib "dw_stl.dll" version 300 successfully loaded

shared lib "dw_gui.dll" version 300 successfully loaded

shared lib "dw_mdm.dll" version 300 successfully loaded

shared lib "dw_rndrt.dll" version 300 successfully loaded

shared lib "dw_abp.dll" version 300 successfully loaded

shared lib "dw_sym.dll" version 300 successfully loaded

shared lib "dw_aci.dll" version 300 successfully loaded

rdisp/softcancel_sequence : -> 0,5,-1

use internal message server connection to port 3900

rdisp/dynamic_wp_check : 1

rdisp/calculateLoadAverage : 1

Thu Jan 03 13:51:17 2013

*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds

***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 6423]

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

DpIPCInit2: write dp-profile-values into sys_adm_ext

DpIPCInit2: start server >veccs0004_SOM_00 <

DpShMCreate: sizeof(wp_adm) 43024 (2264)

DpShMCreate: sizeof(tm_adm) 5517056 (27448)

DpShMCreate: sizeof(wp_ca_adm) 19200 (64)

DpShMCreate: sizeof(appc_ca_adm) 6400 (64)

DpCommTableSize: max/headSize/ftSize/tableSize=500/16/1384064/1384080

DpShMCreate: sizeof(comm_adm) 1384080 (2744)

DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

DpShMCreate: sizeof(slock_adm) 0 (296)

DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

DpShMCreate: sizeof(file_adm) 0 (80)

DpShMCreate: sizeof(vmc_adm) 0 (2152)

DpShMCreate: sizeof(wall_adm) (41664/42896/64/192)

DpShMCreate: sizeof(gw_adm) 48

DpShMCreate: sizeof(j2ee_adm) 3952

DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000D3A0050, size: 7072528)

DpShMCreate: allocated sys_adm at 000000000D3A0060

DpShMCreate: allocated wp_adm_list at 000000000D3A3070

DpShMCreate: allocated wp_adm at 000000000D3A3260

DpShMCreate: allocated tm_adm_list at 000000000D3ADA80

DpShMCreate: allocated tm_adm at 000000000D3ADAD0

DpShMCreate: allocated wp_ca_adm at 000000000D8F09E0

DpShMCreate: allocated appc_ca_adm at 000000000D8F54F0

DpShMCreate: allocated comm_adm at 000000000D8F6E00

DpShMCreate: system runs without slock table

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 000000000DA48CA0

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated gw_adm at 000000000DA48D50

DpShMCreate: allocated j2ee_adm at 000000000DA48D90

DpShMCreate: allocated ca_info at 000000000DA49D10

DpShMCreate: allocated wall_adm at 000000000DA49DA0

DpCommAttachTable: attached comm table (header=000000000D8F6E00/ft=000000000D8F6E10)

DpSysAdmIntInit: initialize sys_adm

rdisp/test_roll : roll strategy is DP_NORMAL_ROLL

dia token check not active (8 token)

MBUF state OFF

DpCommInitTable: init table for 500 entries

DpRqQInit: keep protect_queue / slots_per_queue 0 / 2001 in sys_adm

rdisp/queue_size_check_value : -> on,50,30,40,500,50,500,80

EmInit: MmSetImplementation( 2 ).

MM global diagnostic options set: 0

<ES> client 0 initializing ....

<ES> EsILock: use spinlock for locking

<ES> InitFreeList

<ES> block size is 4096 kByte.

<ES> Info: em/initial_size_MB( 8189MB) not multiple of em/blocksize_KB( 4096KB)

<ES> Info: em/initial_size_MB rounded up to 8192MB

Using implementation view

<EsNT> Using memory model view.

<EsNT> Memory Reset disabled as NT default

<ES> 2047 blocks reserved for free list.

ES initialized.

mm.dump: set maximum dump mem to 96 MB

DpVmcSetActive: set vmc state DP_VMC_NOT_ACTIVE

MPI: dynamic quotas disabled.

MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%

Thu Jan 03 13:51:18 2013

*** WARNING => DpJ2eeStart: profile parameter 'system/type' not correctly set to start J2EE; use 'J2EE' for Java only and 'DS' for double stack instance (info=0x101) [dpxxj2ee.c 343]

J2EE server info

start = TRUE

state = STARTED

pid = 6136

argv[0] = D:\usr\sap\SOM\DVEBMGS00\exe\jcontrol.EXE

argv[1] = D:\usr\sap\SOM\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=D:\usr\sap\SOM\SYS\profile\SOM_DVEBMGS00_veccs0004

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=65000

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=SOM

argv[7] = -DSAPMYNAME=veccs0004_SOM_00

argv[8] = -DSAPPROFILE=D:\usr\sap\SOM\SYS\profile\SOM_DVEBMGS00_veccs0004

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG CPS=> DpLoopInit, ICU ( 3.4 3.4 4.1) [dpxxdisp.c 1701]

***LOG Q0K=> DpMsAttach, mscon ( veccs0004) [dpxxdisp.c 12520]

MBUF state LOADING

DpStartStopMsg: send start message (myname is >veccs0004_SOM_00 <)

DpStartStopMsg: start msg sent

CCMS uses Shared Memory Key 73 for monitoring.

Thu Jan 03 13:51:19 2013

CCMS: Initalized shared memory of size 60000000 for monitoring segment.

CCMS: Checking Downtime Configuration of Monitoring Segment.

CCMS: AlMsUpload called by wp 1024.

CCMS: AlMsUpload successful for D:\usr\sap\SOM\DVEBMGS00\log\ALMTTREE.DAT (697 MTEs).

Thu Jan 03 13:51:22 2013

CCMS: start to initalize 3.X shared alert area (first segment).

DpJ2eeLogin: j2ee state = CONNECTED

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1296]

MBUF state ACTIVE

DpWpBlksLow: max wp blocks in queue is 240 (80 %)

MBUF component UP

DpMsgProcess: 1 server in MBUF

DpAppcBlksLow: max appc blocks in queue is 50 (50 %)

Thu Jan 03 13:53:14 2013

DpModState: change server state from STARTING to ACTIVE

Thu Jan 03 13:54:19 2013

***LOG Q0I=> NiIRead: P=127.0.0.1:1034; L=0.0.0.0:65000: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5087]

*** ERROR => NiIRead: SiRecv failed for hdl 33/sock 612

(SI_ECONN_BROKEN/10054; I4; ST; P=127.0.0.1:1034; L=0.0.0.0:65000) [nixxi.cpp 5087]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=6136)

*** ERROR => DpProcKill: kill failed [dpntdisp.c 397]

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Thu Jan 03 13:54:38 2013

J2EE server info

start = TRUE

state = STARTED

pid = 7436

argv[0] = D:\usr\sap\SOM\DVEBMGS00\exe\jcontrol.EXE

argv[1] = D:\usr\sap\SOM\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=D:\usr\sap\SOM\SYS\profile\SOM_DVEBMGS00_veccs0004

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=64998

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=SOM

argv[7] = -DSAPMYNAME=veccs0004_SOM_00

argv[8] = -DSAPPROFILE=D:\usr\sap\SOM\SYS\profile\SOM_DVEBMGS00_veccs0004

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

Thu Jan 03 13:54:40 2013

DpJ2eeLogin: j2ee state = CONNECTED

Thu Jan 03 13:55:55 2013

***LOG Q0I=> NiIRead: P=127.0.0.1:1165; L=0.0.0.0:64998: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5087]

*** ERROR => NiIRead: SiRecv failed for hdl 65/sock 424

(SI_ECONN_BROKEN/10054; I4; ST; P=127.0.0.1:1165; L=0.0.0.0:64998) [nixxi.cpp 5087]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=7436)

*** ERROR => DpProcKill: kill failed [dpntdisp.c 397]

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Thu Jan 03 13:55:58 2013

J2EE server info

start = TRUE

state = STARTED

pid = 7844

argv[0] = D:\usr\sap\SOM\DVEBMGS00\exe\jcontrol.EXE

argv[1] = D:\usr\sap\SOM\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=D:\usr\sap\SOM\SYS\profile\SOM_DVEBMGS00_veccs0004

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=64997

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=SOM

argv[7] = -DSAPMYNAME=veccs0004_SOM_00

argv[8] = -DSAPPROFILE=D:\usr\sap\SOM\SYS\profile\SOM_DVEBMGS00_veccs0004

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

Thu Jan 03 13:56:00 2013

DpJ2eeLogin: j2ee state = CONNECTED

Thu Jan 03 13:57:15 2013

***LOG Q0I=> NiIRead: P=127.0.0.1:1201; L=0.0.0.0:64997: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5087]

*** ERROR => NiIRead: SiRecv failed for hdl 35/sock 420

(SI_ECONN_BROKEN/10054; I4; ST; P=127.0.0.1:1201; L=0.0.0.0:64997) [nixxi.cpp 5087]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=7844)

*** ERROR => DpProcKill: kill failed [dpntdisp.c 397]

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Thu Jan 03 13:57:18 2013

J2EE server info

start = TRUE

state = STARTED

pid = 4696

argv[0] = D:\usr\sap\SOM\DVEBMGS00\exe\jcontrol.EXE

argv[1] = D:\usr\sap\SOM\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=D:\usr\sap\SOM\SYS\profile\SOM_DVEBMGS00_veccs0004

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=64996

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=SOM

argv[7] = -DSAPMYNAME=veccs0004_SOM_00

argv[8] = -DSAPPROFILE=D:\usr\sap\SOM\SYS\profile\SOM_DVEBMGS00_veccs0004

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

Thu Jan 03 13:57:20 2013

DpJ2eeLogin: j2ee state = CONNECTED

Thu Jan 03 13:58:35 2013

***LOG Q0I=> NiIRead: P=127.0.0.1:1237; L=0.0.0.0:64996: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5087]

*** ERROR => NiIRead: SiRecv failed for hdl 67/sock 428

(SI_ECONN_BROKEN/10054; I4; ST; P=127.0.0.1:1237; L=0.0.0.0:64996) [nixxi.cpp 5087]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=4696)

*** ERROR => DpProcKill: kill failed [dpntdisp.c 397]

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Thu Jan 03 13:58:38 2013

J2EE server info

start = TRUE

state = STARTED

pid = 6388

argv[0] = D:\usr\sap\SOM\DVEBMGS00\exe\jcontrol.EXE

argv[1] = D:\usr\sap\SOM\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=D:\usr\sap\SOM\SYS\profile\SOM_DVEBMGS00_veccs0004

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=64995

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=SOM

argv[7] = -DSAPMYNAME=veccs0004_SOM_00

argv[8] = -DSAPPROFILE=D:\usr\sap\SOM\SYS\profile\SOM_DVEBMGS00_veccs0004

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

Thu Jan 03 13:58:40 2013

DpJ2eeLogin: j2ee state = CONNECTED

Thu Jan 03 13:59:55 2013

***LOG Q0I=> NiIRead: P=127.0.0.1:1276; L=0.0.0.0:64995: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5087]

*** ERROR => NiIRead: SiRecv failed for hdl 37/sock 416

(SI_ECONN_BROKEN/10054; I4; ST; P=127.0.0.1:1276; L=0.0.0.0:64995) [nixxi.cpp 5087]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=6388)

*** ERROR => DpProcKill: kill failed [dpntdisp.c 397]

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Thu Jan 03 13:59:58 2013

J2EE server info

start = TRUE

state = STARTED

pid = 7784

argv[0] = D:\usr\sap\SOM\DVEBMGS00\exe\jcontrol.EXE

argv[1] = D:\usr\sap\SOM\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=D:\usr\sap\SOM\SYS\profile\SOM_DVEBMGS00_veccs0004

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=64994

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=SOM

argv[7] = -DSAPMYNAME=veccs0004_SOM_00

argv[8] = -DSAPPROFILE=D:\usr\sap\SOM\SYS\profile\SOM_DVEBMGS00_veccs0004

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

Thu Jan 03 14:00:00 2013

DpJ2eeLogin: j2ee state = CONNECTED

Thu Jan 03 14:01:15 2013

***LOG Q0I=> NiIRead: P=127.0.0.1:1308; L=0.0.0.0:64994: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5087]

*** ERROR => NiIRead: SiRecv failed for hdl 69/sock 412

(SI_ECONN_BROKEN/10054; I4; ST; P=127.0.0.1:1308; L=0.0.0.0:64994) [nixxi.cpp 5087]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=7784)

*** ERROR => DpProcKill: kill failed [dpntdisp.c 397]

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Thu Jan 03 14:01:18 2013

J2EE server info

start = TRUE

state = STARTED

pid = 8184

argv[0] = D:\usr\sap\SOM\DVEBMGS00\exe\jcontrol.EXE

argv[1] = D:\usr\sap\SOM\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=D:\usr\sap\SOM\SYS\profile\SOM_DVEBMGS00_veccs0004

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=64993

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=SOM

argv[7] = -DSAPMYNAME=veccs0004_SOM_00

argv[8] = -DSAPPROFILE=D:\usr\sap\SOM\SYS\profile\SOM_DVEBMGS00_veccs0004

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

Thu Jan 03 14:01:20 2013

DpJ2eeLogin: j2ee state = CONNECTED

Thu Jan 03 14:02:35 2013

***LOG Q0I=> NiIRead: P=127.0.0.1:1352; L=0.0.0.0:64993: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5087]

*** ERROR => NiIRead: SiRecv failed for hdl 39/sock 404

(SI_ECONN_BROKEN/10054; I4; ST; P=127.0.0.1:1352; L=0.0.0.0:64993) [nixxi.cpp 5087]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=8184)

*** ERROR => DpProcKill: kill failed [dpntdisp.c 397]

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Thu Jan 03 14:02:38 2013

J2EE server info

start = TRUE

state = STARTED

pid = 3892

argv[0] = D:\usr\sap\SOM\DVEBMGS00\exe\jcontrol.EXE

argv[1] = D:\usr\sap\SOM\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=D:\usr\sap\SOM\SYS\profile\SOM_DVEBMGS00_veccs0004

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=64992

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=SOM

argv[7] = -DSAPMYNAME=veccs0004_SOM_00

argv[8] = -DSAPPROFILE=D:\usr\sap\SOM\SYS\profile\SOM_DVEBMGS00_veccs0004

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

Thu Jan 03 14:02:40 2013

DpJ2eeLogin: j2ee state = CONNECTED

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

and when I do a r3trans –d it says "connect failed with dbli_rc_load_lib_failed." r3trans finished <0012>

i have been reading about this.... could be network issues?? or can be kernel?

Someone will have an idea of how to solve this problem???

Regards,

Alejandro.

Former Member · ‎01-08-2013

If the above does not help, i think you need to go back and see what changed. I see that it worked for you at some point in time. What changes caused it to break. you mentioned SLD change which is unlikely. Do you have another system with similar setup you can refer. You can approach SAP, they can login to your system and help you.

Former Member · ‎01-07-2013

Hi all i found here the new server.0.log here it is:

This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 1 seconds.

Could not start server: Connect to SAP gateway failed

Connect parameters: TPNAME=SAPSLDAPI_SOM GWHOST=SOLUTION GWSERV=sapgw00

ERROR partner '192.168.10.94:sapgw00' not reached

TIME Sun Oct 30 03:20:38 201

RELEASE 701

COMPONENT NI (network interface)

VERSION 38

RC -10

MODULE nixxi.cpp

LINE 2835

DETAIL NiPConnect2

SYSTEM CALL connect

ERRNO 10065

ERRNO TEXT WSAEHOSTUNREACH: No route to host

COUNTER 3

##

#1.5 #005056C00001000300000004000003480004B07F60D1D094#1319961038546#/System/Server##com.sap.engine.services.rfcengine.Bundle.startAll()#######SAPEngine_System_Thread[impl:5]_73##0#0#Error#1#com.sap.engine.services.rfcengine#Java###Failed to start first thread for JCo RFC Provider bundle SAPSLDAPI_SOM##

#1.5 #005056C00001000300000006000003480004B07F60D1D6E3#1319961038546#/System/Server##com.sap.engine.services.rfcengine.RFCEngineThreadStarter.run()#######SAPEngine_System_Thread[impl:5]_73##0#0#Error#1#com.sap.engine.services.rfcengine#Java###JCo RFC Provider bundle SAPSLDAPI_SOM failed to start##

#1.5 #005056C00001000000000002000004D80004B07F67CE1E25#1319961155734#/System/Server/Critical##com.sap.engine.core.cluster.impl6.ClusterManagerImpl#######Thread[Thread-1,5,main]##0#0#Error#1#com.sap.engine.core.cluster.impl6.ClusterManagerImpl#Plain###Cannot attach to the Message Server#

#1.5 #005056C00001000000000008000004D80004B07F67CE3175#1319961155734#/System/Server##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Error#1#com.sap.engine.core.Framework#Plain###Loading: ClusterManager returned false! #

#1.5 #005056C0000100000000000A000004D80004B07F67CE336E#1319961155734#/System/Server##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Error#1#com.sap.engine.core.Framework#Plain###Kernel not loaded. System halted.#

#1.5 #0018FE7550F200000000000C000017400004B099C00379A7#1320074304796#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_53##0#0#Error#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service com.sap.security.core.ume.service error. Nested exception is: com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Connect to message server host failed

Connect_PM TYPE=B MSHOST=localhost GROUP=PUBLIC R3NAME=SOM MSSERV=sapmsSOM PCS=1

ERROR Group PUBLIC not found

TIME Mon Oct 31 10:48:24 201

RELEASE 701

COMPONENT LG

VERSION 5

RC -6

MODULE lgxx.c

LINE 4300

DETAIL LgIGroupX

COUNTER 1

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

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

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to message server host failed

Connect_PM TYPE=B MSHOST=localhost GROUP=PUBLIC R3NAME=SOM MSSERV=sapmsSOM PCS=1

ERROR Group PUBLIC not found

TIME Mon Oct 31 10:48:24 201

RELEASE 701

COMPONENT LG

VERSION 5

RC -6

MODULE lgxx.c

LINE 4300

DETAIL LgIGroupX

COUNTER 1

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

... 6 more

#

#1.5 #0018FE7550F200000000000E000017400004B099C0039E49#1320074304796#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_53##0#0#Error#1#/System/Server#Plain###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#

#1.5 #0018FE7550F2000000000010000017400004B099C003A14C#1320074304796#/System/Server/Critical##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_53##0#0#Fatal#1#com.sap.engine.core.Framework#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#

#1.5 #0018FE7550F200000000000C00001A9C0004B099C1361249#1320074324859#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_59##0#0#Error#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service com.sap.security.core.ume.service error. Nested exception is: com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Connect to message server host failed

Connect_PM TYPE=B MSHOST=localhost GROUP=PUBLIC R3NAME=SOM MSSERV=sapmsSOM PCS=1

ERROR Group PUBLIC not found

TIME Mon Oct 31 10:48:44 201

RELEASE 701

COMPONENT LG

VERSION 5

RC -6

MODULE lgxx.c

LINE 4300

DETAIL LgIGroupX

COUNTER 1

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

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