Instance can not be started successfully!

Question

The process "disp+work.EXE" is yellow and has the status "Running but Dialog Queue standstill, J2EE: Connection to message server"
The system is ECC6.0+MaxDB on Windows Server 2003
Following is the developer trace:
trc file: "dev_disp", trc level: 1, release: "700"
sysno      03
sid        EC1
systemid   560 (PC with Windows NT)
relno      7000
patchlevel 0
patchno    52
intno      20050900
make:      multithreaded, Unicode, optimized
pid        7552
Wed Aug 02 17:39:56 2006
kernel runs with dp version 210000(ext=109000) (@(#) DPLIB-INT-VERSION-210000-UC)
length of sys_adm_ext is 572 bytes
SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (03 7552) [dpxxdisp.c   1231]
     shared lib "dw_xml.dll" version 52 successfully loaded
     shared lib "dw_xtc.dll" version 52 successfully loaded
     shared lib "dw_stl.dll" version 52 successfully loaded
     shared lib "dw_gui.dll" version 52 successfully loaded
rdisp/softcancel_sequence :  -> 0,5,-1
Wed Aug 02 17:40:05 2006
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 9 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  5233]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >superjxy_EC1_03                         <
DpShMCreate: sizeof(wp_adm)          12672     (1408)
DpShMCreate: sizeof(tm_adm)          3954072     (19672)
DpShMCreate: sizeof(wp_ca_adm)          24000     (80)
DpShMCreate: sizeof(appc_ca_adm)     8000     (80)
DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064
DpShMCreate: sizeof(comm_adm)          528064     (1048)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm)          0     (72)
DpShMCreate: sizeof(vmc_adm)          0     (1452)
DpShMCreate: sizeof(wall_adm)          (38456/34360/64/184)
DpShMCreate: sizeof(gw_adm)     48
DpShMCreate: SHM_DP_ADM_KEY          (addr: 07310040, size: 4607512)
DpShMCreate: allocated sys_adm at 07310040
DpShMCreate: allocated wp_adm at 07311E28
DpShMCreate: allocated tm_adm_list at 07314FA8
DpShMCreate: allocated tm_adm at 07314FD8
DpShMCreate: allocated wp_ca_adm at 076DA570
DpShMCreate: allocated appc_ca_adm at 076E0330
DpShMCreate: allocated comm_adm at 076E2270
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 07763130
DpShMCreate: allocated gw_adm at 07763170
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 077631A0
DpShMCreate: allocated wall_adm at 077631A8
Wed Aug 02 17:40:06 2006
MBUF state OFF
EmInit: MmSetImplementation( 2 ).
MM diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation flat
<EsNT> Memory Reset disabled as NT default
<ES> 511 blocks reserved for free list.
ES initialized.
Wed Aug 02 17:40:07 2006
J2EE server info
  start = TRUE
  state = STARTED
  pid = 6588
  argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=3540
  argv[5] = -DSAPSYSTEM=03
  argv[6] = -DSAPSYSTEMNAME=EC1
  argv[7] = -DSAPMYNAME=superjxy_EC1_03
  argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  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.0 3.0 4.0.1) [dpxxdisp.c   1617]
***LOG Q0K=> DpMsAttach, mscon ( superjxy) [dpxxdisp.c   11414]
DpStartStopMsg: send start message (myname is >superjxy_EC1_03                         <)
DpStartStopMsg: start msg sent
Wed Aug 02 17:40:08 2006
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
Wed Aug 02 17:40:09 2006
CCMS: start to initalize 3.X shared alert area (first segment).
DpJ2eeLogin: j2ee state = CONNECTED
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1050]
DpMsgAdmin: Set patchno for this platform to 52
Release check o.K.
Wed Aug 02 17:41:55 2006
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1528
     (SI_ECONN_BROKEN; I4; ST; 127.0.0.1:3552) [nixxi.cpp    4235]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=6588)
ERROR => DpProcKill: kill failed [dpntdisp.c   371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Wed Aug 02 17:42:08 2006
J2EE server info
  start = TRUE
  state = STARTED
  pid = 5704
  argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=3618
  argv[5] = -DSAPSYSTEM=03
  argv[6] = -DSAPSYSTEMNAME=EC1
  argv[7] = -DSAPMYNAME=superjxy_EC1_03
  argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  argv[9] = -DFRFC_FALLBACK=ON
  argv[10] = -DFRFC_FALLBACK_HOST=localhost
  start_lazy = 0
  start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Wed Aug 02 17:43:24 2006
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
ERROR => NiIRead: SiRecv failed for hdl 6 / sock 1488
     (SI_ECONN_BROKEN; I4; ST; 127.0.0.1:3619) [nixxi.cpp    4235]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=5704)
ERROR => DpProcKill: kill failed [dpntdisp.c   371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Wed Aug 02 17:43:28 2006
J2EE server info
  start = TRUE
  state = STARTED
  pid = 7028
  argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=3650
  argv[5] = -DSAPSYSTEM=03
  argv[6] = -DSAPSYSTEMNAME=EC1
  argv[7] = -DSAPMYNAME=superjxy_EC1_03
  argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  argv[9] = -DFRFC_FALLBACK=ON
  argv[10] = -DFRFC_FALLBACK_HOST=localhost
  start_lazy = 0
  start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Wed Aug 02 17:44:49 2006
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1480
     (SI_ECONN_BROKEN; I4; ST; 127.0.0.1:3651) [nixxi.cpp    4235]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=7028)
ERROR => DpProcKill: kill failed [dpntdisp.c   371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Wed Aug 02 17:45:08 2006
J2EE server info
  start = TRUE
  state = STARTED
  pid = 6392
  argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=3692
  argv[5] = -DSAPSYSTEM=03
  argv[6] = -DSAPSYSTEMNAME=EC1
  argv[7] = -DSAPMYNAME=superjxy_EC1_03
  argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  argv[9] = -DFRFC_FALLBACK=ON
  argv[10] = -DFRFC_FALLBACK_HOST=localhost
  start_lazy = 0
  start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Wed Aug 02 17:46:30 2006
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
ERROR => NiIRead: SiRecv failed for hdl 6 / sock 1476
     (SI_ECONN_BROKEN; I4; ST; 127.0.0.1:3693) [nixxi.cpp    4235]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=6392)
ERROR => DpProcKill: kill failed [dpntdisp.c   371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Wed Aug 02 17:46:48 2006
J2EE server info
  start = TRUE
  state = STARTED
  pid = 7064
  argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=3728
  argv[5] = -DSAPSYSTEM=03
  argv[6] = -DSAPSYSTEMNAME=EC1
  argv[7] = -DSAPMYNAME=superjxy_EC1_03
  argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  argv[9] = -DFRFC_FALLBACK=ON
  argv[10] = -DFRFC_FALLBACK_HOST=localhost
  start_lazy = 0
  start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Wed Aug 02 17:48:10 2006
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1496
     (SI_ECONN_BROKEN; I4; ST; 127.0.0.1:3729) [nixxi.cpp    4235]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=7064)
ERROR => DpProcKill: kill failed [dpntdisp.c   371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Wed Aug 02 17:48:28 2006
J2EE server info
  start = TRUE
  state = STARTED
  pid = 5660
  argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=3764
  argv[5] = -DSAPSYSTEM=03
  argv[6] = -DSAPSYSTEMNAME=EC1
  argv[7] = -DSAPMYNAME=superjxy_EC1_03
  argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  argv[9] = -DFRFC_FALLBACK=ON
  argv[10] = -DFRFC_FALLBACK_HOST=localhost
  start_lazy = 0
  start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Wed Aug 02 17:49:44 2006
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
ERROR => NiIRead: SiRecv failed for hdl 6 / sock 1484
     (SI_ECONN_BROKEN; I4; ST; 127.0.0.1:3765) [nixxi.cpp    4235]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=5660)
ERROR => DpProcKill: kill failed [dpntdisp.c   371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Wed Aug 02 17:49:48 2006
J2EE server info
  start = TRUE
  state = STARTED
  pid = 6372
  argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=3801
  argv[5] = -DSAPSYSTEM=03
  argv[6] = -DSAPSYSTEMNAME=EC1
  argv[7] = -DSAPMYNAME=superjxy_EC1_03
  argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  argv[9] = -DFRFC_FALLBACK=ON
  argv[10] = -DFRFC_FALLBACK_HOST=localhost
  start_lazy = 0
  start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Wed Aug 02 17:51:09 2006
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1468
     (SI_ECONN_BROKEN; I4; ST; 127.0.0.1:3802) [nixxi.cpp    4235]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=6372)
ERROR => DpProcKill: kill failed [dpntdisp.c   371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Wed Aug 02 17:51:28 2006
J2EE server info
  start = TRUE
  state = STARTED
  pid = 7324
  argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=3838
  argv[5] = -DSAPSYSTEM=03
  argv[6] = -DSAPSYSTEMNAME=EC1
  argv[7] = -DSAPMYNAME=superjxy_EC1_03
  argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  argv[9] = -DFRFC_FALLBACK=ON
  argv[10] = -DFRFC_FALLBACK_HOST=localhost
  start_lazy = 0
  start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Wed Aug 02 17:52:49 2006
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
ERROR => NiIRead: SiRecv failed for hdl 6 / sock 1464
     (SI_ECONN_BROKEN; I4; ST; 127.0.0.1:3839) [nixxi.cpp    4235]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=7324)
ERROR => DpProcKill: kill failed [dpntdisp.c   371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Wed Aug 02 17:53:08 2006
J2EE server info
  start = TRUE
  state = STARTED
  pid = 3968
  argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=3884
  argv[5] = -DSAPSYSTEM=03
  argv[6] = -DSAPSYSTEMNAME=EC1
  argv[7] = -DSAPMYNAME=superjxy_EC1_03
  argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  argv[9] = -DFRFC_FALLBACK=ON
  argv[10] = -DFRFC_FALLBACK_HOST=localhost
  start_lazy = 0
  start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Wed Aug 02 17:54:29 2006
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1460
     (SI_ECONN_BROKEN; I4; ST; 127.0.0.1:3885) [nixxi.cpp    4235]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=3968)
ERROR => DpProcKill: kill failed [dpntdisp.c   371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Wed Aug 02 17:54:48 2006
J2EE server info
  start = TRUE
  state = STARTED
  pid = 188
  argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
  argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=3923
  argv[5] = -DSAPSYSTEM=03
  argv[6] = -DSAPSYSTEMNAME=EC1
  argv[7] = -DSAPMYNAME=superjxy_EC1_03
  argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
  argv[9] = -DFRFC_FALLBACK=ON
  argv[10] = -DFRFC_FALLBACK_HOST=localhost
  start_lazy = 0
  start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED

Answer 1

Thank you for your response
Following is std_server0.out file:
stdout/stderr redirect
node name   : server0
pid         : 2764
system name : EC1
system nr.  : 03
started at  : Tue Aug 01 21:39:10 2006
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 4584] MtxInit: -2 0 0
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
SAP J2EE Engine Version 7.00   PatchLevel is starting...
Loading: LogManager ... 1766 ms.
Loading: PoolManager ... 0 ms.
Loading: ApplicationThreadManager ... 312 ms.
Loading: ThreadManager ... 31 ms.
Loading: IpVerificationManager ... 16 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 406 ms.
Loading: LockingManager ... 156 ms.
Loading: ConfigurationManager ... 10313 ms.
Loading: LicensingManager ... 31 ms.
Loading: CacheManager ... 172 ms.
Loading: ServiceManager ...
Loading services.:
  Service runtimeinfo started. (16 ms).
  Service memory started. (250 ms).
  Service timeout started. (250 ms).
  Service cross started. (312 ms).
  Service file started. (937 ms).
  Service trex.service started. (78 ms).
  Service p4 started. (6140 ms).
  Service classpath_resolver started. (281 ms).
  Service cafeucc~api started. (12453 ms).
  Service userstore started. (16 ms).
  Service jmx_notification started. (46 ms).
  Service log_configurator started. (21562 ms).
  Service locking started. (0 ms).
  Service naming started. (969 ms).
  Service ts started. (281 ms).
  Service licensing started. (0 ms).
  Service javamail started. (750 ms).
  Service failover started. (78 ms).
  Service appclient started. (203 ms).
  Service jmsconnector started. (109 ms).
  Service iiop started. (1547 ms).
  Service connector started. (688 ms).
  Service cafeugpmailcf started. (250 ms).
  Service http started. (1250 ms).
  Service webservices started. (1953 ms).
  Service deploy started. (28125 ms).
  Service configuration started. (16 ms).
  Service MigrationService started. (47 ms).
  Service bimmrdeployer started. (47 ms).
  Service dbpool started. (3687 ms).
Aug 1, 2006 9:40:26 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_74] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "     No logon possible (no hw ID received by mssg server)                ". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
  passwd=********
  receiverid=master
  sysnr=$$
  client=001
  poolmaxsize=10
  user=SAPJSF
  receiverid_guest=master
  ashost=localhost
  poolmaxwait=10000
Aug 1, 2006 9:40:26 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_74] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
Aug 1, 2006 9:40:26 PM    com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_74] Fatal:
Aug 1, 2006 9:40:26 PM    com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_74] 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: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
     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:105)
Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!:      No logon possible (no hw ID received by mssg server)               
     at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
     ... 6 more
com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
     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:105)
Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!:      No logon possible (no hw ID received by mssg server)               
     at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
     ... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Aug 1, 2006 9:40:26 PM              com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_74] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
stdout/stderr redirect
node name   : server0
pid         : 2764
system name : EC1
system nr.  : 03
started at  : Tue Aug 01 21:40:31 2006
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 7752] MtxInit: -2 0 0
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
SAP J2EE Engine Version 7.00   PatchLevel is starting...
Loading: LogManager ... 1047 ms.
Loading: PoolManager ... 15 ms.
Loading: ApplicationThreadManager ... 78 ms.
Loading: ThreadManager ... 32 ms.
Loading: IpVerificationManager ... 15 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 390 ms.
Loading: LockingManager ... 79 ms.
Loading: ConfigurationManager ... 8031 ms.
Loading: LicensingManager ... 31 ms.
Loading: CacheManager ... 156 ms.
Loading: ServiceManager ...
Loading services.:
  Service memory started. (47 ms).
  Service cross started. (15 ms).
  Service file started. (219 ms).
  Service trex.service started. (171 ms).
  Service runtimeinfo started. (15 ms).
  Service cafeucc~api started. (16 ms).
  Service timeout started. (16 ms).
  Service userstore started. (0 ms).
  Service jmx_notification started. (203 ms).
  Service p4 started. (610 ms).
  Service classpath_resolver started. (15 ms).
  Service log_configurator started. (6359 ms).
  Service locking started. (16 ms).
  Service http started. (422 ms).
  Service naming started. (515 ms).
  Service failover started. (125 ms).
  Service javamail started. (266 ms).
  Service jmsconnector started. (296 ms).
  Service appclient started. (265 ms).
  Service ts started. (265 ms).
  Service licensing started. (31 ms).
  Service cafeugpmailcf started. (250 ms).
  Service connector started. (406 ms).
  Service iiop started. (547 ms).
  Service webservices started. (765 ms).
  Service deploy started. (14735 ms).
  Service MigrationService started. (47 ms).
  Service bimmrdeployer started. (32 ms).
  Service configuration started. (47 ms).
  Service dbpool started. (3063 ms).
Aug 1, 2006 9:41:11 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_73] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "     No logon possible (no hw ID received by mssg server)                ". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
  passwd=********
  receiverid=master
  sysnr=$$
  client=001
  poolmaxsize=10
  user=SAPJSF
  receiverid_guest=master
  ashost=localhost
  poolmaxwait=10000
Aug 1, 2006 9:41:11 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_73] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
Aug 1, 2006 9:41:11 PM    com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_73] Fatal:
Aug 1, 2006 9:41:11 PM    com.sap.security.core.InternalUMFactory [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: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
     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:105)
Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!:      No logon possible (no hw ID received by mssg server)               
     at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
     ... 6 more
com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
     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:105)
Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!:      No logon possible (no hw ID received by mssg server)               
     at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
     ... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Aug 1, 2006 9:41:11 PM              com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_73] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
stdout/stderr redirect
node name   : server0
pid         : 2764
system name : EC1
system nr.  : 03
started at  : Tue Aug 01 21:41:21 2006
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 2744] MtxInit: -2 0 0
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
SAP J2EE Engine Version 7.00   PatchLevel is starting...
Loading: LogManager ... 594 ms.
Loading: PoolManager ... 16 ms.
Loading: ApplicationThreadManager ... 78 ms.
Loading: ThreadManager ... 31 ms.
Loading: IpVerificationManager ... 31 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 234 ms.
Loading: LockingManager ... 78 ms.
Loading: ConfigurationManager ... 8000 ms.
Loading: LicensingManager ... 32 ms.
Loading: CacheManager ... 343 ms.
Loading: ServiceManager ...
Loading services.:
  Service memory started. (16 ms).
  Service userstore started. (15 ms).
  Service cross started. (16 ms).
  Service file started. (31 ms).
  Service p4 started. (157 ms).
  Service classpath_resolver started. (32 ms).
  Service timeout started. (78 ms).
  Service trex.service started. (63 ms).
  Service cafeucc~api started. (16 ms).
  Service runtimeinfo started. (16 ms).
  Service jmx_notification started. (47 ms).
  Service log_configurator started. (6297 ms).
  Service locking started. (171 ms).
  Service http started. (250 ms).
  Service naming started. (562 ms).
  Service appclient started. (140 ms).
  Service failover started. (188 ms).
  Service jmsconnector started. (266 ms).
  Service javamail started. (328 ms).
  Service ts started. (360 ms).
  Service licensing started. (16 ms).
  Service cafeugpmailcf started. (313 ms).
  Service connector started. (469 ms).
  Service iiop started. (390 ms).
  Service webservices started. (906 ms).
  Service deploy started. (14906 ms).
  Service MigrationService started. (47 ms).
  Service bimmrdeployer started. (15 ms).
  Service configuration started. (32 ms).
  Service dbpool started. (3125 ms).
Aug 1, 2006 9:41:59 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_66] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "     No logon possible (no hw ID received by mssg server)                ". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
  passwd=********
  receiverid=master
  sysnr=$$
  client=001
  poolmaxsize=10
  user=SAPJSF
  receiverid_guest=master
  ashost=localhost
  poolmaxwait=10000
Aug 1, 2006 9:41:59 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_66] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
Aug 1, 2006 9:41:59 PM    com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_66] Fatal:
Aug 1, 2006 9:41:59 PM    com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_66] 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: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
     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.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!:      No logon possible (no hw ID received by mssg server)               
     at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
     ... 6 more
com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
     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.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!:      No logon possible (no hw ID received by mssg server)               
     at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
     ... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Aug 1, 2006 9:41:59 PM              com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_66] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
stdout/stderr redirect
node name   : server0
pid         : 2764
system name : EC1
system nr.  : 03
started at  : Tue Aug 01 21:42:07 2006
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 3696] MtxInit: -2 0 0
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
SAP J2EE Engine Version 7.00   PatchLevel is starting...
Loading: LogManager ... 609 ms.
Loading: PoolManager ... 0 ms.
Loading: ApplicationThreadManager ... 78 ms.
Loading: ThreadManager ... 47 ms.
Loading: IpVerificationManager ... 16 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 250 ms.
Loading: LockingManager ... 78 ms.
Loading: ConfigurationManager ... 8016 ms.
Loading: LicensingManager ... 31 ms.
Loading: CacheManager ... 344 ms.
Loading: ServiceManager ...
Loading services.:
  Service memory started. (16 ms).
  Service cross started. (15 ms).
  Service file started. (110 ms).
  Service userstore started. (0 ms).
  Service timeout started. (78 ms).
  Service runtimeinfo started. (0 ms).
  Service p4 started. (203 ms).
  Service classpath_resolver started. (31 ms).
  Service cafeucc~api started. (15 ms).
  Service trex.service started. (141 ms).
  Service jmx_notification started. (78 ms).
  Service log_configurator started. (6985 ms).
  Service locking started. (0 ms).
  Service http started. (500 ms).
  Service naming started. (703 ms).
  Service failover started. (141 ms).
  Service appclient started. (484 ms).
  Service javamail started. (515 ms).
  Service ts started. (469 ms).
  Service jmsconnector started. (750 ms).
  Service licensing started. (32 ms).
  Service connector started. (844 ms).
  Service cafeugpmailcf started. (594 ms).
  Service webservices started. (1000 ms).
  Service iiop started. (625 ms).
  Service deploy started. (15016 ms).
  Service MigrationService started. (47 ms).
  Service configuration started. (47 ms).
  Service bimmrdeployer started. (46 ms).
  Service dbpool started. (2953 ms).
Aug 1, 2006 9:42:44 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_79] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "     No logon possible (no hw ID received by mssg server)                ". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
  passwd=********
  receiverid=master
  sysnr=$$
  client=001
  poolmaxsize=10
  user=SAPJSF
  receiverid_guest=master
  ashost=localhost
  poolmaxwait=10000
Aug 1, 2006 9:42:44 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_79] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
Aug 1, 2006 9:42:44 PM    com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_79] Fatal:
Aug 1, 2006 9:42:44 PM    com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_79] 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: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
     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:105)
Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!:      No logon possible (no hw ID received by mssg server)               
     at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
     ... 6 more
com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
     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:105)
Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!:      No logon possible (no hw ID received by mssg server)               
     at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
     ... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Aug 1, 2006 9:42:44 PM              com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_79] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.