cancel
Showing results for 
Search instead for 
Did you mean: 

server0 is not starting

Former Member
0 Kudos

Hai all,

We got CRM Central instance and 2 CRM application servers.

Central instance started successfully and one of the application server also started successfully.The java process- server0 of the second application server is not getting started,the ABAP of the second server is started.

This the std_server0.log-

-


stdout/stderr redirect

-


node name : server0

pid : 5552

system name : CM4

system nr. : 30

started at : Fri Mar 28 18:21:14 2008

[Thr 5912] 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 ... 359 ms.

Loading: PoolManager ... 0 ms.

Loading: ApplicationThreadManager ... 62 ms.

Loading: ThreadManager ... 16 ms.

Loading: IpVerificationManager ... 15 ms.

Loading: ClassLoaderManager ... 16 ms.

Loading: ClusterManager ... 156 ms.

Loading: LockingManager ... 63 ms.

Loading: ConfigurationManager ... 1297 ms.

Loading: LicensingManager ... 15 ms.

Loading: CacheManager ... 125 ms.

Loading: ServiceManager ...

4.277: [ParNew 87040K->7166K(1005056K), 0.0165237 secs]

Loading services.:

Service runtimeinfo started. (32 ms).

Service cross started. (32 ms).

Service file started. (47 ms).

Service memory started. (47 ms).

Service timeout started. (32 ms).

Service trex.service started. (47 ms).

Service cafeucc~api started. (63 ms).

Service userstore started. (15 ms).

Service jmx_notification started. (15 ms).

Service p4 started. (94 ms).

Service classpath_resolver started. (16 ms).

7.165: [ParNew 94206K->13679K(1005056K), 0.0234405 secs]

9.033: [ParNew 100719K->20813K(1005056K), 0.0326975 secs]

Service log_configurator started. (3125 ms).

Service locking started. (0 ms).

Service http started. (156 ms).

Service naming started. (250 ms).

Service failover started. (31 ms).

Service appclient started. (62 ms).

Service jmsconnector started. (78 ms).

Service javamail started. (78 ms).

Service ts started. (78 ms).

Service licensing started. (0 ms).

Service cafeugpmailcf started. (78 ms).

Service connector started. (140 ms).

Service iiop started. (125 ms).

Service webservices started. (391 ms).

9.873: [ParNew 107853K->19937K(1005056K), 0.0192870 secs]

Service deploy started. (11407 ms).

Service configuration started. (16 ms).

Service MigrationService started. (31 ms).

Service bimmrdeployer started. (0 ms).

17.989: [ParNew 106977K->27448K(1005056K), 0.0261789 secs]

Service dbpool started. (82658 ms).

Mar 28, 2008 6:22:56 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_61] Fatal: Initialization of UME persistence adapter "PRIVATE_DATASOURCE" failed.

Mar 28, 2008 6:22:56 PM com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_61] Fatal:

Mar 28, 2008 6:22:56 PM com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_61] 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'!: null

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: (No text available)

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'!: null

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: (No text available)

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.

Mar 28, 2008 6:22:56 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_61] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Any ideas!!!!!!!!!!!!!!!!!!!!

Thanks and Regards,

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

What was the result of shutting down the App server 1 and the starting App-server2.

Check if you have enough Disk space in the Central Instance?

Check if ports are being used

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

Your UME Initialization is failed? did you make any changes in data source? like PRIVATE_DATASOURCE it's looking

Chek this com.sap.security.core.server.ume.service properties

Regards,

Hari.

Former Member
0 Kudos

Hi Venkat,

Try and down the first App. Server and start only the Second App Server.

Let me know the result, so that we can analyse it further.