Server 0 can't start

Former Member · ‎02-12-2008

We are having a problem regarding XI, the server 0 can't start. There is an error code which is error(-11113). Here is the log. Kindly advice -Thank you-

Line:-----

-

trc file: "C:\usr\sap\XI1\DVEBMGS01\work\dev_server0", trc level: 1, release: "640"

-

node name : ID18282050

pid : 36144

system name : XI1

system nr. : 01

started at : Mon Feb 11 16:47:49 2008

arguments :

arg[00] : C:\usr\sap\XI1\DVEBMGS01/j2ee/os_libs/jlaunch.exe

arg[01] : pf=C:\usr\sap\XI1\SYS\profile\XI1_DVEBMGS01_MDCSAP03

arg[02] : -DSAPINFO=XI1_01_server

arg[03] : pf=C:\usr\sap\XI1\SYS\profile\XI1_DVEBMGS01_MDCSAP03

arg[04] : -DSAPSTART=1

arg[05] : -DCONNECT_PORT=2585

arg[06] : -DLISTEN_PORT=2583

arg[07] : -DSAPSYSTEM=01

arg[08] : -DSAPSYSTEMNAME=XI1

arg[09] : -DSAPMYNAME=MDCSAP03_XI1_01

arg[10] : -DSAPPROFILE=C:\usr\sap\XI1\SYS\profile\XI1_DVEBMGS01_MDCSAP03

arg[11] : -DFRFC_FALLBACK=ON

arg[12] : -DFRFC_FALLBACK_HOST=localhost

[Thr 35052] Mon Feb 11 16:47:49 2008

[Thr 35052] INFO: Unknown property [box.number=XI1DVEBMGS01mdcsap03]

[Thr 35052] INFO: Unknown property [ms.host=mdcsap03]

[Thr 35052] INFO: Unknown property [ms.port=3631]

[Thr 35052] INFO: Unknown property [system.id=1]

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

JStartupReadInstanceProperties: read instance properties [C:\usr\sap\XI1\DVEBMGS01\j2ee\cluster\instance.properties]

-> ms host : mdcsap03

-> ms port : 3631

-> OS libs : C:\usr\sap\XI1\DVEBMGS01\j2ee\os_libs

-> Admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

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

Used property files

-> files [00] : C:\usr\sap\XI1\DVEBMGS01\j2ee\cluster\instance.properties

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

Instance properties

-> ms host : mdcsap03

-> ms port : 3631

-> os libs : C:\usr\sap\XI1\DVEBMGS01\j2ee\os_libs

-> admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

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

Bootstrap nodes

-> [00] bootstrap : C:\usr\sap\XI1\DVEBMGS01\j2ee\cluster\instance.properties

-> [01] bootstrap_ID18282000 : C:\usr\sap\XI1\DVEBMGS01\j2ee\cluster\instance.properties

-> [02] bootstrap_ID18282050 : C:\usr\sap\XI1\DVEBMGS01\j2ee\cluster\instance.properties

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

Worker nodes

-> [00] ID18282000 : C:\usr\sap\XI1\DVEBMGS01\j2ee\cluster\instance.properties

-> [01] ID18282050 : C:\usr\sap\XI1\DVEBMGS01\j2ee\cluster\instance.properties

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

[Thr 35052] JLaunchRequestQueueInit: create named pipe for ipc

[Thr 35052] JLaunchRequestQueueInit: create pipe listener thread

[Thr 44156] JLaunchRequestFunc: Thread 44156 started as listener thread for np messages.

[Thr 28552] WaitSyncSemThread: Thread 28552 started as semaphore monitor thread.

[Thr 35052] NiInit2: NI already initialized; param 'maxHandles' ignored

[Thr 35052] INFO: Unknown property [JLaunchParameters=]

[Thr 35052] [Node: server0] java home is set by profile parameter

Java Home: C:\j2sdk1.4.2_13

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

JStartupIReadSection: read node properties [ID18282050]

-> node name : server0

-> node type : server

-> node execute : yes

-> java path : C:\j2sdk1.4.2_13

-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Dsun.io.useCanonCaches=false -XX:NewSize=42m -XX:MaxNewSize=42m -XX:MaxPermSize=192m -Djava.awt.headless=true -XX:PermSize=192m -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc -XX:DisableExplicitGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:UseParNewGC -Drdbms.driverLocation=C:/oracle/SM1/102/jdbc/lib/classes12.jar -Dsys.global.dir=C:/usr/sap/XI1/SYS/global/

-> java vm version : 1.4.2_13-b06

-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)

-> java vm type : server

-> java vm cpu : x86

-> heap size : 512M

-> init heap size : 512M

-> root path : C:\usr\sap\XI1\DVEBMGS01\j2ee\cluster\server0

-> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.

-> OS libs path : C:\usr\sap\XI1\DVEBMGS01\j2ee\os_libs

-> main class : com.sap.engine.boot.Start

-> framework class : com.sap.bc.proj.jstartup.JStartupFramework

-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives

-> framework path : C:\usr\sap\XI1\DVEBMGS01\j2ee\os_libs\jstartup.jar

-> shutdown class : com.sap.engine.boot.Start

-> parameters :

-> debuggable : no

-> debug mode : no

-> debug port : 50121

-> shutdown timeout: 120000

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

[Thr 35052] JLaunchISetDebugMode: set debug mode [no]

[Thr 46248] JLaunchIStartFunc: Thread 46248 started as Java VM thread.

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

JHVM_LoadJavaVM: VM Arguments of node [server0]

-> stack : 262144 Bytes

-> arg[ 0]: exit

-> arg[ 1]: abort

-> arg[ 2]: -Djava.security.policy=./java.policy

-> arg[ 3]: -Djava.security.egd=file:/dev/urandom

-> arg[ 4]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy

-> arg[ 5]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy

-> arg[ 6]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy

-> arg[ 7]: -Djco.jarm=1

-> arg[ 8]: -Dsun.io.useCanonCaches=false

-> arg[ 9]: -XX:NewSize=42m

-> arg[ 10]: -XX:MaxNewSize=42m

-> arg[ 11]: -XX:MaxPermSize=192m

-> arg[ 12]: -Djava.awt.headless=true

-> arg[ 13]: -XX:PermSize=192m

-> arg[ 14]: -XX:SurvivorRatio=2

-> arg[ 15]: -XX:TargetSurvivorRatio=90

-> arg[ 16]: -XX:SoftRefLRUPolicyMSPerMB=1

-> arg[ 17]: -verbose:gc

-> arg[ 18]: -XX:+DisableExplicitGC

-> arg[ 19]: -XX:+PrintGCDetails

-> arg[ 20]: -XX:+PrintGCTimeStamps

-> arg[ 21]: -XX:+UseParNewGC

-> arg[ 22]: -Drdbms.driverLocation=C:/oracle/SM1/102/jdbc/lib/classes12.jar

-> arg[ 23]: -Dsys.global.dir=C:/usr/sap/XI1/SYS/global/

-> arg[ 24]: -Dsys.global.dir=C:\usr\sap\XI1\SYS\global

-> arg[ 25]: -Dapplication.home=C:\usr\sap\XI1\DVEBMGS01\j2ee\os_libs

-> arg[ 26]: -Djava.class.path=C:\usr\sap\XI1\DVEBMGS01\j2ee\os_libs\jstartup.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.

-> arg[ 27]: -Djava.library.path=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;C:\j2sdk1.4.2_13\bin;C:\usr\sap\XI1\DVEBMGS01\j2ee\os_libs;C:\oracle\XI1\102\bin;C:\oracle\SM1\102\bin;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\Program Files\Windows Resource Kits\Tools\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\oracle\SM1\102\jre\1.4.2\bin;C:\Program Files\Dell\SysMgt\oma\bin;C:\usr\sap\XI1\SYS\exe\run

-> arg[ 28]: -Dmemory.manager=512M

-> arg[ 29]: -Xmx512M

-> arg[ 30]: -Xms512M

-> arg[ 31]: -DLoadBalanceRestricted=no

-> arg[ 32]: -Djstartup.mode=JCONTROL

-> arg[ 33]: -Djstartup.ownProcessId=36144

-> arg[ 34]: -Djstartup.ownHardwareId=P0676210680

-> arg[ 35]: -Djstartup.whoami=server

-> arg[ 36]: -Djstartup.debuggable=no

-> arg[ 37]: -DSAPINFO=XI1_01_server

-> arg[ 38]: -DSAPSTART=1

-> arg[ 39]: -DCONNECT_PORT=2585

-> arg[ 40]: -DLISTEN_PORT=2583

-> arg[ 41]: -DSAPSYSTEM=01

-> arg[ 42]: -DSAPSYSTEMNAME=XI1

-> arg[ 43]: -DSAPMYNAME=MDCSAP03_XI1_01

-> arg[ 44]: -DSAPPROFILE=C:\usr\sap\XI1\SYS\profile\XI1_DVEBMGS01_MDCSAP03

-> arg[ 45]: -DFRFC_FALLBACK=ON

-> arg[ 46]: -DFRFC_FALLBACK_HOST=localhost

-> arg[ 47]: -DSAPSTARTUP=1

-> arg[ 48]: -DSAPSYSTEM=01

-> arg[ 49]: -DSAPSYSTEMNAME=XI1

-> arg[ 50]: -DSAPMYNAME=MDCSAP03_XI1_01

-> arg[ 51]: -DSAPDBHOST=MDCSAP03

-> arg[ 52]: -Dj2ee.dbhost=mdcsap03

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

[Thr 46248] JHVM_LoadJavaVM: Java VM created OK.

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

JHVM_BuildArgumentList: main method arguments of node [server0]

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

[Thr 42680] Mon Feb 11 16:47:51 2008

[Thr 42680] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework

[Thr 42680] JLaunchISetClusterId: set cluster id 18282050

[Thr 42680] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]

[Thr 42680] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]

[Thr 40544] Mon Feb 11 16:48:20 2008

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

[Thr 40544] **********************************************************************

ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 940893 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.

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

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

Former Member · ‎02-15-2008

Hello,

Here is the log from defaulttrace.trc. Kindly advice.

java.sql.SQLException: Io exception: Software caused connection abort: socket write error

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:111)

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:145)

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:254)

at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:976)

at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1059)

at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:838)

at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1131)

at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3315)

at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3360)

at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeQuery(BasicPreparedStatement.java:97)

at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:270)

at com.sap.sql.jdbc.common.CommonPreparedStatement.executeQuery(CommonPreparedStatement.java:252)

at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:235)

at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.populatePrincipalDatabag(DataBasePersistence.java:2257)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.populatePrincipalDatabagAttribute(PrincipalDatabagFactoryInstance.java:2265)

at com.sap.security.core.imp.AbstractPrincipal.getPrincipalDatabagValues(AbstractPrincipal.java:1895)

at com.sap.security.core.imp.AbstractPrincipal.getAttribute(AbstractPrincipal.java:245)

at com.sap.security.core.role.imp.PermissionRoles.addAction(PermissionRoles.java:46)

at com.sap.security.core.role.imp.PermissionRoles.createDefaultRoles(PermissionRoles.java:401)

at com.sap.security.core.role.imp.PermissionRoles.createDefaultRoles(PermissionRoles.java:317)

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

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)

#

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

Former Member · ‎02-15-2008

Hello,

the logs below is the std_server0.out, Please advice.

-

stdout/stderr redirect

-

node name : server0

pid : 42668

system name : XI1

system nr. : 01

started at : Fri Feb 15 09:22:13 2008

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

CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue

CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode

CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode

CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto

SAP J2EE Engine Version 6.40 PatchLevel 106831.313 is starting...

Loading: LogManager ... 765 ms.

Loading: PoolManager ... 16 ms.

Loading: ApplicationThreadManager ... 94 ms.

Loading: ThreadManager ... 31 ms.

Loading: IpVerificationManager ... 15 ms.

Loading: ClassLoaderManager ... 32 ms.

Loading: ClusterManager ... 312 ms.

Loading: LockingManager ... 2203 ms.

Loading: ConfigurationManager ... 5.193: [GC 5.193: [ParNew: 21503K->1461K(32256K), 0.0098085 secs] 21503K->1461K(513536K), 0.0098682 secs]

2657 ms.

Loading: LicensingManager ... 46 ms.

Loading: ServiceManager ...

8.103: [GC 8.103: [ParNew: 22965K->2410K(32256K), 0.0090291 secs] 22965K->2410K(513536K), 0.0090875 secs]

11.969: [GC 11.969: [ParNew: 23914K->4868K(32256K), 0.0244303 secs] 23914K->4868K(513536K), 0.0244910 secs]

Loading services.:

Service runtimeinfo started. (31 ms).

Service cross started. (31 ms).

Service file started. (47 ms).

Service memory started. (47 ms).

Service timeout started. (31 ms).

Service trex.service started. (47 ms).

Service p4 started. (234 ms).

Service userstore started. (15 ms).

Service jmx_notification started. (31 ms).

Service classpath_resolver started. (16 ms).

13.766: [GC 13.766: [ParNew: 26372K->6399K(32256K), 0.0202103 secs] 26372K->6399K(513536K), 0.0202718 secs]

14.587: [GC 14.587: [ParNew: 27894K->7339K(32256K), 0.0212100 secs] 27894K->7339K(513536K), 0.0212853 secs]

15.294: [GC 15.295: [ParNew: 28843K->7896K(32256K), 0.0224654 secs] 28843K->7896K(513536K), 0.0225384 secs]

16.064: [GC 16.064: [ParNew: 29400K->7894K(32256K), 0.0155209 secs] 29400K->7894K(513536K), 0.0155894 secs]

16.954: [GC 16.955: [ParNew: 29398K->7942K(32256K), 0.0159458 secs] 29398K->7942K(513536K), 0.0160082 secs]

17.680: [GC 17.680: [ParNew: 29446K->8551K(32256K), 0.0147370 secs] 29446K->8551K(513536K), 0.0147975 secs]

18.193: [GC 18.193: [ParNew: 30055K->9531K(32256K), 0.0181741 secs] 30055K->9531K(513536K), 0.0182339 secs]

18.623: [GC 18.623: [ParNew: 31035K->9711K(32256K), 0.0184781 secs] 31035K->9711K(513536K), 0.0185456 secs]

Service log_configurator started. (5938 ms).

Service locking started. (0 ms).

19.258: [GC 19.259: [ParNew: 31215K->10363K(32256K), 0.0186569 secs] 31215K->10363K(513536K), 0.0187168 secs]

Service http started. (250 ms).

Service naming started. (344 ms).

Service failover started. (62 ms).

Service javamail started. (93 ms).

Service appclient started. (94 ms).

Service ts started. (109 ms).

Service licensing started. (16 ms).

Service jmsconnector started. (140 ms).

Service connector started. (250 ms).

Service webservices started. (500 ms).

21.033: [GC 21.033: [ParNew: 31867K->10017K(32256K), 0.0219053 secs] 31867K->11322K(513536K), 0.0219663 secs]

Service deploy started. (10438 ms).

Service configuration started. (47 ms).

Service MobileArchiveContainer started. (47 ms).

Service MobileSetupGeneration started. (234 ms).

24.527: [GC 24.527: [ParNew: 31521K->10752K(32256K), 0.0245336 secs] 32826K->13227K(513536K), 0.0245938 secs]

Service dbpool started. (1453 ms).

Feb 15, 2008 9:22:40 AM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_59] Fatal: Initialization of UME persistence adapter "PRIVATE_DATASOURCE" failed.

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: ConnectionFactory "SAP/BC_UME" does not exist. Possible reasons: the connector in which ConnectionFactory "SAP/BC_UME" is defined is not deployed or not started.

ume.db.connection_pool_type=SAP/BC_UME

ume.db.connection_pool.j2ee.xatransactions_used=FALSE

ume.db.connection_pool.j2ee.is_unicode=FALSE

ume.db.connection_pool.j2ee.oracle_native_driver_used=false: ConnectionFactory "SAP/BC_UME" does not exist. Possible reasons: the connector in which ConnectionFactory "SAP/BC_UME" is defined is not deployed or not started.

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

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: ConnectionFactory "SAP/BC_UME" does not exist. Possible reasons: the connector in which ConnectionFactory "SAP/BC_UME" is defined is not deployed or not started.

ume.db.connection_pool_type=SAP/BC_UME

ume.db.connection_pool.j2ee.xatransactions_used=FALSE

ume.db.connection_pool.j2ee.is_unicode=FALSE

ume.db.connection_pool.j2ee.oracle_native_driver_used=false: ConnectionFactory "SAP/BC_UME" does not exist. Possible reasons: the connector in which ConnectionFactory "SAP/BC_UME" is defined is not deployed or not started.

at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:698)

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

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

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

... 6 more

com.sap.engine.frame.ServiceException: ConnectionFactory "SAP/BC_UME" does not exist. Possible reasons: the connector in which ConnectionFactory "SAP/BC_UME" is defined is not deployed or not started.

ume.db.connection_pool_type=SAP/BC_UME

ume.db.connection_pool.j2ee.xatransactions_used=FALSE

ume.db.connection_pool.j2ee.is_unicode=FALSE

ume.db.connection_pool.j2ee.oracle_native_driver_used=false: ConnectionFactory "SAP/BC_UME" does not exist. Possible reasons: the connector in which ConnectionFactory "SAP/BC_UME" is defined is not deployed or not started.

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

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: ConnectionFactory "SAP/BC_UME" does not exist. Possible reasons: the connector in which ConnectionFactory "SAP/BC_UME" is defined is not deployed or not started.

ume.db.connection_pool_type=SAP/BC_UME

ume.db.connection_pool.j2ee.xatransactions_used=FALSE

ume.db.connection_pool.j2ee.is_unicode=FALSE

ume.db.connection_pool.j2ee.oracle_native_driver_used=false: ConnectionFactory "SAP/BC_UME" does not exist. Possible reasons: the connector in which ConnectionFactory "SAP/BC_UME" is defined is not deployed or not started.

at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:698)

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

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

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

... 6 more

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

Feb 15, 2008 9:22:40 AM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_59] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Reserved 1610612736 (0x60000000) bytes before loading DLLs.

Former Member · ‎02-12-2008

-11113 occurs when services timeout causing j2ee engine to not start successfully.

Please check std_server0.out and look for exceptions, paste the same here.

Could you please also check defaultrace.trc from server0\log directory and see for any major exceptions there. Could you paste the excerpt of the defaultrace file during the j2ee restart.

Regards,

Snehal

Edited by: Snehal Bhaidasna on Feb 12, 2008 12:48 PM

Former Member · ‎02-12-2008

Hi Jezie,

Here are few threads on similar issue

Hope it will be useful.

-Pinkle

Server 0 can't start

Accepted Solutions (0)

Answers (4)

Answers (4)

Why html_repo_runtime is added in the resources se...

Re: Deploy Fiori Freestyle App to Cloud Foundry - ...

Re: SAP BO 4.3 Cloud: Error - The document has bee...

Re: How to get the FIRST Date in a date column

Re: SAP Cloud ALM - Granular Authorization to Scop...