J2EE engine not getting started

Hi All,
My J2ee engine isnt getting started. When i check the logs, i see the following error,
Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
Loading: LogManager ... 672 ms.
Loading: PoolManager ... 0 ms.
Loading: ApplicationThreadManager ... 78 ms.
Loading: ThreadManager ... 31 ms.
Loading: IpVerificationManager ... 0 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 218 ms.
Loading: LockingManager ... 94 ms.
Loading: ConfigurationManager ...
Loading: ConfigurationManager returned false!
Kernel not loaded. System halted.
Can anybody help me out with this ??
Thanks in advance,
Pranav

Hi Arun,
ya indeed it looks like a DB connection problem. When i check the logs i see the following error :
#1.5#001321D5DC2000000000001500049EDC0004163FAB8F0C2D#1150362623876#com.sap.engine.core.configuration##com.sap.engine.core.configuration#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Error while connecting to DB.
=======================================================
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
     at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:360)
     at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:125)
     at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
     at</i></i> com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
     at com.sap.engine.core.configuration.impl.ConfigurationHandlerFactoryImpl.<init>(ConfigurationHandlerFactoryImpl.java:30)
     at com.sap.engine.core.configuration.impl0.ConfigurationManagerImpl.initInternal(ConfigurationManagerImpl.java:189)
     at com.sap.engine.core.configuration.AbstractConfigurationManagerImpl.init(AbstractConfigurationManagerImpl.java:169)
     at com.sap.engine.core.Framework.loadSingleManager(Framework.java:560)
     at com.sap.engine.core.Framework.loadManagers(Framework.java:254)
     at com.sap.engine.core.Framework.start(Framework.java:188)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.boot.FrameThread.run(FrameThread.java:61)
     at java.lang.Thread.run(Thread.java:534)
Caused by: java.sql.SQLException: [SAP_NWMss][SQLServer JDBC Driver][SQLServer]Login failed for user 'SAPBQ3DB'. The user is not associated with a trusted SQL Server connection.
     at com.sap.nwmss.jdbc.base.BaseExceptions.createException(Unknown Source)
     at com.sap.nwmss.jdbc.base.BaseExceptions.getException(Unknown Source)
     at com.sap.nwmss.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
     at com.sap.nwmss.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
     at com.sap.nwmss.jdbc.sqlserver.tds.TDSLoginRequest.processReplyToken(Unknown Source)
     at com.sap.nwmss.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
     at com.sap.nwmss.jdbc.sqlserver.tds.TDSLoginRequest.submitRequest(Unknown Source)
     at com.sap.nwmss.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
     at com.sap.nwmss.jdbc.base.BaseConnection.connect(Unknown Source)
     at com.sap.nwmss.jdbc.base.BaseConnection.setupImplConnection(Unknown Source)
     at com.sap.nwmss.jdbc.base.BaseConnection.open(Unknown Source)
     at com.sap.nwmss.jdbc.base.BaseDriver.connect(Unknown Source)
     at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:219)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:579)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:263)
Actually i've upgraded my SQL Server2000 DB to SQL Server 2005, i suspect that causes the problem. Would be great if somebody can provide me any further clues..
Regards,
Pranav

Similar Messages

  • J2EE application not getting started.

    Hi there,
    I have depoyed my J2EE application successfully but it is not getting started, below is the log trace that is being shown.
    My java path seems fine but cudn't get to know why the initializing is failing.
    Favour would be definitely appreciated.
    One Observation is, WAR file seems like not got deployed properly even though at the time of deployment every acknowledgement message shown was fine.
    **My version is Oracle Weblogic 11g (10.3.0) on IBM AIX 64-bit 6.1 power series system.**
    **JDK used is 1.6.0**
    BEA-149231:
    *Unable to set the activation state to true for the application 'SAMPLEAPP1'. weblogic.application.ModuleException: [HTTP:101216]Servlet: "BranchController" failed to preload on startup in Web application: "FCJNeoWeb". java.lang.ExceptionInInitializerError at java.lang.J9VMInternals.initialize(J9VMInternals.java:222) at com.ofss.infra.controller.BranchController.init(BranchController.java:118) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1893) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1870) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1790) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184) at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361) at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51) at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196) at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30) at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233) at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169) at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123) at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173) at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89) at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) Caused by: java.lang.NumberFormatException: null at java.lang.Throwable.<init>(Throwable.java:67) at java.lang.Integer.parseInt(Integer.java:428) at java.lang.Integer.parseInt(Integer.java:511) at com.ofss.fcc.common.BranchConstants.<clinit>(BranchConstants.java:88) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(J9VMInternals.java:200) ... 43 more at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184) at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361) at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51) at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196) at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30) at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233) at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169) at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123) at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173) at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89) at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.NumberFormatException: null at java.lang.Throwable.<init>(Throwable.java:67) at java.lang.Integer.parseInt(Integer.java:428) at java.lang.Integer.parseInt(Integer.java:511) at com.ofss.fcc.common.BranchConstants.<clinit>(BranchConstants.java:88) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(J9VMInternals.java:200) at com.ofss.infra.controller.BranchController.init(BranchController.java:118) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1893) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1870) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1790) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184) at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361) at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51) at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196) at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30) at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233) at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169) at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123) at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173) at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89) at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)*
    Cheers.. PCZ

    with the same problem but with weblogic, i tried this solution but i still get this error
    Exception:
    [HTTP:101216]Servlet: "BranchController" failed to preload on startup in Web application: "FCJNeoWeb". java.lang.ExceptionInInitializerError at com.ofss.infra.controller.BranchController.init(BranchController.java:122) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3046) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:463) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1269) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116) at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:143) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) Caused by: java.lang.NumberFormatException: null at java.lang.Integer.parseInt(Integer.java:417) at java.lang.Integer.parseInt(Integer.java:499) at com.ofss.fcc.common.BranchConstants.<clinit>(BranchConstants.java:92) at com.ofss.infra.controller.BranchController.init(BranchController.java:122) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116) at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:143) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67) ... 3 more
    and my deployment state is failed

  • J2EE server not getting started.....NO Activeuserstore is set...

    Hi,
    I have installed NW2004s.After patch installtion, when I tried to start my server, the Java Instance(server0) is not getting started.I saw postings in SDN but i couldnt find any helpful answers,now again posting it because i think  anyone of u might have solved it.Could u please tell me what is the solution, as I have to finish it before EOD and I ve to run my scenarios..I have a demo tomorrow.Waiting for ur reply.
    It is saying "No Activeuserstore is set"...
    Replies will be highly "appreciated".
    Expecting replies,
    Manikandan Rajendran
    Message was edited by: manikandan rajendran

    Hi Manikandan,
    I'm not sure waht the problem is but check this.
    http://help.sap.com/saphelp_nw04/helpdata/en/57/ef429d748ba84f83d9a6800c8cf252/frameset.htm
    Hope this help!
    Juan
    PS: don't forget to reward if helpful

  • Deployment while the J2EE Engine not getting Connected

    Hello Group,
    Versions : EP6.0 SP14, WAS 6.4 AND NWDS 2.0.9
    I'm new to WD and developed a Welcomecomponent
    and deploying the component using J2EE Engine and given the settings as follows..
    in NWDS -> WINDOWS-> PREFERENCES->SAP Engine Installed on Remote Host->
    Message Server Host: sapep.xxxx.com
    Message Server Port:52100
    and applied all the changes at the time i got a error message "<b>Deployment Aborted</b>"
    The Error Message as follows:
    <b>Dec 8, 2005 12:08:49 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [001]Deployment aborted
    Deployment exception : Cannot determine sdm host (is empty). Please configure your engine/sdm correctly !</b>
    I will apreciate how will let us give mea reply for this
    Thanks in advance also
    Sreedhar

    Hello Deban,
    Thanx for u r reply.,
    My settings Like this:
    sapplm.xxxx.com
    3621
    And i made sapmsI21 3621/tcp entry in my host file also
    and i started the SDM aslo and i refreshed J2EE Engine many times but it's still Depolyment Aborted.
    <b>"Deployment exception : Cannot determine sdm host (is empty). Please configure your engine/sdm correctly "</b>
    Thanks in advance
    Bye

  • J2EE Server is not getting started exit code -11113

    Hi,
    J2EE Server is not getting started, the exit code is -11113. When I tried to start J2EE Enginer Visual Administrator its giving below error.
    Unable to lookup connection default.
    https://SAPXI:8101/msgserver/text/logon returned empty list of connection parameters.
    Please help.
    Thanks,
    Nishant

    Go to the following directory.
    /usr/sap/<SAPSID>/<Instance_Name>/j2ee/admin
    and start the go.bat.
    Java Add-In You cannot use the Default login. Instead, perform the following steps:
    a) Choose New.
    b) Enter a display name and choose Direct Connection to a dispatcher Node.
    c) Choose Next.
    d) Enter at least the following:
    ■ User Name: J2EE_ADMIN
    ■ Host: <host_name> of the J2EE engine
    ■ Port: <P4_Port>
    The following convention applies for the port:
    5<Instance_Number_of_SAP_J2EE_Engine>04. For example, if
    your J2EE instance number is 15, the P4port is 51504.
    e) Choose Save and connect with your new login account by choosing
    Connect.
    f) Enter the password for the J2EE_ADMIN user and choose Connect.

  • Java engine (server0 process) not getting started.

    Hi All,
    I am not able to start java engine. Y'day I changed the password of SAPJSF user in portal side. Server0 process is not getting started from y'day. Error message is like below. Can any one help me in this area?
    =====================================================================================
    com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Name or password is incorrect (repeat logon)
            at com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo640Proxy$Client640.getAttributes(R3JCo640Proxy.java:408)
            at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.doInitRfc(R3PersistenceBase.java:689)
            at com.sap.security.core.persistence.datasource.imp.R3Persistence.localInitialization(R3Persistence.java:277)
            at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:424)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:363)
            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:222)
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:286)
            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)
    =====================================================================================
    Thanks & Regards,
    Charanjit Singh.

    Hi Anil,
    This time I face new problem. Error log is below.
    ==================================================================
    Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
            at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
            at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
            at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
            at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
            at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
            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)
    ============================================================================
    Thanks & Regards,
    Charanjit Singh,

  • J2EE Engine not starting

    Hi
    I am having a problen in starting J2EE engine. Follwoing is the error log of file  DEV_JCONTROL. Can some body help me in this?
    Thanks in advance
    trc file: "D:\usr\sap\PCN\DVEBMGS00\work\dev_jcontrol", trc level: 1, release: "700"
    node name   : jcontrol
    pid         : 6048
    system name : PCN
    system nr.  : 00
    started at  : Mon Sep 29 12:34:11 2008
    arguments       :
           arg[00] : D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs\jcontrol.exe
           arg[01] : pf=D:\usr\sap\PCN\SYS\profile\PCN_DVEBMGS00_SAPXI
           arg[02] : -DSAPSTART=1
           arg[03] : -DCONNECT_PORT=64991
           arg[04] : -DSAPSYSTEM=00
           arg[05] : -DSAPSYSTEMNAME=PCN
           arg[06] : -DSAPMYNAME=SAPXI_PCN_00
           arg[07] : -DSAPPROFILE=D:\usr\sap\PCN\SYS\profile\PCN_DVEBMGS00_SAPXI
           arg[08] : -DFRFC_FALLBACK=ON
           arg[09] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 7492] Mon Sep 29 12:34:11 2008
    [Thr 7492] *** WARNING => INFO: Unknown property [instance.box.number=PCNDVEBMGS00sapxi] [jstartxx.c   841]
    [Thr 7492] *** WARNING => INFO: Unknown property [instance.en.host=SAPXI] [jstartxx.c   841]
    [Thr 7492] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 7492] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [D:\usr\sap\PCN\DVEBMGS00\j2ee\cluster\instance.properties;D:\usr\sap\PCN\DVEBMGS00\SDM\program\config\sdm_jstartup.properties]
    -> ms host    : SAPXI
    -> ms port    : 3901
    -> OS libs    : D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : D:\usr\sap\PCN\DVEBMGS00\j2ee\cluster\instance.properties
    -> files [01] : D:\usr\sap\PCN\DVEBMGS00\SDM\program\config\sdm_jstartup.properties
    Instance properties
    -> ms host    : SAPXI
    -> ms port    : 3901
    -> os libs    : D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : D:\usr\sap\PCN\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID4383600  : D:\usr\sap\PCN\DVEBMGS00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID4383650  : D:\usr\sap\PCN\DVEBMGS00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID4383600            : D:\usr\sap\PCN\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] ID4383650            : D:\usr\sap\PCN\DVEBMGS00\j2ee\cluster\instance.properties
    -> [02] sdm                  : D:\usr\sap\PCN\DVEBMGS00\SDM\program\config\sdm_jstartup.properties
    [Thr 7492] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
    [Thr 7492] [Node: bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_13
    [Thr 7492] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs\jstartup.jar
    [Thr 7492] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs\jvmx.jar
    JStartupIReadSection: read node properties [bootstrap]
    -> node name          : bootstrap
    -> node type          : bootstrap
    -> node execute       : yes
    -> java path          : C:\j2sdk1.4.2_13
    -> java parameters    : -Djco.jarm=1
    -> 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          : 256M
    -> root path          : D:\usr\sap\PCN\DVEBMGS00\j2ee\cluster
    -> class path         : .\bootstrap\launcher.jar
    -> OS libs path       : D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs
    -> main class         : com.sap.engine.offline.OfflineToolStart
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs\jstartup.jar;D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs\jvmx.jar
    -> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0043836
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 60000
    -> shutdown timeout   : 120000
    JControlStartJLaunch: program = D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs\jlaunch.exe
    -> arg[00] = D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\PCN\SYS\profile\PCN_DVEBMGS00_SAPXI
    -> arg[02] = -DSAPINFO=PCN_00_bootstrap
    -> arg[03] = -nodeId=-1
    -> arg[04] = -file=D:\usr\sap\PCN\DVEBMGS00\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_6048
    -> arg[06] = -nodeName=bootstrap
    -> arg[07] = -jvmOutFile=D:\usr\sap\PCN\DVEBMGS00\work\jvm_bootstrap.out
    -> arg[08] = -stdOutFile=D:\usr\sap\PCN\DVEBMGS00\work\std_bootstrap.out
    -> arg[09] = -locOutFile=D:\usr\sap\PCN\DVEBMGS00\work\dev_bootstrap
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=D:\usr\sap\PCN\SYS\profile\PCN_DVEBMGS00_SAPXI
    -> arg[12] = -DSAPSTART=1
    -> arg[13] = -DCONNECT_PORT=4509
    -> arg[14] = -DSAPSYSTEM=00
    -> arg[15] = -DSAPSYSTEMNAME=PCN
    -> arg[16] = -DSAPMYNAME=SAPXI_PCN_00
    -> arg[17] = -DSAPPROFILE=D:\usr\sap\PCN\SYS\profile\PCN_DVEBMGS00_SAPXI
    -> arg[18] = -DFRFC_FALLBACK=ON
    -> arg[19] = -DFRFC_FALLBACK_HOST=localhost
    -> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\PCN\102\bin;D:\oracle\SM4\102\bin;D:\oracle\c46\102\bin;D:\oracle\c46\920\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_13\bin;D:\usr\sap\PCN\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\PCN\DVEBMGS00\j2ee\os_libs;D:\oracle\PCN\102\bin;D:\oracle\SM4\102\bin;D:\oracle\c46\102\bin;D:\oracle\c46\920\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_13\bin;D:\usr\sap\PCN\SYS\exe\uc\NTI386
    [Thr 5276] JControlDPMessageProxy: Thread 5276 started as handler thread for R/3 dispatcher messages.
    [Thr 7492] Mon Sep 29 12:34:12 2008
    [Thr 7492] *** ERROR => invalid return code of process [bootstrap] (exitcode = -1) [jstartxx.c   1642]
    [Thr 7492] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc = -1)
    [Thr 7492] JControlCloseProgram: started (exitcode = -1)
    [Thr 7492] JControlCloseProgram: good bye... (exitcode = -1)

    Mayank
    Now I am having access to Configtool. and now while starting its gives error. Following is the extract form std.server0.out file:
    stdout/stderr redirect
    node name   : server0
    pid         : 2732
    system name : PCN
    system nr.  : 00
    started at  : Mon Sep 29 13:30:38 2008
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 3632] 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
    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 7.00   PatchLevel is starting...
    Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
    Loading: LogManager ... 6765 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 484 ms.
    Loading: ThreadManager ... 47 ms.
    Loading: IpVerificationManager ... 47 ms.
    Loading: ClassLoaderManager ... 15 ms.
    Loading: ClusterManager ... 907 ms.
    Loading: LockingManager ... 406 ms.
    Loading: ConfigurationManager ... 16078 ms.
    Loading: LicensingManager ... 16 ms.
    Loading: CacheManager ... 687 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service memory started. (16 ms).
      Service DQE started. (0 ms).
      Service timeout started. (15 ms).
      Service runtimeinfo started. (0 ms).
      Service cross started. (1125 ms).
      Service file started. (1156 ms).
      Service trex.service started. (15 ms).
      Service cafeuodi~mnuacc started. (0 ms).
      Service p4 started. (2422 ms).
      Service classpath_resolver started. (62 ms).
      Service cafeucc~api started. (8859 ms).
      Service userstore started. (16 ms).
      Service jmx_notification started. (141 ms).
      Service log_configurator started. (13094 ms).
      Service locking started. (0 ms).
      Service http started. (156 ms).
      Service naming started. (1329 ms).
      Service ts started. (31 ms).
      Service licensing started. (15 ms).
      Service jmsconnector started. (32 ms).
      Service failover started. (0 ms).
      Service appclient started. (32 ms).
      Service iiop started. (734 ms).
      Service javamail started. (2156 ms).
      Service connector started. (2641 ms).
      Service webservices started. (4703 ms).
      Service deploy started. (18406 ms).
      Service configuration started. (16 ms).
      Service MigrationService started. (16 ms).
      Service bimmrdeployer started. (0 ms).
      Service dbpool started. (2078 ms).
      Service cafeugpmailcf started. (16 ms).
      Service com.sap.security.core.ume.service started. (2125 ms).
    Sep 29, 2008 1:32:00 PM  ...xt.<init>(UserContextSpi, Properties) [SAPEngine_System_Thread[impl:5]_29] Fatal: Can not instantiate UserContext with given properties.
      service security ================= ERROR =================
    Core service security failed. J2EE Engine cannot be started.
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
         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.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
         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.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more
    [Framework -> criticalShutdown] Core service security failed. J2EE Engine cannot be started.
    Sep 29, 2008 1:32:00 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_29] Fatal: Critical shutdown was invoked. Reason is: Core service security failed. J2EE Engine cannot be started.
    stdout/stderr redirect
    node name   : server0
    pid         : 2732
    system name : PCN
    system nr.  : 00
    started at  : Mon Sep 29 13:32:06 2008
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 7356] 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
    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 7.00   PatchLevel is starting...
    Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
    Loading: LogManager ... 719 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 6422 ms.
    Loading: ThreadManager ... 47 ms.
    Loading: IpVerificationManager ... 0 ms.
    Loading: ClassLoaderManager ... 15 ms.
    Loading: ClusterManager ... 329 ms.
    Loading: LockingManager ... 46 ms.
    Loading: ConfigurationManager ... 2250 ms.
    Loading: LicensingManager ... 15 ms.
    Loading: CacheManager ... 110 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service userstore started. (16 ms).
      Service memory started. (16 ms).
      Service DQE started. (0 ms).
      Service cafeuodi~mnuacc started. (0 ms).
      Service cross started. (16 ms).
      Service file started. (47 ms).
      Service cafeucc~api started. (63 ms).
      Service runtimeinfo started. (47 ms).
      Service jmx_notification started. (47 ms).
      Service p4 started. (297 ms).
      Service timeout started. (265 ms).
      Service trex.service started. (265 ms).
      Service classpath_resolver started. (47 ms).
      Service deploy started. (8359 ms).
      Service MigrationService started. (125 ms).
      Service bimmrdeployer started. (15 ms).
      Service log_configurator started. (10344 ms).
      Service locking started. (16 ms).
      Service naming started. (594 ms).
      Service ts started. (16 ms).
      Service failover started. (0 ms).
      Service licensing started. (16 ms).
      Service iiop started. (140 ms).
      Service jmsconnector started. (31 ms).
      Service appclient started. (94 ms).
      Service javamail started. (312 ms).
      Service http started. (266 ms).
      Service connector started. (218 ms).
      Service configuration started. (78 ms).
      Service webservices started. (1812 ms).
      Service dbpool started. (4594 ms).
      Service cafeugpmailcf started. (157 ms).
      Service com.sap.security.core.ume.service started. (1531 ms).
    Sep 29, 2008 1:32:41 PM  ...xt.<init>(UserContextSpi, Properties) [SAPEngine_System_Thread[impl:5]_36] Fatal: Can not instantiate UserContext with given properties.
      service security ================= ERROR =================
    Core service security failed. J2EE Engine cannot be started.
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
         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.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
         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.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more
    [Framework -> criticalShutdown] Core service security failed. J2EE Engine cannot be started.
    Sep 29, 2008 1:32:41 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_36] Fatal: Critical shutdown was invoked. Reason is: Core service security failed. J2EE Engine cannot be started.
    stdout/stderr redirect
    node name   : server0
    pid         : 2732
    system name : PCN
    system nr.  : 00
    started at  : Mon Sep 29 13:32:47 2008
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 6676] 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
    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 7.00   PatchLevel is starting...
    Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
    Loading: LogManager ... 4719 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 156 ms.
    Loading: ThreadManager ... 15 ms.
    Loading: IpVerificationManager ... 16 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 187 ms.
    Loading: LockingManager ... 47 ms.
    Loading: ConfigurationManager ... 2219 ms.
    Loading: LicensingManager ... 16 ms.
    Loading: CacheManager ... 125 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service memory started. (16 ms).
      Service DQE started. (0 ms).
      Service cafeuodi~mnuacc started. (0 ms).
      Service cross started. (15 ms).
      Service file started. (46 ms).
      Service timeout started. (16 ms).
      Service cafeucc~api started. (16 ms).
      Service runtimeinfo started. (0 ms).
      Service trex.service started. (63 ms).
      Service jmx_notification started. (32 ms).
      Service userstore started. (47 ms).
      Service p4 started. (1188 ms).
      Service classpath_resolver started. (31 ms).
      Service log_configurator started. (7406 ms).
      Service locking started. (0 ms).
      Service naming started. (296 ms).
      Service appclient started. (94 ms).
      Service javamail started. (375 ms).
      Service jmsconnector started. (281 ms).
      Service failover started. (281 ms).
      Service http started. (766 ms).
      Service connector started. (265 ms).
      Service ts started. (515 ms).
      Service licensing started. (0 ms).
      Service iiop started. (1703 ms).
      Service webservices started. (3547 ms).
      Service deploy started. (14203 ms).
      Service MigrationService started. (62 ms).
      Service configuration started. (47 ms).
      Service bimmrdeployer started. (297 ms).
      Service dbpool started. (1234 ms).
      Service cafeugpmailcf started. (16 ms).
      Service com.sap.security.core.ume.service started. (1328 ms).
    Sep 29, 2008 1:33:21 PM  ...xt.<init>(UserContextSpi, Properties) [SAPEngine_System_Thread[impl:5]_35] Fatal: Can not instantiate UserContext with given properties.
      service security ================= ERROR =================
    Core service security failed. J2EE Engine cannot be started.
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
         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.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
         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.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more
    [Framework -> criticalShutdown] Core service security failed. J2EE Engine cannot be started.
    Sep 29, 2008 1:33:21 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_35] Fatal: Critical shutdown was invoked. Reason is: Core service security failed. J2EE Engine cannot be started.
    stdout/stderr redirect
    node name   : server0
    pid         : 2732
    system name : PCN
    system nr.  : 00
    started at  : Mon Sep 29 13:33:26 2008
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 6032] 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
    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 7.00   PatchLevel is starting...
    Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
    Loading: LogManager ... 468 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 313 ms.
    Loading: ThreadManager ... 15 ms.
    Loading: IpVerificationManager ... 16 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 172 ms.
    Loading: LockingManager ... 31 ms.
    Loading: ConfigurationManager ... 2172 ms.
    Loading: LicensingManager ... 32 ms.
    Loading: CacheManager ... 109 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service userstore started. (15 ms).
      Service memory started. (16 ms).
      Service DQE started. (0 ms).
      Service cafeuodi~mnuacc started. (0 ms).
      Service runtimeinfo started. (47 ms).
      Service cafeucc~api started. (62 ms).
      Service cross started. (172 ms).
      Service file started. (234 ms).
      Service jmx_notification started. (46 ms).
      Service trex.service started. (219 ms).
      Service timeout started. (234 ms).
      Service p4 started. (266 ms).
      Service classpath_resolver started. (0 ms).
      Service log_configurator started. (6219 ms).
      Service locking started. (0 ms).
      Service http started. (281 ms).
      Service naming started. (328 ms).
      Service failover started. (15 ms).
      Service appclient started. (31 ms).
      Service jmsconnector started. (47 ms).
      Service webservices started. (532 ms).
      Service javamail started. (360 ms).
      Service ts started. (172 ms).
      Service connector started. (235 ms).
      Service licensing started. (0 ms).
      Service iiop started. (156 ms).
      Service deploy started. (11219 ms).
      Service configuration started. (0 ms).
      Service MigrationService started. (109 ms).
      Service bimmrdeployer started. (765 ms).
      Service dbpool started. (3062 ms).
      Service cafeugpmailcf started. (16 ms).
      Service com.sap.security.core.ume.service started. (1625 ms).
    Sep 29, 2008 1:33:51 PM  ...xt.<init>(UserContextSpi, Properties) [SAPEngine_System_Thread[impl:5]_36] Fatal: Can not instantiate UserContext with given properties.
      service security ================= ERROR =================
    Core service security failed. J2EE Engine cannot be started.
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
         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.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
         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.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more
    [Framework -> criticalShutdown] Core service security failed. J2EE Engine cannot be started.
    Sep 29, 2008 1:33:51 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_36] Fatal: Critical shutdown was invoked. Reason is: Core service security failed. J2EE Engine cannot be started.

  • Jstart.exe process in sap mmc is not getting started

    Hi,
    The jstart.exe process of sap mmc (management console/server) is not getting started.
    The status for this process is "starting the processes". Need help!
    The developer trace is as follows :
    trc file: "dev_jstart.7668", trc level: 1, release: "720"
    trc file: "dev_jstart.new", trc level: 1, release: "720"
    sysno      02
    sid        SV1
    systemid   562 (PC with Windows NT)
    relno      7200
    patchlevel 0
    patchno    63
    intno      20020600
    make       multithreaded, Unicode, 64 bit, optimized
    profile    \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    pid        7668
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      All, egi
    Mon Oct 08 10:03:13 2012
    *  trace logging activated, max size = 52428800 bytes, 2 versions
    arguments :
      arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
      arg[ 1] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    F Mon Oct 08 10:03:13 2012
    F  ********************************************************************************
    F  Java environment properties (C:\usr\sap\SV1\J02\work\jstart.jvm)
    F    root directory    : C:\usr\sap\SV1\J02\exe\sapjvm_6
    F    vendor            : SAP AG
    F    version           : 1.6.0_17
    F    cpu               : amd64
    F    java vm type      : server
    F    java vm version   : 6.1.018
    F    jvm library name  : jvm.dll
    F    library path      : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
    F    executable path   : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
    F  ********************************************************************************
    F    SAP extensions    : available
    F  ********************************************************************************
    I  [Thr 7652] MtxInit: 30002 0 2
    trc file: "dev_jstart", trc level: 1, release: "720"
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      All, egi

    F [Thr 7652] Mon Oct 08 10:03:14 2012
    F  [Thr 7652] *** LOG => connected to Enqueue Server.
    F  [Thr 7652] *** LOG => connected to Message Server.
    F  [Thr 7652] *** LOG => Starting run level 1.
    F  ********************************************************************************
    F  Java process [deployment] properties:
    F    section name     : deployment
    F    config file      : C:\usr\sap\SV1\J02\exe\startup.properties
    F    node name        : Deploy_offline
    F    home directory   : C:\usr\sap\SV1\J02\j2ee\cluster
    F    shutdown timeout : 136000 ms
    F    exit timeout     : 7000 ms
    F    debuggable       : false
    F    debugger active  : false
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Instance state is "Deploying offline components" (STARTING @ 0, INACTIVE).
    F  [Thr 7652] *** LOG => Starting nodes: runlevel 1.

    F Mon Oct 08 10:03:15 2012
    F  ********************************************************************************
    F  Starting process: C:\usr\sap\SV1\J02\exe\jstart.EXE
    F    arg[ 1] = -nodeId=0
    F    arg[ 2] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    F    arg[ 3] = -hostvm
    F    arg[ 4] = -nodeName=deployment
    F    arg[ 5] = -file=C:\usr\sap\SV1\J02\exe\startup.properties
    F    arg[ 6] = -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
    F    arg[ 7] = -traceFile=C:\usr\sap\SV1\J02\work\dev_deployment
    F    arg[ 8] = -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_deployment.out
    F    env   : NODNSSAPTRANSHOST=1
    F  exePath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  libPath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  stdout  : C:\usr\sap\SV1\J02\work\std_deployment.out
    F  stderr  : C:\usr\sap\SV1\J02\work\std_deployment.out
    F  console : no
    F  debugger: no
    F  nice    : no
    F  ********************************************************************************
    F  Process Deploy_offline started with pid 7968
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Process deployment started (pid 7968).

    F [Thr 7652] Mon Oct 08 10:03:19 2012
    F  [Thr 7652] *** LOG => Process deployment stopping (pid 7968).

    F [Thr 6972] Mon Oct 08 10:03:19 2012
    F  [Thr 6972] *** LOG => Signal 13 SIGCHLD.
    F  [Thr 7652] *** LOG => Process deployment stopped (pid 7968).
    F  [Thr 7652] *** LOG => Instance state is "Deploying offline components" (STOPPING @ 0, INACTIVE).
    F  [Thr 7652] *** LOG => Run level 1 completed.
    F  [Thr 7652] *** LOG => Starting run level 2.
    F  ********************************************************************************
    F  Java process [bootstrap] properties:
    F    section name     : bootstrap
    F    config file      : C:\usr\sap\SV1\J02\exe\startup.properties
    F    node name        : Instance_bootstrap
    F    home directory   : C:\usr\sap\SV1\J02\j2ee\cluster
    F    shutdown timeout : 136000 ms
    F    exit timeout     : 7000 ms
    F    debuggable       : false
    F    debugger active  : false
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Instance state is "Synchronizing binaries" (STARTING @ 0, INACTIVE).
    F  [Thr 7652] *** LOG => Starting nodes: runlevel 2.

    F Mon Oct 08 10:03:20 2012
    F  ********************************************************************************
    F  Starting process: C:\usr\sap\SV1\J02\exe\jstart.EXE
    F    arg[ 1] = -nodeId=0
    F    arg[ 2] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    F    arg[ 3] = -hostvm
    F    arg[ 4] = -nodeName=bootstrap
    F    arg[ 5] = -file=C:\usr\sap\SV1\J02\exe\startup.properties
    F    arg[ 6] = -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
    F    arg[ 7] = -traceFile=C:\usr\sap\SV1\J02\work\dev_bootstrap
    F    arg[ 8] = -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_bootstrap.out
    F    env   : NODNSSAPTRANSHOST=1
    F  exePath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  libPath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  stdout  : C:\usr\sap\SV1\J02\work\std_bootstrap.out
    F  stderr  : C:\usr\sap\SV1\J02\work\std_bootstrap.out
    F  console : no
    F  debugger: no
    F  nice    : no
    F  ********************************************************************************
    F  Process Instance_bootstrap started with pid 7952
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Process bootstrap started (pid 7952).

    F [Thr 7652] Mon Oct 08 10:03:47 2012
    F  [Thr 7652] *** LOG => Process bootstrap running (pid 7952).
    F  [Thr 7652] *** LOG => Instance state is "Synchronizing binaries" (RUNNING @ 0, INACTIVE).

    F [Thr 7652] Mon Oct 08 10:04:10 2012
    F  [Thr 7652] *** LOG => Process bootstrap stopping (pid 7952).

    F [Thr 4436] Mon Oct 08 10:04:10 2012
    F  [Thr 4436] *** LOG => Signal 13 SIGCHLD.
    F  [Thr 7652] *** LOG => Process bootstrap stopped (pid 7952).
    F  [Thr 7652] *** LOG => Instance state is "Synchronizing binaries" (STOPPING @ 0, INACTIVE).
    F  [Thr 7652] *** LOG => Run level 2 completed.
    F  [Thr 7652] *** LOG => Starting run level 3.
    F  ********************************************************************************
    F  Java process [debugproxy] properties:
    F    section name     : debugproxy
    F    config file      : C:\usr\sap\SV1\J02\exe\dproxy.properties
    F    node name        : Debug_Proxy
    F    home directory   : C:\usr\sap\SV1\J02/j2ee/rdbg.proxy
    F    shutdown timeout : 136000 ms
    F    exit timeout     : 7000 ms
    F    debuggable       : false
    F    debugger active  : false
    F  ********************************************************************************
    F  ********************************************************************************
    F  ICM process [icm] properties:
    F    section name     : icm
    F    config file      : C:\usr\sap\SV1\J02\exe\icm.properties
    F    node name        : ICM
    F    home directory   : C:\usr\sap\SV1\J02\work
    F    shutdown timeout : 122000 ms
    F    exit timeout     : 7000 ms
    F  ********************************************************************************
    F  ********************************************************************************
    F  Java process [server0] properties:
    F    section name     : ID24836450
    F    config file      : C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
    F    node name        : server0
    F    home directory   : .
    F    shutdown timeout : 136000 ms
    F    exit timeout     : 7000 ms
    F    debuggable       : true
    F    debugger active  : false
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Instance state is "Starting the processes" (STARTING @ 0, INACTIVE).
    F  [Thr 7652] *** LOG => Starting nodes: runlevel 3, phase 0.
    F  ********************************************************************************
    F  Starting process: C:\usr\sap\SV1\J02\exe\icman.EXE
    F    arg[ 1] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    F    arg[ 2] = -nodeId=1
    F    arg[ 3] = -f
    F    arg[ 4] = C:\usr\sap\SV1\J02\work\\dev_icm
    F    env   : NODNSSAPTRANSHOST=1
    F  exePath : PATH=C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  libPath : PATH=C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  stdout  : C:\usr\sap\SV1\J02\work\std_icm.out
    F  stderr  : C:\usr\sap\SV1\J02\work\std_icm.out
    F  console : no
    F  debugger: no
    F  nice    : no
    F  ********************************************************************************
    F  Process ICM started with pid 7336
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Process icm started (pid 7336).

    F [Thr 7652] Mon Oct 08 10:04:12 2012
    F  [Thr 7652] *** LOG => Process icm running (pid 7336).
    F  [Thr 7652] *** LOG => Starting nodes: runlevel 3, phase 1.

    F Mon Oct 08 10:04:16 2012
    F  ********************************************************************************
    F  Starting process: C:\usr\sap\SV1\J02\exe\jstart.EXE
    F    arg[ 1] = -nodeId=2
    F    arg[ 2] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    F    arg[ 3] = -DSAPINFO=SV1_02_server0
    F    arg[ 4] = -hostvm
    F    arg[ 5] = -nodeName=ID24836450
    F    arg[ 6] = -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
    F    arg[ 7] = -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
    F    arg[ 8] = -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
    F    arg[ 9] = -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out
    F    env   : NODNSSAPTRANSHOST=1
    F  exePath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  libPath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  stdout  : C:\usr\sap\SV1\J02\work\std_server0.out
    F  stderr  : C:\usr\sap\SV1\J02\work\std_server0.out
    F  console : no
    F  debugger: no
    F  nice    : no
    F  ********************************************************************************
    F  Process server0 started with pid 7616
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Process server0 started (pid 7616).

    Hi Ravi,
    Thanks for your quick response.
    Where do I find the default trace for this?
    The server0 process status is "Waiting to start". The developer trace for server0 is as follows :
    trc file: "dev_server0", trc level: 1, release: "720"
    sysno      02
    sid        SV1
    systemid   562 (PC with Windows NT)
    relno      7200
    patchlevel 0
    patchno    63
    intno      20020600
    make       multithreaded, Unicode, 64 bit, optimized
    profile    \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    pid        7616
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      All, egi
    Mon Oct 08 10:04:17 2012
    *  trace logging activated, max size = 52428800 bytes, 2 versions
    arguments :
      arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
      arg[ 1] : -appTrc
      arg[ 2] : -nodeId=2
      arg[ 3] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
      arg[ 4] : -DSAPINFO=SV1_02_server0
      arg[ 5] : -hostvm
      arg[ 6] : -nodeName=ID24836450
      arg[ 7] : -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
      arg[ 8] : -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
      arg[ 9] : -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
      arg[10] : -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out

    F Mon Oct 08 10:04:17 2012
    F  ********************************************************************************
    F  Java environment properties
    F    root directory    : C:\usr\sap\SV1\J02\exe\sapjvm_6
    F    vendor            : SAP AG
    F    version           : 1.6.0_17
    F    cpu               : amd64
    F    java vm type      : server
    F    java vm version   : 6.1.018
    F    jvm library name  : jvm.dll
    F    library path      : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
    F    executable path   : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
    F    SAP extensions    : available
    F  ********************************************************************************
    I  [Thr 7280] MtxInit: 10002 0 2
    I  [Thr 7280] MPI: dynamic quotas disabled.
    I  [Thr 7280] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
    M  [Thr 7280] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
    M  [Thr 7280] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.
    M  [Thr 7280] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.
    M  [Thr 7280] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    M  [Thr 7280] CCMS: CCMS Monitoring Initialization finished, rc=0.

    F Mon Oct 08 10:04:17 2012
    F  ********************************************************************************
    F  SAP Java VM arguments:
    F    arg[ 0] = vfprintf
    F    arg[ 1] = abort
    F    arg[ 2] = exit
    F    arg[ 3] = -XmonGcCallback
    F    arg[ 4] = -XdebugStateChangeCallback
    F    arg[ 5] = -DSAPJStartVersion=720, patch 68, changelist 1198183, NTAMD64, optU (Oct 20 2010, 01:55:49)
    F    arg[ 6] = -Xjvmx
    F    arg[ 7] = -XsapSystem:02
    F    arg[ 8] = -DSAPSTARTUP=1
    F    arg[ 9] = -DSAPSYSTEM=02
    F    arg[10] = -DSAPSYSTEMNAME=SV1
    F    arg[11] = -DSAPMYNAME=INLD50787371A_SV1_02
    F    arg[12] = -DSAPDBHOST=INLD50787371A
    F    arg[13] = -DSAPINFO=SV1_02_server0
    F    arg[14] = -Dj2ee.dbhost=INLD50787371A
    F    arg[15] = -Dsun.java.launcher=jstart
    F    arg[16] = -Dsun.java.command=com.sap.engine.boot.Start 
    F    arg[17] = -Djstartup.mode=JSTART
    F    arg[18] = -Djstartup.whoami=server
    F    arg[19] = -Djstartup.ownProcessId=7616
    F    arg[20] = -Djstartup.ownHardwareId=Q0723431166
    F    arg[21] = -Djstartup.debuggable=yes
    F    arg[22] = -DLoadBalanceRestricted=no
    F    arg[23] = -XdebugPortRange:50221-50221
    F    arg[24] = -Denv.class.path=
    F    arg[25] = -Dsys.global.dir=C:\usr\sap\SV1\SYS\global
    F    arg[26] = -Dapplication.home=C:\usr\sap\SV1\J02\exe
    F    arg[27] = -Djava.class.path=C:\usr\sap\SV1\J02\exe\jstart71.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\SV1\J02\exe\jre\lib\iqlib.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\tools.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\memoryanalyzer.jar
    F    arg[28] = -Djava.library.path=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F    arg[29] = -XX:PermSize=1024m
    F    arg[30] = -Xmx2048m
    F    arg[31] = -XX:MaxNewSize=410m
    F    arg[32] = -XX:MaxPermSize=1024m
    F    arg[33] = -Xms2048m
    F    arg[34] = -XX:NewSize=410m
    F    arg[35] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    F    arg[36] = -Djavax.management.builder.initial=com.sap.pj.jmx.server.interceptor.InterceptorChainBuilder
    F    arg[37] = -Djmx.invoke.getters=true
    F    arg[38] = -Djava.security.policy=./../bin/kernel/java.policy
    F    arg[39] = -Djava.security.egd=file:/dev/urandom
    F    arg[40] = -Djava.awt.headless=true
    F    arg[41] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    F    arg[42] = -Drdbms.driverLocation=C:\sapdb\clients\SV1\runtime\jar\sapdbc.jar
    F    arg[43] = -Djava.io.tmpdir=./temp
    F    arg[44] = -Dsun.lang.ClassLoader.allowArraySyntax=true
    F    arg[45] = -Djava.protocol.handler.pkgs=com.sap.engine.httpdsrclient.protocols|iaik.protocol
    F    arg[46] = -Dnetworkaddress.cache.ttl=10
    F    arg[47] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler
    F    arg[48] = -Djco.jarm=1
    F    arg[49] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    F    arg[50] = -agentpath:C:\PROGRA~1\JPROFI~1\bin\WINDOW~1\jprofilerti.dll==port=8849
    F    arg[51] = -XX:+UseConcMarkSweepGC
    F    arg[52] = -XX:TargetSurvivorRatio=90
    F    arg[53] = -verbose:gc
    F    arg[54] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
    F    arg[55] = -XX:+PrintGCDetails
    F    arg[56] = -XX:MaxErrorQueueLength=200
    F    arg[57] = -XX:+PrintGCTimeStamps
    F    arg[58] = -XX:+DisableExplicitGC
    F    arg[59] = -XX:SoftRefLRUPolicyMSPerMB=1
    F    arg[60] = -XX:-StringInternTableInPermGen
    F    arg[61] = -XX:SurvivorRatio=9
    F    arg[62] = -XX:+HeapDumpOnOutOfMemoryError
    F    arg[63] = -XX:HeapDumpPath=OOM.hprof
    F    arg[64] = -XX:-TraceClassUnloading
    F    arg[65] = -Xss2097152
    F  ignore unrecognized options : no
    F  ********************************************************************************
    J  JVMX version - Sep 16 2010 15:40:24 - 61_REL - optU - windows amd64 - 6 - bas2:142976 (mixed mode)
    J  Error occurred during initialization of VM
    J  Could not find agent library in absolute path: C:\PROGRA?1\JPROFI?1\bin\WINDOW?1\jprofilerti.dll
    F  [Thr 7364] *** LOG => SfCJavaVm: abort hook is called.

    F [Thr 7280] Mon Oct 08 12:28:13 2012
    F  [Thr 7280] *** LOG => Command STOP 0 {}.
    F  [Thr 7280] *** LOG => Result for STOP 0 {}: 0 ok, 00000000.

    F [Thr 7280] Mon Oct 08 12:28:33 2012
    F  [Thr 7280] *** LOG => Command DUMP_THREADS 0 {}.

    J  ================================================================================
    J  Java thread dump : Mon Oct 08 12:28:33 2012

    J  ================================================================================
    F  [Thr 7280] *** LOG => Result for DUMP_THREADS 0 {}: 0 ok, 00000000.

    M [Thr 684] Mon Oct 08 12:28:33 2012
    M  [Thr 684] CCMS: CCMS Monitoring Cleanup finished successfully.
    trc file: "dev_server0", trc level: 1, release: "720"
    sysno      02
    sid        SV1
    systemid   562 (PC with Windows NT)
    relno      7200
    patchlevel 0
    patchno    63
    intno      20020600
    make       multithreaded, Unicode, 64 bit, optimized
    profile    \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    pid        5508
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      All, egi
    Mon Oct 08 12:28:34 2012
    *  trace logging activated, max size = 52428800 bytes, 2 versions
    arguments :
      arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
      arg[ 1] : -appTrc
      arg[ 2] : -nodeId=2
      arg[ 3] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
      arg[ 4] : -DSAPINFO=SV1_02_server0
      arg[ 5] : -hostvm
      arg[ 6] : -nodeName=ID24836450
      arg[ 7] : -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
      arg[ 8] : -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
      arg[ 9] : -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
      arg[10] : -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out

    F Mon Oct 08 12:28:34 2012
    F  ********************************************************************************
    F  Java environment properties
    F    root directory    : C:\usr\sap\SV1\J02\exe\sapjvm_6
    F    vendor            : SAP AG
    F    version           : 1.6.0_17
    F    cpu               : amd64
    F    java vm type      : server
    F    java vm version   : 6.1.018
    F    jvm library name  : jvm.dll
    F    library path      : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
    F    executable path   : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
    F    SAP extensions    : available
    F  ********************************************************************************
    I  [Thr 500] MtxInit: 10002 0 2
    I  [Thr 500] MPI: dynamic quotas disabled.
    I  [Thr 500] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
    M  [Thr 500] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
    M  [Thr 500] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.
    M  [Thr 500] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.
    M  [Thr 500] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    M  [Thr 500] CCMS: CCMS Monitoring Initialization finished, rc=0.

    F Mon Oct 08 12:28:34 2012
    F  ********************************************************************************
    F  SAP Java VM arguments:
    F    arg[ 0] = vfprintf
    F    arg[ 1] = abort
    F    arg[ 2] = exit
    F    arg[ 3] = -XmonGcCallback
    F    arg[ 4] = -XdebugStateChangeCallback
    F    arg[ 5] = -DSAPJStartVersion=720, patch 68, changelist 1198183, NTAMD64, optU (Oct 20 2010, 01:55:49)
    F    arg[ 6] = -Xjvmx
    F    arg[ 7] = -XsapSystem:02
    F    arg[ 8] = -DSAPSTARTUP=1
    F    arg[ 9] = -DSAPSYSTEM=02
    F    arg[10] = -DSAPSYSTEMNAME=SV1
    F    arg[11] = -DSAPMYNAME=INLD50787371A_SV1_02
    F    arg[12] = -DSAPDBHOST=INLD50787371A
    F    arg[13] = -DSAPINFO=SV1_02_server0
    F    arg[14] = -Dj2ee.dbhost=INLD50787371A
    F    arg[15] = -Dsun.java.launcher=jstart
    F    arg[16] = -Dsun.java.command=com.sap.engine.boot.Start 
    F    arg[17] = -Djstartup.mode=JSTART
    F    arg[18] = -Djstartup.whoami=server
    F    arg[19] = -Djstartup.ownProcessId=5508
    F    arg[20] = -Djstartup.ownHardwareId=Q0723431166
    F    arg[21] = -Djstartup.debuggable=yes
    F    arg[22] = -DLoadBalanceRestricted=no
    F    arg[23] = -XdebugPortRange:50221-50221
    F    arg[24] = -Denv.class.path=
    F    arg[25] = -Dsys.global.dir=C:\usr\sap\SV1\SYS\global
    F    arg[26] = -Dapplication.home=C:\usr\sap\SV1\J02\exe
    F    arg[27] = -Djava.class.path=C:\usr\sap\SV1\J02\exe\jstart71.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\SV1\J02\exe\jre\lib\iqlib.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\tools.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\memoryanalyzer.jar
    F    arg[28] = -Djava.library.path=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F    arg[29] = -XX:PermSize=1024m
    F    arg[30] = -Xmx2048m
    F    arg[31] = -XX:MaxNewSize=410m
    F    arg[32] = -XX:MaxPermSize=1024m
    F    arg[33] = -Xms2048m
    F    arg[34] = -XX:NewSize=410m
    F    arg[35] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    F    arg[36] = -Djavax.management.builder.initial=com.sap.pj.jmx.server.interceptor.InterceptorChainBuilder
    F    arg[37] = -Djmx.invoke.getters=true
    F    arg[38] = -Djava.security.policy=./../bin/kernel/java.policy
    F    arg[39] = -Djava.security.egd=file:/dev/urandom
    F    arg[40] = -Djava.awt.headless=true
    F    arg[41] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    F    arg[42] = -Drdbms.driverLocation=C:\sapdb\clients\SV1\runtime\jar\sapdbc.jar
    F    arg[43] = -Djava.io.tmpdir=./temp
    F    arg[44] = -Dsun.lang.ClassLoader.allowArraySyntax=true
    F    arg[45] = -Djava.protocol.handler.pkgs=com.sap.engine.httpdsrclient.protocols|iaik.protocol
    F    arg[46] = -Dnetworkaddress.cache.ttl=10
    F    arg[47] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler
    F    arg[48] = -Djco.jarm=1
    F    arg[49] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    F    arg[50] = -agentpath:C:\PROGRA~1\JPROFI~1\bin\WINDOW~1\jprofilerti.dll==port=8849
    F    arg[51] = -XX:+UseConcMarkSweepGC
    F    arg[52] = -XX:TargetSurvivorRatio=90
    F    arg[53] = -verbose:gc
    F    arg[54] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
    F    arg[55] = -XX:+PrintGCDetails
    F    arg[56] = -XX:MaxErrorQueueLength=200
    F    arg[57] = -XX:+PrintGCTimeStamps
    F    arg[58] = -XX:+DisableExplicitGC
    F    arg[59] = -XX:SoftRefLRUPolicyMSPerMB=1
    F    arg[60] = -XX:-StringInternTableInPermGen
    F    arg[61] = -XX:SurvivorRatio=9
    F    arg[62] = -XX:+HeapDumpOnOutOfMemoryError
    F    arg[63] = -XX:HeapDumpPath=OOM.hprof
    F    arg[64] = -XX:-TraceClassUnloading
    F    arg[65] = -Xss2097152
    F  ignore unrecognized options : no
    F  ********************************************************************************
    J  JVMX version - Sep 16 2010 15:40:24 - 61_REL - optU - windows amd64 - 6 - bas2:142976 (mixed mode)
    J  Error occurred during initialization of VM
    J  Could not find agent library in absolute path: C:\PROGRA?1\JPROFI?1\bin\WINDOW?1\jprofilerti.dll
    F  [Thr 4136] *** LOG => SfCJavaVm: abort hook is called.

    F [Thr 500] Mon Oct 08 12:29:02 2012
    F  [Thr 500] *** LOG => Command DUMP_THREADS 0 {}.

    J  ================================================================================
    J  Java thread dump : Mon Oct 08 12:29:02 2012

    J  ================================================================================
    F  [Thr 500] *** LOG => Result for DUMP_THREADS 0 {}: 0 ok, 00000000.

    M [Thr 5068] Mon Oct 08 12:29:02 2012
    M  [Thr 5068] CCMS: CCMS Monitoring Cleanup finished successfully.
    trc file: "dev_server0", trc level: 1, release: "720"
    sysno      02
    sid        SV1
    systemid   562 (PC with Windows NT)
    relno      7200
    patchlevel 0
    patchno    63
    intno      20020600
    make       multithreaded, Unicode, 64 bit, optimized
    profile    \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    pid        7704
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      All, egi
    Mon Oct 08 12:29:17 2012
    *  trace logging activated, max size = 52428800 bytes, 2 versions
    arguments :
      arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
      arg[ 1] : -appTrc
      arg[ 2] : -nodeId=2
      arg[ 3] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
      arg[ 4] : -DSAPINFO=SV1_02_server0
      arg[ 5] : -hostvm
      arg[ 6] : -nodeName=ID24836450
      arg[ 7] : -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
      arg[ 8] : -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
      arg[ 9] : -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
      arg[10] : -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out

    F Mon Oct 08 12:29:17 2012
    F  ********************************************************************************
    F  Java environment properties
    F    root directory    : C:\usr\sap\SV1\J02\exe\sapjvm_6
    F    vendor            : SAP AG
    F    version           : 1.6.0_17
    F    cpu               : amd64
    F    java vm type      : server
    F    java vm version   : 6.1.018
    F    jvm library name  : jvm.dll
    F    library path      : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
    F    executable path   : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
    F    SAP extensions    : available
    F  ********************************************************************************
    I  [Thr 4980] MtxInit: 10002 0 2
    I  [Thr 4980] MPI: dynamic quotas disabled.
    I  [Thr 4980] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
    M  [Thr 4980] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
    M  [Thr 4980] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.
    M  [Thr 4980] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.
    M  [Thr 4980] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    M  [Thr 4980] CCMS: CCMS Monitoring Initialization finished, rc=0.

    F Mon Oct 08 12:29:17 2012
    F  ********************************************************************************
    F  SAP Java VM arguments:
    F    arg[ 0] = vfprintf
    F    arg[ 1] = abort
    F    arg[ 2] = exit
    F    arg[ 3] = -XmonGcCallback
    F    arg[ 4] = -XdebugStateChangeCallback
    F    arg[ 5] = -DSAPJStartVersion=720, patch 68, changelist 1198183, NTAMD64, optU (Oct 20 2010, 01:55:49)
    F    arg[ 6] = -Xjvmx
    F    arg[ 7] = -XsapSystem:02
    F    arg[ 8] = -DSAPSTARTUP=1
    F    arg[ 9] = -DSAPSYSTEM=02
    F    arg[10] = -DSAPSYSTEMNAME=SV1
    F    arg[11] = -DSAPMYNAME=INLD50787371A_SV1_02
    F    arg[12] = -DSAPDBHOST=INLD50787371A
    F    arg[13] = -DSAPINFO=SV1_02_server0
    F    arg[14] = -Dj2ee.dbhost=INLD50787371A
    F    arg[15] = -Dsun.java.launcher=jstart
    F    arg[16] = -Dsun.java.command=com.sap.engine.boot.Start 
    F    arg[17] = -Djstartup.mode=JSTART
    F    arg[18] = -Djstartup.whoami=server
    F    arg[19] = -Djstartup.ownProcessId=7704
    F    arg[20] = -Djstartup.ownHardwareId=Q0723431166
    F    arg[21] = -Djstartup.debuggable=yes
    F    arg[22] = -DLoadBalanceRestricted=no
    F    arg[23] = -XdebugPortRange:50221-50221
    F    arg[24] = -Denv.class.path=
    F    arg[25] = -Dsys.global.dir=C:\usr\sap\SV1\SYS\global
    F    arg[26] = -Dapplication.home=C:\usr\sap\SV1\J02\exe
    F    arg[27] = -Djava.class.path=C:\usr\sap\SV1\J02\exe\jstart71.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\SV1\J02\exe\jre\lib\iqlib.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\tools.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\memoryanalyzer.jar
    F    arg[28] = -Djava.library.path=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F    arg[29] = -XX:PermSize=1024m
    F    arg[30] = -Xmx2048m
    F    arg[31] = -XX:MaxNewSize=410m
    F    arg[32] = -XX:MaxPermSize=1024m
    F    arg[33] = -Xms2048m
    F    arg[34] = -XX:NewSize=410m
    F    arg[35] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    F    arg[36] = -Djavax.management.builder.initial=com.sap.pj.jmx.server.interceptor.InterceptorChainBuilder
    F    arg[37] = -Djmx.invoke.getters=true
    F    arg[38] = -Djava.security.policy=./../bin/kernel/java.policy
    F    arg[39] = -Djava.security.egd=file:/dev/urandom
    F    arg[40] = -Djava.awt.headless=true
    F    arg[41] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    F    arg[42] = -Drdbms.driverLocation=C:\sapdb\clients\SV1\runtime\jar\sapdbc.jar
    F    arg[43] = -Djava.io.tmpdir=./temp
    F    arg[44] = -Dsun.lang.ClassLoader.allowArraySyntax=true
    F    arg[45] = -Djava.protocol.handler.pkgs=com.sap.engine.httpdsrclient.protocols|iaik.protocol
    F    arg[46] = -Dnetworkaddress.cache.ttl=10
    F    arg[47] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler
    F    arg[48] = -Djco.jarm=1
    F    arg[49] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    F    arg[50] = -agentpath:C:\PROGRA~1\JPROFI~1\bin\WINDOW~1\jprofilerti.dll==port=8849
    F    arg[51] = -XX:+UseConcMarkSweepGC
    F    arg[52] = -XX:TargetSurvivorRatio=90
    F    arg[53] = -verbose:gc
    F    arg[54] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
    F    arg[55] = -XX:+PrintGCDetails
    F    arg[56] = -XX:MaxErrorQueueLength=200
    F    arg[57] = -XX:+PrintGCTimeStamps
    F    arg[58] = -XX:+DisableExplicitGC
    F    arg[59] = -XX:SoftRefLRUPolicyMSPerMB=1
    F    arg[60] = -XX:-StringInternTableInPermGen
    F    arg[61] = -XX:SurvivorRatio=9
    F    arg[62] = -XX:+HeapDumpOnOutOfMemoryError
    F    arg[63] = -XX:HeapDumpPath=OOM.hprof
    F    arg[64] = -XX:-TraceClassUnloading
    F    arg[65] = -Xss2097152
    F  ignore unrecognized options : no
    F  ********************************************************************************
    J  JVMX version - Sep 16 2010 15:40:24 - 61_REL - optU - windows amd64 - 6 - bas2:142976 (mixed mode)
    J  Error occurred during initialization of VM
    J  Could not find agent library in absolute path: C:\PROGRA?1\JPROFI?1\bin\WINDOW?1\jprofilerti.dll
    F  [Thr 4736] *** LOG => SfCJavaVm: abort hook is called.

  • Java Instance not getting started

    Hi Experts,
                      After System copy we are not able to start the java instance of SAP BW Java Instance of 7.0.Though Dispatcher is getting started but server 0 is not getting started.Sending you the jcontrol & dev_w0 error.We are using sql server 2008 & win 2008.
    [Thr 6336] JControlICheckProcessList: process server0 started (PID:6268)
    [Thr 6336] Mon Jun 21 02:50:16 2010
    [Thr 6336] JControlICheckProcessList: process server0 (pid:6268) died (RUN-FLAG)
    [Thr 6336] JControlIResetProcess: reset process server0
    [Thr 6336] JControlIResetProcess: [server0] not running -> increase error count (4)
    [Thr 6336] JControlICheckProcessList: running flight recorder:
         C:\j2sdk1.4.2_19-x64\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID15726550 1277103001 -bz G:\usr\sap\DBJ\SYS\global
    dev_w0----
    [Thr 4704] Mon Jun 21 03:39:01 2010
    [Thr 4704] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr 4704] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 4704] JLaunchCloseProgram: good bye (exitcode = -11113)
    Please suggest.

    Sunny sending u the log files.Yah I have imported java of our source system.
    dev_sever0 log :
    trc file: "G:\usr\sap\DBJ\JC01\work\dev_server0", trc level: 1, release: "701"
    node name   : ID15726550
    pid         : 388
    system name : DBJ
    system nr.  : 01
    started at  : Tue Jun 22 02:56:02 2010
    arguments       :
           arg[00] : G:\usr\sap\DBJ\JC01\exe\jlaunch.exe
           arg[01] : pf=G:\usr\sap\DBJ\SYS\profile\DBJ_JC01_GOLITSAPD28
           arg[02] : -DSAPINFO=DBJ_01_server
           arg[03] : pf=G:\usr\sap\DBJ\SYS\profile\DBJ_JC01_GOLITSAPD28
    [Thr 4416] Tue Jun 22 02:56:02 2010
    [Thr 4416] *** WARNING => INFO: Unknown property [instance.box.number=DBJJC01golitsapd28] [jstartxx.c   841]
    [Thr 4416] *** WARNING => INFO: Unknown property [instance.en.host=GOLITSAPD28] [jstartxx.c   841]
    [Thr 4416] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]
    [Thr 4416] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [G:\usr\sap\DBJ\JC01\j2ee\cluster\instance.properties]
    -> ms host    : GOLITSAPD28
    -> ms port    : 3900
    -> OS libs    : G:\usr\sap\DBJ\JC01\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : normal
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : G:\usr\sap\DBJ\JC01\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : GOLITSAPD28
    -> ms port    : 3900
    -> os libs    : G:\usr\sap\DBJ\JC01\j2ee\os_libs
    -> admin URL  :
    -> run mode   : normal
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : G:\usr\sap\DBJ\JC01\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID15726500 : G:\usr\sap\DBJ\JC01\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID15726550 : G:\usr\sap\DBJ\JC01\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID15726500           : G:\usr\sap\DBJ\JC01\j2ee\cluster\instance.properties
    -> [01] ID15726550           : G:\usr\sap\DBJ\JC01\j2ee\cluster\instance.properties
    [Thr 4416] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 4416] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 5144] JLaunchRequestFunc: Thread 5144 started as listener thread for np messages.
    [Thr 6104] WaitSyncSemThread: Thread 6104 started as semaphore monitor thread.
    [Thr 4416] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 4416] CPIC (version=701.2009.01.26)
    [Thr 4416] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_19-x64\
    [Thr 4416] JStartupICheckFrameworkPackage: can't find framework package G:\usr\sap\DBJ\JC01\exe\jvmx.jar
    [Thr 4316] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 4316] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 4316] JLaunchISetClusterId: set cluster id 15726550
    [Thr 4316] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 4316] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    Tue Jun 22 02:56:32 2010
    4.725: [GC 4.725: [DefNew: 174592K->12689K(261888K), 0.0611219 secs] 174592K->12689K(2009856K), 0.0612466 secs]
    Tue Jun 22 02:56:34 2010
    6.803: [GC 6.803: [DefNew: 187281K->16256K(261888K), 0.0465093 secs] 187281K->16256K(2009856K), 0.0465882 secs]
    Tue Jun 22 02:56:36 2010
    8.329: [GC 8.329: [DefNew: 190848K->18509K(261888K), 0.0445783 secs] 190848K->18509K(2009856K), 0.0446530 secs]
    Tue Jun 22 02:56:37 2010
    9.631: [GC 9.631: [DefNew: 193101K->22134K(261888K), 0.0486306 secs] 193101K->22134K(2009856K), 0.0487179 secs]
    [Thr 7116] Tue Jun 22 02:56:40 2010
    [Thr 7116] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr 7116] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 7116] JLaunchCloseProgram: good bye (exitcode = -11113)
    [Thr 568] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 568] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 5544] JLaunchRequestFunc: Thread 5544 started as listener thread for np messages.
    [Thr 5408] WaitSyncSemThread: Thread 5408 started as semaphore monitor thread.
    [Thr 568] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 568] CPIC (version=701.2009.01.26)
    [Thr 568] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_19-x64\
    [Thr 568] Tue Jun 22 02:56:43 2010
    [Thr 568] JStartupICheckFrameworkPackage: can't find framework package G:\usr\sap\DBJ\JC01\exe\jvmx.jar
    Edited by: N. Das on Jun 22, 2010 11:44 AM

  • SDM is not getting started

    hi experts,
    When J2EE server is started, SDM is not getting started. It appears in red color. what could be wrong ?
    thanks in advance,
    nikhil

    Hello Nikhil,
    Probably the reason is that the SDM is in standalone mode. Open command prompt in the SDM folder(SDM/program/) and execute the following commands:
    For Windows:
    sdm.bat jstartup “mode=integrated”
    StartServer.bat
    For UNIX:
    ./sdm.sh jstartup mode=integrated
    ./StartServer.sh
    If that doesn’t help, please check the dev_sdm std_sdm.out and jvm_sdm.out log files in the instance work directory.
    Regards,
    Ventsi Tsachev
    Technology Development Support (J2EE Engine)
    SAP Labs, Palo Alto, Ca (USA)

  • Com.sap.security.core.ume.service failed. J2EE Engine cannot be started

    Hi,
    I have configured SNC on NetWeaver 7.0 (ABAP+JAVA) System on Windows 2003 Server with MS-SQL 2005 Database.
    After the SNC configuration restarted the Server but the JAVA Server process is going down with EXIT Code -11113. The SNC Configuration is working fine but JAVA is not running. SDM and dispatcher are in green but server process is going gray.
    I have checked the log files under C:\usr\sap\SID\DVEBMGS00\j2ee\cluster\server0\log
    The following is the part of log file.
    #1.5#005056BA6C3F001D0000000F000008D8000489ACAFC86070#1277274683393#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_71##0#0#Error#1#/System/Server#Java###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    [EXCEPTION]
    #1#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:372)
         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:105)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    #1.5#005056BA6C3F001D00000011000008D8000489ACAFC8628E#1277274683393#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_71##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.#
    Please help me to solve the issue.
    Thanks,
    Ajay.

    Hi Tim,
    I have configured using Kerberos library for 32 bit on Net Weaver 7.0 with MS SQL 2005 Server on Windows 2003 Server. I didnt change any thing on JAVA side. I have configured as per the Kerberos configuration steps  as per below URL
    http://help.sap.com/saphelp_nw70ehp2/helpdata/en/44/0ebf6c9b2b0d1ae10000000a114a6b/frameset.htm
    The configuration was successful and I am able to login with out asking password, but After the configuration when I have restarted every thing on ABAP side works well but JAVA server process going down with EXIT code -11113. One of the log file contains follows error message.
    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:372)
         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:105)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Jun 25, 2010 3:05:24 AM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_69] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    One of the line says "SNC required for this connection". What does this mean? What else need to be done for JAVA to communicate with ABAP?
    Thanks,
    Ajay.

  • Exit Code -11114 J2EE Engine doesn't start completely. DESPERATE

    XI system - Windows - Oracle - ABAP + Java Stack
    We would like to upgrade our J2EE Engine Version however, during the upgrade, there is a phase wherein the J2EE Engine is being started. But, as it is being started, it returns an error and it provides the message Exit Code -11114 and it starts restarts the J2EE Instance automatically over and over again. I've read a forum here that resolved this error. However, the scenario wherein the data source is database_only is not applicable to our case since our data source is already dataSourceConfiguration_r3_roles_db.xml. Furthermore, I've read in one of the logs that indicates that: Critical shutdown was invoked. Reason is: 5 core services have timed out http://adminadapter; security; jmx; com.sap.security.core.ume.service; basicadmin. Hope you could help us out! Please help us! This is affecting the business operation since the server 0 doesn't startup completely, thus the java sites are all inaccessible.
    Here is one part of the trace.
    #1.5#0015C588AED40047000001690000141800044578CA30039C#1202284997468#com.sap.engine.services.servlets_jsp.server.container.WebContainer##com.sap.engine.services.servlets_jsp.server.container.WebContainer#######SAPEngine_System_Thread[impl:5]_51##0#0#Error#1#/System/Server#Plain###Cannot lookup and destroy an application context of [sap.com/com.sap.aii.af.sdk.rnif.message.listener] application.
    The error is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at applications, the whole lookup name is webContainer/applications/sap.com/com.sap.aii.af.sdk.rnif.message.listener.
    Exception id: [0015C588AED40047000001670000141800044578CA300130]#
    #1.5#0015C588AED400470000016E0000141800044578CA30A0A8#1202284997515#com.sap.engine.services.servlets_jsp.Deploy##com.sap.engine.services.servlets_jsp.Deploy#######SAPEngine_System_Thread[impl:5]_51##0#0#Error##Plain###Cannot lookup and destroy an application context of [sap.com/tclmwebadminclusteradminapp] application. The error is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at applications, the whole lookup name is webContainer/applications/sap.com/tclmwebadminclusteradminapp.
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.sap.engine.services.servlets_jsp.server.container.StopAction.unBindApp(StopAction.java:92)
         at com.sap.engine.services.servlets_jsp.server.container.StopAction.commitStop(StopAction.java:56)
         at com.sap.engine.services.servlets_jsp.server.container.WebContainer.commitStop(WebContainer.java:419)
         at com.sap.engine.services.deploy.server.application.StopTransaction.commonCommitFinished(StopTransaction.java:262)
         at com.sap.engine.services.deploy.server.application.StopTransaction.commitCommon(StopTransaction.java:305)
         at com.sap.engine.services.deploy.server.application.StopTransaction.commitLocal(StopTransaction.java:296)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:374)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:117)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:235)
         at com.sap.engine.services.deploy.server.FinishListener.run(FinishListener.java:77)
         at com.sap.engine.services.deploy.server.FinishListener.makeOperation(FinishListener.java:57)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startTransactionsLocal(DeployServiceImpl.java:4183)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.stopMyApplications(DeployCommunicatorImpl.java:214)
         at com.sap.engine.services.servlets_jsp.server.ServletsAndJspServerFrame.stop(ServletsAndJspServerFrame.java:235)
         at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:31)
         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#0015C588AED40047000001700000141800044578CA30A304#1202284997515#com.sap.engine.services.servlets_jsp.server.container.WebContainer##com.sap.engine.services.servlets_jsp.server.container.WebContainer#######SAPEngine_System_Thread[impl:5]_51##0#0#Error#1#/System/Server#Plain###Cannot lookup and destroy an application context of [sap.com/tclmwebadminclusteradminapp] application.
    The error is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at applications, the whole lookup name is webContainer/applications/sap.com/tclmwebadminclusteradminapp.
    Exception id: [0015C588AED400470000016E0000141800044578CA30A0A8]#
    #1.5#0015C588AED4005D0000004A0000141800044578CA38DF9E#1202284998062#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:
    Thread[SAPEngine_System_Thread[impl:5]_5]
    Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: java.lang.Thread | toString: Thread[SAPEngine_EnquReader,5,main]] with classloader [com.sap.engine.boot.CoreClassLoader@a981ca]#
    #1.5#0015C588AED4005D0000004B0000141800044578CA38F484#1202284998062#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:
    Thread[SAPEngine_System_Thread[impl:5]_51]
    Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: com.sap.engine.core.service630.container.ServiceStopper | toString: com.sap.engine.core.service630.container.ServiceStopper@122c960] with classloader [null]#
    #1.5#0015C588AED4005D0000004C0000141800044578CA38F5B3#1202284998062#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:
    Thread[SAPEngine_System_Thread[impl:5]_71]
    Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: com.sap.engine.services.log_configurator.archive.ArchivingThread | toString: [email protected]d2e636] with classloader [[email protected]5b6@service:log_configurator]#
    #1.5#0015C588AED40047000001780000141800044578CA38F6DB#1202284998062#com.sap.engine.core.service630.container.ServiceStopper##com.sap.engine.core.service630.container.ServiceStopper#######SAPEngine_System_Thread[impl:5]_51##0#0#Error##Plain###Service servlet_jsp error java.lang.ThreadDeath during shutdown.#
    #1.5#0015C588AED4005D0000004D0000141800044578CA3DA356#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
    Thread[SAPEngine_Application_Thread[impl:3]_2]
    Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.af.service.jms.WorkerHandlerImpl | toString: com.sap.aii.af.service.jms.WorkerHandlerImpl@81f25] with classloader [[email protected]b87f@service:com.sap.aii.adapter.jms.svc]#
    #1.5#0015C588AED4005D0000004E0000141800044578CA3DA528#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
    Thread[SAPEngine_Application_Thread[impl:3]_25]
    Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory | toString: [email protected]2222] with classloader [[email protected]74b@common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore]#
    #1.5#0015C588AED4005D0000004F0000141800044578CA3DA681#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
    Thread[SAPEngine_Application_Thread[impl:3]_29]
    Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.af.service.scheduler.JobBroker$Broker | toString: com.sap.aii.af.service.scheduler.JobBroker$Broker@134d801] with classloader [[email protected]619e@service:com.sap.aii.af.svc]#
    #1.5#0015C588AED4005D000000500000141800044578CA3DA79A#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
    Thread[SAPEngine_Application_Thread[impl:3]_32]
    Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.adapter.xi.ms.SLDReader | toString: com.sap.aii.adapter.xi.ms.SLDReader@513bb5] with classloader [[email protected]4ab4@service:com.sap.aii.adapter.xi.svc]#
    #1.5#0015C588AED4001900000000000034D800044578FAB55C7D#1202285811437#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupConfigurationService().after<super()>#
    #1.5#0015C588AED4001900000001000034D800044578FAB58D2D#1202285811437#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupConfigurationService().after<applicationServiceContext = ctx;>#
    #1.5#0015C588AED4001900000002000034D800044578FAB597E9#1202285811453#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###mobile_setupGenerationdoes exist.#
    #1.5#0015C588AED4001900000003000034D800044578FAC784C7#1202285812625#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupApplicationServiceFrame.after<7>#
    #1.5#0015C588AED4001900000004000034D800044578FAC78D1C#1202285812625#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupApplicationServiceFrame.after<8>#
    #1.5#0015C588AED4000000000016000034D8000445790BF2E967#1202286100703#com.sap.engine.frame.Environment##com.sap.engine.frame.Environment#######Thread[Thread-1,5,main]##0#0#Error#1#/System#Plain###Wed Feb 06 16:21:40 CST 2008 Thread[Thread-1] initiated a full thread dump due to: Timed out services:
    Service com.sap.aii.af.svc > hard reference to service com.sap.aii.af.cpa.svc.
    Service com.sap.aii.adapter.marketplace.svc > hard reference to service com.sap.aii.af.cpa.svc.
    Service ejb > hard reference to interface security.
    Service com.sap.aii.af.security.service > hard reference to service keystore.
    Service ssl > hard reference to service keystore.
    Service com.sap.aii.adapter.jms.svc > hard reference to service com.sap.aii.af.cpa.svc.
    Service adminadapter > hard reference to service jmx.
    Service tcsecsecurestorage~service > hard reference to service keystore.
    Service pmi > hard reference to service tcsecdestinations~service.
    Service security > hard reference to service com.sap.security.core.ume.service.
    Service jms_provider > hard reference to service security.
    Service sld > hard reference to service tcsecsecurestorage~service.
    Service jmx > hard reference to interface security.
    Service rfcengine > hard reference to service ejb.
    Service tcsecsaml~service > hard reference to service adminadapter.
    Service telnet > hard reference to service shell.
    Service com.sap.aii.adapter.jdbc.svc > hard reference to service com.sap.aii.af.cpa.svc.
    Service tclmctcculculservice_sda > hard reference to service jmx.
    Service webdynpro > hard reference to interface shell.
    Service tcsecvsiservice > hard reference to service tcsecdestinationsservice.
    Service tceCATTPingservice > hard reference to interface shell.
    Service com.sap.aii.af.ispeak.svc > hard reference to service applocking.
    Service tcsecdestinationsservice > hard reference to service tcsecsecurestorageservice.
    Service dsr > hard reference to service security.
    Service keystore > hard reference to service security.
    Service applocking > hard reference to service security.
    Service tclmctcculservice_sda > hard reference to service jmx.
    Service monitor > hard reference to service jmx.
    Service com.sap.security.core.ume.service > service com.sap.security.core.ume.service start method invoked.
    Service com.sap.aii.adapter.bc.svc > hard reference to service com.sap.aii.af.cpa.svc.
    Service com.sap.aii.adapter.rfc.svc > hard reference to service com.sap.aii.af.cpa.svc.
    Service tc.monitoring.logviewer > hard reference to service jmx.
    Service apptracing > hard reference to service jmx.
    Service com.sap.aii.af.ms.svc > hard reference to service com.sap.aii.af.svc.
    Service com.sap.aii.af.cpa.svc > hard reference to service sld.
    Service shell > hard reference to interface security.
    Service tcsecwssecservice > hard reference to service tcsecsecurestorageservice.
    Service com.sap.aii.adapter.mail.svc > hard reference to service com.sap.aii.af.cpa.svc.
    Service servlet_jsp > hard reference to interface security.
    Service com.sap.aii.adapter.file.svc > hard reference to service com.sap.aii.af.cpa.svc.
    Service classload > hard reference to service security.
    Service basicadmin > hard reference to service jmx.
    Service com.sap.aii.adapter.xi.svc > hard reference to service com.sap.aii.af.cpa.svc.
    #1.5#0015C588AED4000000000018000034D8000445790BF36AF2#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###43 services have timed out.#
    #1.5#0015C588AED400000000001A000034D8000445790BF36CBF#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#0015C588AED400000000001C000034D8000445790BF36E70#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.marketplace.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#0015C588AED400000000001E000034D8000445790BF3702D#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service ejb has timed out > hard reference to interface security.#
    #1.5#0015C588AED4000000000020000034D8000445790BF371D8#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.security.service has timed out > hard reference to service keystore.#
    #1.5#0015C588AED4000000000022000034D8000445790BF3737F#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service ssl has timed out > hard reference to service keystore.#
    #1.5#0015C588AED4000000000024000034D8000445790BF3752A#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.jms.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#0015C588AED4000000000026000034D8000445790BF376D2#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service adminadapter has timed out > hard reference to service jmx.#
    #1.5#0015C588AED4000000000028000034D8000445790BF3787A#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecsecurestorage~service has timed out > hard reference to service keystore.#
    #1.5#0015C588AED400000000002A000034D8000445790BF37ACC#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service pmi has timed out > hard reference to service tcsecdestinations~service.#
    #1.5#0015C588AED400000000002C000034D8000445790BF37D4C#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service security has timed out > hard reference to service com.sap.security.core.ume.service.#
    #1.5#0015C588AED400000000002E000034D8000445790BF37EF7#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service jms_provider has timed out > hard reference to service security.#
    #1.5#0015C588AED4000000000030000034D8000445790BF380A1#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service sld has timed out > hard reference to service tcsecsecurestorage~service.#
    #1.5#0015C588AED4000000000032000034D8000445790BF3824E#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service jmx has timed out > hard reference to interface security.#
    #1.5#0015C588AED4000000000034000034D8000445790BF383F8#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service rfcengine has timed out > hard reference to service ejb.#
    #1.5#0015C588AED4000000000036000034D8000445790BF385A7#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecsaml~service has timed out > hard reference to service adminadapter.#
    #1.5#0015C588AED4000000000038000034D8000445790BF38754#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service telnet has timed out > hard reference to service shell.#
    #1.5#0015C588AED400000000003A000034D8000445790BF38903#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.jdbc.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#0015C588AED400000000003C000034D8000445790BF38AB4#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tclmctcculculservice_sda has timed out > hard reference to service jmx.#
    #1.5#0015C588AED400000000003E000034D8000445790BF38C5D#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service webdynpro has timed out > hard reference to interface shell.#
    #1.5#0015C588AED4000000000040000034D8000445790BF38E07#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecvsiservice has timed out > hard reference to service tcsecdestinationsservice.#
    #1.5#0015C588AED4000000000042000034D8000445790BF38FD6#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tceCATTPingservice has timed out > hard reference to interface shell.#
    #1.5#0015C588AED4000000000044000034D8000445790BF3918B#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.ispeak.svc has timed out > hard reference to service applocking.#
    #1.5#0015C588AED4000000000046000034D8000445790BF3938A#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecdestinationsservice has timed out > hard reference to service tcsecsecurestorageservice.#
    #1.5#0015C588AED4000000000048000034D8000445790BF3953F#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service dsr has timed out > hard reference to service security.#
    #1.5#0015C588AED400000000004A000034D8000445790BF396EC#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service keystore has timed out > hard reference to service security.#
    #1.5#0015C588AED400000000004C000034D8000445790BF398A2#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service applocking has timed out > hard reference to service security.#
    #1.5#0015C588AED400000000004E000034D8000445790BF39B53#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tclmctcculservice_sda has timed out > hard reference to service jmx.#
    #1.5#0015C588AED4000000000050000034D8000445790BF39CFE#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service monitor has timed out > hard reference to service jmx.#
    #1.5#0015C588AED4000000000052000034D8000445790BF39EAB#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.security.core.ume.service has timed out > service com.sap.security.core.ume.service start method invoked.#
    #1.5#0015C588AED4000000000054000034D8000445790BF3A068#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.bc.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#0015C588AED4000000000056000034D8000445790BF3A217#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.rfc.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#0015C588AED4000000000058000034D8000445790BF3A3CD#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tc.monitoring.logviewer has timed out > hard reference to service jmx.#
    #1.5#0015C588AED400000000005A000034D8000445790BF3A5EC#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service apptracing has timed out > hard reference to service jmx.#
    #1.5#0015C588AED400000000005C000034D8000445790BF3A7B3#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.ms.svc has timed out > hard reference to service com.sap.aii.af.svc.#
    #1.5#0015C588AED400000000005E000034D8000445790BF3A967#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.cpa.svc has timed out > hard reference to service sld.#
    #1.5#0015C588AED4000000000060000034D8000445790BF3AB0C#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service shell has timed out > hard reference to interface security.#
    #1.5#0015C588AED4000000000062000034D8000445790BF3ACBC#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecwssecservice has timed out > hard reference to service tcsecsecurestorageservice.#
    #1.5#0015C588AED4000000000064000034D8000445790BF3AE81#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.mail.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#0015C588AED4000000000066000034D8000445790BF3B03B#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service servlet_jsp has timed out > hard reference to interface security.#
    #1.5#0015C588AED4000000000068000034D8000445790BF3B2D1#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.file.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#0015C588AED400000000006A000034D8000445790BF3B47F#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service classload has timed out > hard reference to service security.#
    #1.5#0015C588AED400000000006C000034D8000445790BF3B628#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service basicadmin has timed out > hard reference to service jmx.#
    #1.5#0015C588AED400000000006E000034D8000445790BF3B7D3#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.xi.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#0015C588AED4000000000070000034D8000445790BF3BA67#1202286100750#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: 5 core services have timed out [adminadapter; security; jmx; com.sap.security.core.ume.service; basicadmin].#

    Hello Sir,
    I am also having the similar prblem after upgrading the AIX 5.3 TL 5 to TL6.
    I would really like to know what you did to solve you problem, even though our scenario is a little different.

  • WAS not getting started!

    Hi,
    my system s (sap bw NW04 platform) SAP web application server is not getting started.It is of 6.40 version. it always stays in yellow colour even after 1 day!
    i had found that in process list, dispatcher is stopped!
    i am pasting the log at developer trace ! please go through it and tell me what could be the remedy!
    trc file: "dev_disp", trc level: 1, release: "640"
    Mon Nov 06 18:26:06 2006
    kernel runs with dp version 128000(ext=102000) (@(#) DPLIB-INT-VERSION-128000-UC)
    length of sys_adm_ext is 524 bytes
    systemid   560 (PC with Windows NT)
    relno      6400
    patchlevel 0
    patchno    43
    intno      20020600
    make:      multithreaded, Unicode
    pid        1252
    ***LOG Q00=> DpSapEnvInit, DPStart (00 1252) [dpxxdisp.c   1100]
         shared lib "dw_xml.dll" version 43 successfully loaded
         shared lib "dw_xtc.dll" version 43 successfully loaded
         shared lib "dw_stl.dll" version 43 successfully loaded
         shared lib "dw_gui.dll" version 43 successfully loaded
    Mon Nov 06 18:26:12 2006
    WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
    ***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  3886]
    MtxInit: -2 0 0
    DpSysAdmExtInit: ABAP is active
    DpSysAdmExtInit: JAVA is not active
    DpShMCreate: sizeof(wp_adm)          10528     (1316)
    DpShMCreate: sizeof(tm_adm)          2780232     (13832)
    DpShMCreate: sizeof(wp_ca_adm)          24000     (80)
    DpShMCreate: sizeof(appc_ca_adm)     8000     (80)
    DpShMCreate: sizeof(comm_adm)          290000     (580)
    DpShMCreate: sizeof(vmc_adm)          0     (372)
    DpShMCreate: sizeof(wall_adm)          (38456/34360/64/184)
    DpShMCreate: SHM_DP_ADM_KEY          (addr: 069F0040, size: 3192688)
    DpShMCreate: allocated sys_adm at 069F0040
    DpShMCreate: allocated wp_adm at 069F1B58
    DpShMCreate: allocated tm_adm_list at 069F4478
    DpShMCreate: allocated tm_adm at 069F44A0
    DpShMCreate: allocated wp_ca_adm at 06C9B0E8
    DpShMCreate: allocated appc_ca_adm at 06CA0EA8
    DpShMCreate: allocated comm_adm_list at 06CA2DE8
    DpShMCreate: allocated comm_adm at 06CA2E00
    DpShMCreate: allocated vmc_adm_list at 06CE9AD0
    DpShMCreate: system runs without vmc_adm
    DpShMCreate: allocated ca_info at 06CE9AF8
    DpShMCreate: allocated wall_adm at 06CE9B00
    MBUF state OFF
    Mon Nov 06 18:26:13 2006
    EmInit: MmSetImplementation( 2 ).
    <ES> client 0 initializing ....
    <ES> InitFreeList
    <ES> block size is 1024 kByte.
    Using implementation flat
    <EsNT> Memory Reset disabled as NT default
    <ES> 594 blocks reserved for free list.
    ES initialized.
    Mon Nov 06 18:26:18 2006
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 2768
      argv[0] = C:\usr\sap\J2E\DVEBMGS00/j2ee/os_libs/jcontrol.exe
      argv[1] = C:\usr\sap\J2E\DVEBMGS00/j2ee/os_libs/jcontrol.exe
      argv[2] = pf=C:\usr\sap\J2E\SYS\profile\J2E_DVEBMGS00_RKOTTUR
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=1164
      argv[5] = -DLISTEN_PORT=1165
      argv[6] = -DSAPSYSTEM=00
      argv[7] = -DSAPSYSTEMNAME=J2E
      argv[8] = -DSAPMYNAME=RKOTTUR_J2E_00
      argv[9] = -DSAPPROFILE=C:\usr\sap\J2E\SYS\profile\J2E_DVEBMGS00_RKOTTUR
      argv[10] = -DFRFC_FALLBACK=ON
      argv[11] = -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 ( 2.6.1 2.6 4.0) [dpxxdisp.c   1462]
    Mon Nov 06 18:26:19 2006
    ***LOG Q0K=> DpMsAttach, mscon ( RKOTTUR) [dpxxdisp.c   9736]
    Mon Nov 06 18:26:21 2006
    CCMS: start to initalize 3.X shared alert area (first segment).
    DpMsgAdmin: Set release to 6400, patchlevel 0
    MBUF state PREPARED
    MBUF component UP
    DpMBufHwIdSet: set Hardware-ID
    ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1025]
    DpMsgAdmin: Set patchno for this platform to 43
    Release check o.K.
    Mon Nov 06 18:26:23 2006
    DpJ2eeLogin: j2ee state = CONNECTED
    Mon Nov 06 18:26:43 2006
    ***LOG Q0I=> NiPRead: recv (10054: WSAECONNRESET: Connection reset by peer) [ninti.c 777]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=2768)
    ERROR => DpProcKill: kill failed [dpntdisp.c   433]
    DpIJ2eeShutdown: j2ee state = SHUTDOWN
    Mon Nov 06 18:27:00 2006
    ERROR => W0 (pid 2776) died [dpxxdisp.c   12187]
    ERROR => W1 (pid 2784) died [dpxxdisp.c   12187]
    my types changed after wp death/restart 0xbf --> 0xbe
    ERROR => W2 (pid 2792) died [dpxxdisp.c   12187]
    my types changed after wp death/restart 0xbe --> 0xbc
    ERROR => W3 (pid 2800) died [dpxxdisp.c   12187]
    my types changed after wp death/restart 0xbc --> 0xb8
    ERROR => W4 (pid 2808) died [dpxxdisp.c   12187]
    ERROR => W5 (pid 2816) died [dpxxdisp.c   12187]
    my types changed after wp death/restart 0xb8 --> 0xb0
    ERROR => W6 (pid 2824) died [dpxxdisp.c   12187]
    my types changed after wp death/restart 0xb0 --> 0xa0
    ERROR => W7 (pid 2832) died [dpxxdisp.c   12187]
    my types changed after wp death/restart 0xa0 --> 0x80
    DP_FATAL_ERROR => DpWPCheck: no more work processes
    DISPATCHER EMERGENCY SHUTDOWN ***
    increase tracelevel of WPs
    killing W0-2776 (SIGUSR2)
    ERROR => DpWpKill(2776, SIGUSR2) failed [dpxxtool.c   2468]
    killing W1-2784 (SIGUSR2)
    ERROR => DpWpKill(2784, SIGUSR2) failed [dpxxtool.c   2468]
    killing W2-2792 (SIGUSR2)
    ERROR => DpWpKill(2792, SIGUSR2) failed [dpxxtool.c   2468]
    killing W3-2800 (SIGUSR2)
    ERROR => DpWpKill(2800, SIGUSR2) failed [dpxxtool.c   2468]
    killing W4-2808 (SIGUSR2)
    ERROR => DpWpKill(2808, SIGUSR2) failed [dpxxtool.c   2468]
    killing W5-2816 (SIGUSR2)
    ERROR => DpWpKill(2816, SIGUSR2) failed [dpxxtool.c   2468]
    killing W6-2824 (SIGUSR2)
    ERROR => DpWpKill(2824, SIGUSR2) failed [dpxxtool.c   2468]
    killing W7-2832 (SIGUSR2)
    ERROR => DpWpKill(2832, SIGUSR2) failed [dpxxtool.c   2468]
    NiWait: sleep (10000 msecs) ...
    NiISelect: timeout 10000 ms
    NiISelect: maximum fd=437
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Mon Nov 06 18:27:10 2006
    NiISelect: TIMEOUT occured (10000 ms)
    dump system status
    Workprocess Table (long)               Mon Nov 06 12:57:10 2006
    ========================
    No Ty. Pid      Status  Cause Start Err Sem CPU    Time  Program  Cl  User         Action                    Table
    0 DIA     2776 Ended         no      1   0             0                                                             
    1 DIA     2784 Ended         no      1   0             0                                                             
    2 UPD     2792 Ended         no      1   0             0                                                             
    3 ENQ     2800 Ended         no      1   0             0                                                             
    4 BTC     2808 Ended         no      1   0             0                                                             
    5 BTC     2816 Ended         no      1   0             0                                                             
    6 SPO     2824 Ended         no      1   0             0                                                             
    7 UP2     2832 Ended         no      1   0             0                                                             
    Dispatcher Queue Statistics               Mon Nov 06 12:57:10 2006
    ===========================
    --------++++--
    +
    Typ
    now
    high
    max
    writes
    reads
    --------++++--
    +
    NOWP
    0
    3
    2000
    10
    10
    --------++++--
    +
    DIA
    5
    5
    2000
    5
    0
    --------++++--
    +
    UPD
    0
    0
    2000
    0
    0
    --------++++--
    +
    ENQ
    0
    0
    2000
    0
    0
    --------++++--
    +
    BTC
    0
    0
    2000
    0
    0
    --------++++--
    +
    SPO
    0
    0
    2000
    0
    0
    --------++++--
    +
    UP2
    0
    0
    2000
    0
    0
    --------++++--
    +
    max_rq_id          13
    wake_evt_udp_now     0
    wake events           total     9,  udp     7 ( 77%),  shm     2 ( 22%)
    since last update     total     9,  udp     7 ( 77%),  shm     2 ( 22%)
    Dump of tm_adm structure:               Mon Nov 06 12:57:10 2006
    =========================
    Term    uid  man user    term   lastop  mod wp  ta   a/i (modes)
    Workprocess Comm. Area Blocks               Mon Nov 06 12:57:10 2006
    =============================
    Slots: 300, Used: 1, Max: 0
    --------++--
    +
    id
    owner
    pid
    eyecatcher
    --------++--
    +
    0
    DISPATCHER
    -1
    WPCAAD000
    NiWait: sleep (5000 msecs) ...
    NiISelect: timeout 5000 ms
    NiISelect: maximum fd=437
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Mon Nov 06 18:27:15 2006
    NiISelect: TIMEOUT occured (5000 ms)
    Shutdown server ...
    DpJ2eeDisableRestart
    DpModState: buffer in state MBUF_PREPARED
    NiBufSend starting
    NiIWrite: write 110, 1 packs, MESG_IO, hdl 5, data complete
    MsINiWrite: sent 110 bytes
    MsIModState: change state to SHUTDOWN
    DpModState: change server state from STARTING to SHUTDOWN
    Switch off Shared memory profiling
    ShmProtect( 57, 3 )
    ShmProtect(SHM_PROFILE, SHM_PROT_RW
    ShmProtect( 57, 1 )
    ShmProtect(SHM_PROFILE, SHM_PROT_RD
    DpWakeUpWps: wake up all wp's
    Stop work processes...
    Stop gateway
    killing process (2740) (SOFT_KILL)
    Stop icman
    killing process (2764) (SOFT_KILL)
    Terminate gui connections
    [DpProcDied] Process lives  (PID:2740  HANDLE:420)
    waiting for termination of gateway
    NiWait: sleep (1000 msecs) ...
    NiISelect: timeout 1000 ms
    NiISelect: maximum fd=437
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Mon Nov 06 18:27:16 2006
    NiISelect: TIMEOUT occured (1000 ms)
    [DpProcDied] Process died  (PID:2740  HANDLE:420)
    [DpProcDied] Process died  (PID:2764  HANDLE:412)
    DpHalt: cancel all lcom connections
    MPI CancelAll 2 -> 0
    MPI DeleteAll 2 -> 0
    [DpProcDied] Process died  (PID:2768  HANDLE:388)
    NiIMyHostName: hostname = 'RKOTTUR'
    AdGetSelfIdentRecord: >                                                                           <
    AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
    AdCvtRecToExt: opcode 4 (AD_STARTSTOP), ser 0, ex 0, errno 0
    DpConvertRequest: net size = 163 bytes
    NiBufSend starting
    NiIWrite: write 562, 1 packs, MESG_IO, hdl 5, data complete
    MsINiWrite: sent 562 bytes
    send msg (len 110+452) to name          -, type 4, key -
    detach from message server
    ***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c   9962]
    NiBufSend starting
    NiIWrite: write 110, 1 packs, MESG_IO, hdl 5, data complete
    MsINiWrite: sent 110 bytes
    MsIDetach: send logout to msg_server
    MsIDetach: call exit function
    DpMsShutdownHook called
    NiSelClear: removed hdl 5 from selectset
    MBUF state OFF
    AdGetSelfIdentRecord: >                                                                           <
    AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
    AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
    AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
    blks_in_queue/wp_ca_blk_no/wp_max_no = 1/300/8
    LOCK WP ca_blk 1
    make DISP owner of wp_ca_blk 1
    DpRqPutIntoQueue: put request into queue (reqtype 1, prio LOW, rq_id 19)
    MBUF component DOWN
    NiBufClose: clear extensions for hdl 5
    NiBufSetStat: bufstat of hdl 5 changed from OK to OFF
    NiICloseHandle: shutdown and close hdl 5 / socket 316
    MsIDetach: detach MS-system
    EsCleanup ....
    ***LOG Q05=> DpHalt, DPStop ( 1252) [dpxxdisp.c   8495]
    Good Bye .....
    Thank you,
    Ravi

    Hello Ravi,
    Do you mean that the web dispatcher is not running or the J2EE dispatcher process. To me it looks more like that the J2EE dispatcher is stopped so you should look for errors in dev_dispatcher and std_dispatcher.out files.
    Best Regards
    Vyara

  • Db Console service  not getting started

    Hello,
    I am trying to start DB console from services and also from the command prompt.Its not getting start from both.
    The database is up and running. Even the Isqlplus service is running successfully. Any idea why the DB Console could not be getting started.
    Regards,
    Faiz
    [email protected]

    Hi,
    I have this same issue of not able to start my Oracle 10g DBConsole on my windows xp machine.
    this is what happened. the dbconsole was starting up fine until we had to change the IP address of our systems.
    from the moment we changed IP address of our systems, the dbconsole is not functioning at all.
    i have even update the hosts file under window system32 folder. but still dbconsole is not starting.
    initially i was getting error as ORACLE_SID not set. so i set the environment variable. and then when i try to start dbconsole at command prompt as
    c:>emctl start dbconsole
    i get error as
    "OC4J Configuration issue. C:\oracle\product\10.2.0\db_1/oc4j/j2ee/OC4J_DBConsole
    _DECK_AAORCL not found."
    Can someone help me solve this.
    Thanks,
    Philip.

  • J2EE Engine cannot be started

    Hi All,
    My j2ee engine is not starting. Kindly assist me regarding this. Kindly find below log.
    Where to check this user.
    stdout/stderr redirect
    node name   : server0
    pid         : 229540
    system name : GSQ
    system nr.  : 02
    started at  : Tue Feb 21 18:21:43 2012
    SAP J2EE Engine Version 7.00   PatchLevel 66803.450 is starting...
    Loading: LogManager ... 623 ms.
    Loading: PoolManager ... 2 ms.
    Loading: ApplicationThreadManager ... 3568 ms.
    Loading: ThreadManager ... 28 ms.
    Loading: IpVerificationManager ... 12 ms.
    Loading: ClassLoaderManager ... 20 ms.
    Loading: ClusterManager ... 307 ms.
    Loading: LockingManager ... 84 ms.
    Loading: ConfigurationManager ... 1674 ms.
    Loading: LicensingManager ... 19 ms.
    Loading: CacheManager ... 127 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service DQE started. (37 ms).
      Service memory started. (62 ms).
      Service cafeuodi~mnuacc started. (2 ms).
      Service cross started. (138 ms).
      Service file started. (139 ms).
      Service timeout started. (147 ms).
      Service runtimeinfo started. (91 ms).
      Service trex.service started. (170 ms).
      Service cafeucc~api started. (196 ms).
      Service userstore started. (20 ms).
      Service jmx_notification started. (36 ms).
      Service p4 started. (215 ms).
      Service classpath_resolver started. (49 ms).
    <af type="nursery" id="1" timestamp="Feb 21 18:23:25 2012" intervalms="0.000">
      <minimum requested_bytes="96" />
      <time exclusiveaccessms="0.209" />
      <nursery freebytes="0" totalbytes="209715200" percent="0" />
      <tenured freebytes="1724301920" totalbytes="1728053248" percent="99" >
        <soa freebytes="1637899872" totalbytes="1641651200" percent="99" />
        <loa freebytes="86402048" totalbytes="86402048" percent="100" />
      </tenured>
      <gc type="scavenger" id="1" totalid="1" intervalms="0.000">
        <flipped objectcount="283441" bytes="21271320" />
        <tenured objectcount="0" bytes="0" />
        <refs_cleared soft="685" weak="1" phantom="0" />
        <finalization objectsqueued="1462" />
        <scavenger tiltratio="50" />
        <nursery freebytes="188305568" totalbytes="209715200" percent="89" tenureage="10" />
        <tenured freebytes="1724301920" totalbytes="1728053248" percent="99" >
          <soa freebytes="1637899872" totalbytes="1641651200" percent="99" />
          <loa freebytes="86402048" totalbytes="86402048" percent="100" />
        </tenured>
        <time totalms="101.150" />
      </gc>
      <nursery freebytes="188303520" totalbytes="209715200" percent="89" />
      <tenured freebytes="1724301920" totalbytes="1728053248" percent="99" >
        <soa freebytes="1637899872" totalbytes="1641651200" percent="99" />
        <loa freebytes="86402048" totalbytes="86402048" percent="100" />
      </tenured>
      <time totalms="102.710" />
    </af>
    <af type="nursery" id="2" timestamp="Feb 21 18:23:28 2012" intervalms="3381.768">
      <minimum requested_bytes="32552" />
      <time exclusiveaccessms="0.203" />
      <nursery freebytes="16072" totalbytes="209715200" percent="0" />
      <tenured freebytes="1724285064" totalbytes="1728053248" percent="99" >
        <soa freebytes="1637883016" totalbytes="1641651200" percent="99" />
        <loa freebytes="86402048" totalbytes="86402048" percent="100" />
      </tenured>
      <gc type="scavenger" id="2" totalid="2" intervalms="3383.004">
        <flipped objectcount="405653" bytes="30029056" />
        <tenured objectcount="0" bytes="0" />
        <refs_cleared soft="983" weak="0" phantom="0" />
        <finalization objectsqueued="901" />
        <scavenger tiltratio="50" />
        <nursery freebytes="179257688" totalbytes="209715200" percent="85" tenureage="10" />
        <tenured freebytes="1724285064" totalbytes="1728053248" percent="99" >
          <soa freebytes="1637883016" totalbytes="1641651200" percent="99" />
          <loa freebytes="86402048" totalbytes="86402048" percent="100" />
        </tenured>
        <time totalms="56.165" />
      </gc>
      <nursery freebytes="179225136" totalbytes="209715200" percent="85" />
      <tenured freebytes="1724285064" totalbytes="1728053248" percent="99" >
        <soa freebytes="1637883016" totalbytes="1641651200" percent="99" />
        <loa freebytes="86402048" totalbytes="86402048" percent="100" />
      </tenured>
      <time totalms="57.048" />
    </af>
      Service log_configurator started. (8042 ms).
      Service locking started. (9 ms).
      Service http started. (283 ms).
    <af type="nursery" id="3" timestamp="Feb 21 18:23:31 2012" intervalms="2407.476">
      <minimum requested_bytes="1208" />
      <time exclusiveaccessms="0.309" />
      <nursery freebytes="0" totalbytes="209715200" percent="0" />
      <tenured freebytes="1724206264" totalbytes="1728053248" percent="99" >
        <soa freebytes="1637804216" totalbytes="1641651200" percent="99" />
        <loa freebytes="86402048" totalbytes="86402048" percent="100" />
      </tenured>
      <gc type="scavenger" id="3" totalid="3" intervalms="2408.194">
        <flipped objectcount="554169" bytes="41224280" />
        <tenured objectcount="0" bytes="0" />
        <refs_cleared soft="952" weak="0" phantom="0" />
        <finalization objectsqueued="1316" />
        <scavenger tiltratio="50" />
        <nursery freebytes="167984600" totalbytes="209715200" percent="80" tenureage="10" />
        <tenured freebytes="1724206264" totalbytes="1728053248" percent="99" >
          <soa freebytes="1637804216" totalbytes="1641651200" percent="99" />
          <loa freebytes="86402048" totalbytes="86402048" percent="100" />
        </tenured>
        <time totalms="76.821" />
      </gc>
      <nursery freebytes="167983392" totalbytes="209715200" percent="80" />
      <tenured freebytes="1724206264" totalbytes="1728053248" percent="99" >
        <soa freebytes="1637804216" totalbytes="1641651200" percent="99" />
        <loa freebytes="86402048" totalbytes="86402048" percent="100" />
      </tenured>
      <time totalms="78.249" />
    </af>
      Service naming started. (801 ms).
      Service failover started. (69 ms).
      Service javamail started. (207 ms).
      Service ts started. (173 ms).
      Service appclient started. (192 ms).
      Service licensing started. (47 ms).
      Service jmsconnector started. (308 ms).
      Service connector started. (280 ms).
      Service iiop started. (325 ms).
      Service webservices started. (749 ms).
    <af type="nursery" id="4" timestamp="Feb 21 18:23:33 2012" intervalms="2262.903">
      <minimum requested_bytes="32" />
      <time exclusiveaccessms="0.192" />
      <nursery freebytes="0" totalbytes="209715200" percent="0" />
      <tenured freebytes="1724111408" totalbytes="1728053248" percent="99" >
        <soa freebytes="1637709360" totalbytes="1641651200" percent="99" />
        <loa freebytes="86402048" totalbytes="86402048" percent="100" />
      </tenured>
      <gc type="scavenger" id="4" totalid="4" intervalms="2264.002">
        <flipped objectcount="614335" bytes="45869976" />
        <tenured objectcount="0" bytes="0" />
        <refs_cleared soft="35" weak="0" phantom="0" />
        <finalization objectsqueued="7" />
        <scavenger tiltratio="50" />
        <nursery freebytes="163275192" totalbytes="209715200" percent="77" tenureage="10" />
        <tenured freebytes="1724111408" totalbytes="1728053248" percent="99" >
          <soa freebytes="1637709360" totalbytes="1641651200" percent="99" />
          <loa freebytes="86402048" totalbytes="86402048" percent="100" />
        </tenured>
        <time totalms="78.029" />
      </gc>
      <nursery freebytes="163273144" totalbytes="209715200" percent="77" />
      <tenured freebytes="1724111408" totalbytes="1728053248" percent="99" >
        <soa freebytes="1637709360" totalbytes="1641651200" percent="99" />
        <loa freebytes="86402048" totalbytes="86402048" percent="100" />
      </tenured>
      <time totalms="79.277" />
    </af>
      Service deploy started. (10986 ms).
      Service com.sap.portal.runtime.config.kmreadonly started. (11 ms).
      Service configuration started. (39 ms).
      Service MigrationService started. (69 ms).
      Service bimmrdeployer started. (17 ms).
      Service dbpool started. (1237 ms).
      Service UT started. (14 ms).
      Service cafeugpmailcf started. (53 ms).
    Feb 21, 2012 6:23:37 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_78] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "Password logon no longer possible - too many failed attempts". This message is critical if it appears during the startup of the AS Java.
    Feb 21, 2012 6:23:37 PM  ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_78] 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: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Password logon no longer possible - too many failed attempts
         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)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Password logon no longer possible - too many failed attempts
         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:446)
         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
    com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Password logon no longer possible - too many failed attempts
         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)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Password logon no longer possible - too many failed attempts
         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:446)
         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
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Feb 21, 2012 6:23:37 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_78] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    </verbosegc>

    I would recommand to login as <SID>adm to your central instance and go to path usr\sap\<systemid>\<system instance>\J2EE\configtool
    then configtool.bat and start it.
    also access this tool only to make password reset
    Refer thread[http://forums.sdn.sap.com/thread.jspa?threadID=2107011&tstart=15] for setting env variable
    Regards,
    Edited by: Rupali B on Feb 22, 2012 2:09 PM

Maybe you are looking for

  • Web Service (SSL) and certificates (keytool) with INternet Explorer

    Hi, Followed this steps http://www.grallandco.com/blog/archives/2006/10/using_htts_with.html to have a secure SSL WEb service (with client authorization). Tested from Jdeveloper it worked O.K. Now I would like to test it with Internet explorer, but n

  • ABAP KEYWORD DOCUMENTATION

    Hi, The link which I was using for ABAP KEYWORD DOCUMENTATION does not work anymore. http://help.sap.com/abapdocu/en/ABENABAP.htm Does anyone know the correct link? Thanks and Regards, Reena

  • Not able to start Listener in window 7

    Please help. I installed Oracle 10g (10.2.0). After installation I was able to connect to DB and everything was ruuning smootly. But when I log into my computer, one/two day later: listener was not up and I could not restart it as well. Error Mssg: T

  • Elke's Intro

    I am quite honored to share in the ranks of such intelligent Oracle Applications Technologists. And, I like, Debra and Floyd before me find this intro a bit embarrassing. So, anyway, here's the part about me-.. I have worked with Oracle Technology si

  • HT1338 Viewing videos and adobe flashplayer

    I have never encountered any issues with my Mac until recently.  I now for some reason have a green below my menu toolbar that shows the bookmark symbol and other sites such as apple, yahoo, etc.  This green box says McAfee and has a check mark in it