server0 is not starting

[Former Member]

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: http://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 caf_eucc~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: http://ParNew 94206K->13679K(1005056K), 0.0234405 secs

9.033: http://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 caf_eugp_mailcf started. (78 ms).

Service connector started. (140 ms).

Service iiop started. (125 ms).

Service webservices started. (391 ms).

9.873: http://ParNew 107853K->19937K(1005056K), 0.0192870 secs

Service deploy started. (11407 ms).

Service configuration started. (16 ms).

Service MigrationService started. (31 ms).

Service bi_mmrdeployer started. (0 ms).

17.989: http://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_Threadimpl: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_Threadimpl:5]_61 Fatal:

Mar 28, 2008 6:22:56 PM com.sap.security.core.InternalUMFactory [SAPEngine_System_Threadimpl: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_Threadimpl: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,

[Former Member]

Check your Diskspace in Central Instance under c:\usr\sap\<sid>

[Former Member]

Venkata,

I am looking at the start of your process and overall - your Java app-server - the node name is somewhat interesting since the central instance Java Installation should be named Server0 and the dialog instance is also called Server0 - so just checking to make sure. When you installed the Java Instance on the App-Server, did you install it as a Java dialog instance or Java central instance? There is a difference when the SID is shared with the ABAP and Java Stacks and there is an expectation that there be only one persistence node per SID (Central Java Instance).

Edited by: David Milliken on Apr 1, 2008 11:29 PM

[Former Member]

Could you please check DBPOOL property "sysDS.aliases" in config tool. Sometimes it might have been messed up. Set it to default and then give a complete restart.

Kindly reward points in-case you find this useful.

Rgds,

KINO

[Former Member]

There should be a corresponding exception related to UME in defaultrace.trc under server0\log. That usually has more details.

Please paste it here.

Regards,

Snehal

[TomCenens]

This error is often seen as you update one of the J2EE engine components but you have not updated a linked component (which has to have the same version).

Please verify your component versions (J2EE stack) and update them where neccesary.

[jochen_rundholz]

This can happen for example if parameters ume.logon.security_policy.* are not set correctly. Just a guess but may be worth to check.

the other thing I can think of is that you might have some kind of DNS or network problem since other j2ee instances can start.

Regards,

Jochen

[JPReyes]

As far as i can see this is an error regarding the configuration of the UME

"Initialization of UME persistence adapter "PRIVATE_DATASOURCE" failed."

"Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started."

Theres omething wrong with the DATASOURCE file configuration

Regards

Juan

[Former Member]

Hai,

The DATASOURCE file configuration is same for 2 application servers.One of the application server is started successfully,but the other server is still giving the same error...

Any other ideas!!!!!!!!!!!!!!

Thanks and Regards,

[enginimaldb]

Hi Venkata,

the UME SDA´s can be inconsistent. Please redeploy them as per note: 942050

Regards

Eimal

[Former Member]

Hi Venkata,

It seems on central instance and one of the application instance your JAVA is running.

On the instance where JAVA stack is not starting (server0) check the parameters in visual admin. If you have specified the correct the hostname, Instanc number etc.

Best Wishes.

[Former Member]

Hi Venkata,

Possibly, SAPJSF user has been lock or you changed its password through configtool UME configuration.

Best regards,

Orkun

[Former Member]

Hi. Check the user SAPJSF on your system is locked or not chek the password of this user. Also can you login in ABAP stack ? Regards.

[Former Member]

Hai,

The SAPJSF user is not locked and i can login into ABAP stack also.Even i can able to start the CRM central instance and one Application server also.....

Thanks and Regards,

[Former Member]

Are you create any upgrade with JSPM or other upgrade tool ? If yes read the note 942050, if not go to sm21 on abap stack and chek if any error exist. After this the error are coming? What did you change recently? More information.

Regards.