J2EE engine will not start

Hi experts.
J2EE engine will not start.  Below is the lower section of the trace.  I'd appreciate help with interpretation as I am a NW newby.
I just installed an J2EE key in tcode SLICENSE for our developer's subscription NW 7.0 instance.  Another thread implied installing the J2EE key in visual administrator, but how is that possible if the J2EE engine is not running?  I cannot establish a connection.
Thanks,
Aron
DpJ2eeStart: j2ee state = STARTED
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c   1633]
***LOG Q0K=> DpMsAttach, mscon ( S-SAPDEV01) [dpxxdisp.c   11822]
DpStartStopMsg: send start message (myname is >S-SAPDEV01_DS1_00                       <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 60000000 for monitoring segment.
Tue Jul 08 13:43:35 2008
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1050]
DpMsgAdmin: Set patchno for this platform to 146
Release check o.K.
DpJ2eeLogin: j2ee state = CONNECTED
Tue Jul 08 13:43:37 2008
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
ERROR => NiIRead: SiRecv failed for hdl 4 / sock 236
    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:4027) [nixxi.cpp    4424]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=5508)
ERROR => DpProcKill: kill failed [dpntdisp.c   371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
MBUF state ACTIVE
Tue Jul 08 13:43:38 2008
DpModState: change server state from STARTING to ACTIVE
Tue Jul 08 13:44:14 2008
J2EE server info
  start = TRUE
  state = STARTED
  pid = 3412
  argv[0] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
  argv[1] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
  argv[2] = pf=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=64998
  argv[5] = -DSAPSYSTEM=00
  argv[6] = -DSAPSYSTEMNAME=DS1
  argv[7] = -DSAPMYNAME=S-SAPDEV01_DS1_00
  argv[8] = -DSAPPROFILE=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
  argv[9] = -DFRFC_FALLBACK=ON
  argv[10] = -DFRFC_FALLBACK_HOST=localhost
  start_lazy = 0
  start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Tue Jul 08 13:44:17 2008
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
ERROR => NiIRead: SiRecv failed for hdl 6 / sock 668
    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:4095) [nixxi.cpp    4424]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=3412)
ERROR => DpProcKill: kill failed [dpntdisp.c   371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Tue Jul 08 13:44:34 2008
J2EE server info
  start = TRUE
  state = STARTED
  pid = 5156
  argv[0] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
  argv[1] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
  argv[2] = pf=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=64997
  argv[5] = -DSAPSYSTEM=00
  argv[6] = -DSAPSYSTEMNAME=DS1
  argv[7] = -DSAPMYNAME=S-SAPDEV01_DS1_00
  argv[8] = -DSAPPROFILE=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
  argv[9] = -DFRFC_FALLBACK=ON
  argv[10] = -DFRFC_FALLBACK_HOST=localhost
  start_lazy = 0
  start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Tue Jul 08 13:44:37 2008
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
ERROR => NiIRead: SiRecv failed for hdl 4 / sock 208
    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:4105) [nixxi.cpp    4424]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=5156)
ERROR => DpProcKill: kill failed [dpntdisp.c   371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Tue Jul 08 13:44:54 2008
J2EE server info
  start = TRUE
  state = STARTED
  pid = 6072
  argv[0] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
  argv[1] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
  argv[2] = pf=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=64996
  argv[5] = -DSAPSYSTEM=00
  argv[6] = -DSAPSYSTEMNAME=DS1
  argv[7] = -DSAPMYNAME=S-SAPDEV01_DS1_00
  argv[8] = -DSAPPROFILE=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
  argv[9] = -DFRFC_FALLBACK=ON
  argv[10] = -DFRFC_FALLBACK_HOST=localhost
  start_lazy = 0
  start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Tue Jul 08 13:44:57 2008
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
ERROR => NiIRead: SiRecv failed for hdl 6 / sock 200
    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:4117) [nixxi.cpp    4424]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=6072)
ERROR => DpProcKill: kill failed [dpntdisp.c   371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN

Actually it was to remove compression, not to allow archiving.  Sorry!
We're using Windows Server 2003.  Right-click on a folder or file, choose Properties.  Click on the Advanced button on the General tab.  Remove the check box for Compress to save disk space, click ok.  When you click on Apply there will be a prompt to apply just to that folder only or on subfolders and files as well.
When compression is applied, the text for the folder turns blue.  When is not applied, the text is black.

Similar Messages

  • J2EE Engine does not start

    Hi All.
    I installed a Dialog instance.
    After the installation of the license key on the central instance, the dialog J2EE Engine does not start anymore.
    Here it is the std_server0.out log:
    stdout/stderr redirect
    node name   : server0
    pid         : 1298548
    system name : PRP
    system nr.  : 10
    started at  : Mon Sep  3 19:07:54 2007
    [Thr  1] Mon Sep  3 19:07:55 2007
    [Thr  1] MtxInit: -2 0 0
    JVMST080: verbosegc is enabled
    JVMST082: -verbose:gc output will be written to stderr
    ^MSAP J2EE Engine Version 7.00   PatchLevel is starting...
    ^M
    Loading: LogManager ... 1887 ms.
    Loading: PoolManager ... 3 ms.
    Loading: ApplicationThreadManager ... 452 ms.
    Loading: ThreadManager ... 428 ms.
    Loading: IpVerificationManager ... 16 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 392 ms.
    Loading: LockingManager ... 140 ms.
    Loading: ConfigurationManager ... 4656 ms.
    Loading: LicensingManager ... 28 ms.
    Loading: CacheManager ... 311 ms.
    Loading: ServiceManager ...
    <AF[1]: Allocation Failure. need 536 bytes, 0 ms since last AF>
    <AF[1]: managing allocation failure, action=0 (959472304/1073740288)>
      <GC(1): GC cycle started Mon Sep  3 19:08:13 2007
      <GC(1): freed 64170704 bytes, 95% free (1023643008/1073740288), in 136 ms>
      <GC(1): mark: 123 ms, sweep: 13 ms, compact: 0 ms>
      <GC(1): refs: soft 0 (age >= 32), weak 0, final 475, phantom 0>
    <AF[1]: completed in 159 ms>
    Loading services.:
      Service cross started. (72 ms).
      Service file started. (156 ms).
      Service memory started. (160 ms).
      Service userstore started. (24 ms).
      Service timeout started. (51 ms).
      Service runtimeinfo started. (8 ms).
      Service trex.service started. (90 ms).
      Service jmx_notification started. (77 ms).
      Service p4 started. (182 ms).
      Service classpath_resolver started. (99 ms).
      Service deploy started. (9491 ms).
      Service MigrationService started. (28 ms).
      Service bimmrdeployer started. (6 ms).
      Service log_configurator started. (21621 ms).
      Service locking started. (3 ms).
      Service http started. (772 ms).
      Service naming started. (1518 ms).
      Service failover started. (23 ms).
      Service appclient started. (29 ms).
      Service javamail started. (87 ms).
      Service ts started. (70 ms).
      Service jmsconnector started. (80 ms).
      Service licensing started. (10 ms).
      Service iiop started. (141 ms).
      Service connector started. (119 ms).
      Service configuration started. (31 ms).
      Service webservices started. (463 ms).
      Service dbpool started. (8765 ms).
    Sep 3, 2007 6:08:47 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] Fatal: Initialization of UME
    persistence adapter "PRIVATE_DATASOURCE" failed.
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME i
    nitialization failed.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization f
    ailed.
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:379)
            at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
            at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
            at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
            at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
            at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
            at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: null
            ume.db.connection_pool_type=SAP/BC_UME
            ume.db.connection_pool.j2ee.xatransactions_used=false
            ume.db.connection_pool.j2ee.is_unicode=FALSE
            ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
            at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:865)
            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)
            ... 6 more
    com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME i
    nitialization failed.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization f
    ailed.
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:379)
            at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
            at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
            at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
            at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
            at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
            at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: null
            ume.db.connection_pool_type=SAP/BC_UME
            ume.db.connection_pool.j2ee.xatransactions_used=false
            ume.db.connection_pool.j2ee.is_unicode=FALSE
            ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
            at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:865)
            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)
            ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Sep 3, 2007 6:08:47 PM              com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_54] Fatal: Critical shutdown was
    invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Anyone can help?
    Thanks,
    Marco

    Hi all,
    after some corrections, now the problem is changed.
    Here you can find the std_server0.out:
    <b>com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME i
    nitialization failed.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization f
    ailed.
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:379)
            at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
            at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
            at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
            at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
            at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
            at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed
    Connect_PM  TYPE=A ASHOST=SAPPRP-DB SYSNR=10 GWHOST=SAPPRP-DB GWSERV=sapgw10 PCS=1
    LOCATION    CPIC (TCP/IP) on local host with Unicode
    ERROR       partner 'SAPPRP-DB:sapgw10' not reached
    TIME        Fri Sep  7 15:01:11 2007
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2764
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       79
    ERRNO TEXT  A remote host refused an attempted connect operation.
    COUNTER     1
            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: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)
            ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Sep 7, 2007 2:01:11 PM              com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_55] Fatal: Critical shutdown was
    invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.</b>
    Thanks all,
    Marco

  • J2EE Engine is not starting

    Hi Experts,
    our J2EE Engine is not starting. After application restart in SAP MMC's process list for disp+work.exe the status is yellow (Running, Message Server connectionok, ...., J2EE: Some processes running). In the J2EE Process table the server0 is stopped. He tries to start it a couple of times, but after all it stopps with exitcode -11113. So I've checked the dev_trace, the entry was:
    [Thr 2376] Wed Nov 17 15:41:35 2010
    [Thr 2376] *** WARNING => INFO: Unknown property [instance.box.number=EI3DVEBMGS00chopin] [jstartxx.c   841]
    [Thr 2376] *** WARNING => INFO: Unknown property [instance.en.host=chopin] [jstartxx.c   841]
    [Thr 2376] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 2376] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    [Thr 1128] Wed Nov 17 15:45:06 2010
    [Thr 1128] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 1128] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 1128] JLaunchISetClusterId: set cluster id 2121050
    [Thr 1128] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 1128] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 5284] Wed Nov 17 15:45:34 2010
    [Thr 5284] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 5284] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
    [Thr 5900] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr 5900] **********************************************************************
    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 5900] JLaunchCloseProgram: good bye (exitcode = -11113)
    So I searched a little and found this [Thread|Restart of J2EE Engine] and modified the Heapsize. As our Server is a 32-bit machine I used this sizes:
    Max heap size: 1024M
    -Xms1024M // old size: 512
    -XX:PermSize=512M // old size: 128
    -XX:MaxPermSize=512M // old size: 128
    -XX:NewSize=320M // old size: 86
    -XX:MaxNewSize=320M // old size: 86
    The result was another error message in dev_trace:
    Error occurred during initialization of VM
    Could not reserve enough space for object heap
    [Thr 2396] JLaunchIAbortJava: abort hook is called
    [Thr 2396] **********************************************************************
    ERROR => The Java VM aborted unexpectedly.
    Please see SAP Note 943602 , section 'Java VM crashes'
    for additional information and trouble shooting.
    [Thr 2396] JLaunchCloseProgram: good bye (exitcode = -2)
    ok, so I changed the sizes again to:
    Max heao size: 1024M
    -XX:MaxPermSize=128M
    -XX:PermSize=512M
    -Xms512M
    -XX:NewSize=320M
    -XX:MaxNewSize=86M
    But there's still the same error occurring.
    Please, does someone has an idea how to solve this issue?
    Thanks in advance,
    Tan

    Hi Desiree,
    thank you for your posting. It's getting better, but it's still not running. I've set up the same password in client 001 and in the java ume and restarted the cluster. When starting the server0 is J2EE Process Table is starting framework, then starting apps, but after something about 9 minutes its restarting, but it seems not to have errors (in the J2EE Process Table there are restarts displayed but no errors. So its better than before where the server0 restarts after 30 seconds and stopps restarting after 3 errors and 4 restarts.
    But nows he's restarting and restarting....
    In TA SMICM there is the J2EE server operational TRUE which was not before. When checking the RFC Destination there comes the status "not ready" during Starting framework phase and status "Service unavailable" during starting apps phase.
    Here are some parts of the dev_trave:
    "VM Thread" prio=5 tid=0x003cec80 nid=0x1028 runnable
    "Suspend Checker Thread" prio=10 tid=0x011d8038 nid=0x7e0 runnable
    [Thr 4136] JLaunchIExitJava: exit hook is called (rc = 666)
    [Thr 4136] **********************************************************************
    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 4136] JLaunchCloseProgram: good bye (exitcode = 666)
    "VM Thread" prio=5 tid=0x003cec80 nid=0xb50 runnable
    "VM Periodic Task Thread" prio=10 tid=0x011dcc88 nid=0x9e4 waiting on condition
    "Suspend Checker Thread" prio=10 tid=0x011d8038 nid=0x748 runnable
    [Thr 2896] Thu Nov 18 09:13:33 2010
    [Thr 2896] JLaunchIExitJava: exit hook is called (rc = 666)
    [Thr 2896] **********************************************************************
    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 2896] JLaunchCloseProgram: good bye (exitcode = 666)
    ... and so on.
    I'm not sure whether I should change or add entries in the configtool.bat like in your link recommended. The Engine was running with this settings before.....

  • J2EE engine does not start correctly

    hi,
    after the installation of sap was v6.40 abap & j2ee, i cannot logon to the j2ee engine as described in the documentation. when i will access the engine by using a web browser, i get the following error message:
    "503: Service Unavailable"
    i had a look on the log files and found these messages in the server log file:
    java.rmi.RemoteException: Error occurred while starting applications; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Container EJBContainer is not active at the moment and it is not possible to startApp sap.com/com.sap.lcrabapapi.
         at ...
    there are more lines with error messages which seems to belong to the original problem with the ejbcontainer.
    can anyone tell me how to fix the errors?
    thanks in advance,
    michael keller

    Hi,
    See note: 535532
    Mid way through the note it says:
    You can then register the SAP J2EE Engine as a windows-service by using the SAP J2EE Engine Config Tool. Open a command prompt and change to the directory <J2EE Engine installation directory>configtool and run configtool.bat or start this tool via your Start-Menu "Tools->Config Tool" of the J2EE Server entry. Select at the left navigation area of this tool the entry "cluster/ server" the checkbox "Enabled" at the tabstrip "NT Service". Apply these settings by clicking on "File->Apply" at the menu. Do the same with the entry "cluster / dispatcher".
    After you have finished these steps you can register now the J2EE Engine as a windows service.
    Start service.exe, which is also located in the directory
    <J2EE Engine installation directory>configtool. It works with three
    parameters:
    Service.exe u2013install u2013 the service(s) is (are) registered as NT/2000 Service(s). For each specified cluster node, a separate service is generated. All services have startup mode automatic. To start the service(s), open the Control Panel ¨Services folder. Find the service in the list of available services (for example: SAP J2EE Server 1, SAP J2EE Dispatcher 1, SAP J2EE Server 2, and so on). Select it, and choose u201CStartu201D on the right-hand side. No u201CStartup Parametersu201D are needed for the service to run. The system starts the particular J2EE Engine 6.20 node in background mode. It can be used and administered as usual. The only difference is that the server does not run in a console window.
    There may be other notes along these lines.
    You should also check any notes on the setup of SAP in MSCS cluster, as it will contain instructions for registering the services.
    Hope this gives you a pointer in the right direction.

  • Dispatcher of J2EE Engine does not start

    I have the following problem, we restart the j2ee engine and the dispatcher does not come up. The server and SDM works fine
    <b>dev_dispatcher:</b>
    trc file: "/usr/sap/Q82/JC00/work/dev_dispatcher", trc level: 1, release: "700"
    node name   : ID2430700
    pid         : 1192142
    system name : Q82
    system nr.  : 00
    started at  : Tue Nov 20 10:47:45 2007
    arguments       :
           arg[00] : /usr/sap/Q82/JC00/exe/jlaunch
           arg[01] : pf=/usr/sap/Q82/SYS/profile/Q82_JC00_sapQ82
           arg[02] : -DSAPINFO=Q82_00_dispatcher
           arg[03] : pf=/usr/sap/Q82/SYS/profile/Q82_JC00_sapQ82
    [Thr  1] Tue Nov 20 10:47:45 2007
    [Thr  1] *** WARNING => INFO: Unknown property [instance.box.number=Q82JC00sapq82] [jstartxx_mt. 841]
    [Thr  1] *** WARNING => INFO: Unknown property [instance.en.host=sapQ82] [jstartxx_mt. 841]
    [Thr  1] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx_mt. 841]
    [Thr  1] *** WARNING => INFO: Unknown property [instance.system.id=00] [jstartxx_mt. 841]
    JStartupReadInstanceProperties: read instance properties [/usr/sap/Q82/JC00/j2ee/cluster/instance.properties]
    -> ms host    : sapQ82
    -> ms port    : 3901
    -> OS libs    : /usr/sap/Q82/JC00/j2ee/os_libs
    -> Admin URL  :
    -> run mode   : normal
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : /usr/sap/Q82/JC00/j2ee/cluster/instance.properties
    Instance properties
    -> ms host    : sapQ82
    -> ms port    : 3901
    -> os libs    : /usr/sap/Q82/JC00/j2ee/os_libs
    -> admin URL  :
    -> run mode   : normal
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : /usr/sap/Q82/JC00/j2ee/cluster/instance.properties
    -> [01] bootstrap_ID2430700  : /usr/sap/Q82/JC00/j2ee/cluster/instance.properties
    -> [02] bootstrap_ID2430750  : /usr/sap/Q82/JC00/j2ee/cluster/instance.properties
    Worker nodes
    -> [00] ID2430700            : /usr/sap/Q82/JC00/j2ee/cluster/instance.properties
    -> [01] ID2430750            : /usr/sap/Q82/JC00/j2ee/cluster/instance.properties
    [Thr  1] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr  1] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 258] JLaunchRequestFunc: Thread 258 started as listener thread for np messages.
    [Thr 515] WaitSyncSemThread: Thread 515 started as semaphore monitor thread.
    [Thr  1] SigISetDefaultAction : default handling for signal 20
    [Thr  1] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr  1] CPIC (version=700.2006.09.13)
    [Thr  1] [Node: dispatcher] java home is set by profile parameter
         Java Home: /usr/java14_64
    [Thr  1] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/Q82/JC00/exe/jvmx.jar
    JStartupIReadSection: read node properties [ID2430700]
    -> node name          : dispatcher
    -> node type          : dispatcher
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : /usr/java14_64
    -> java parameters    : -Xj9 -Xgcpolicy.gencon -verbose:gc -Xmn70m -Xdisableexplicitgc -Djava.security.policy=.\java.policy -Djava.security.egd=file:/dev/urandom -Djco.jarm=1
    -> java vm version    : J2RE 1.4.2 IBM J9 2.3 AIX ppc64-64 j9ap64142ifx-20070510a (JIT enabled)
    -> java vm vendor     : IBM J9 VM (IBM Corporation)
    -> java vm type       : server
    -> java vm cpu        : ppc64
    -> heap size          : 202M
    -> init heap size     : 202M
    -> root path          : /usr/sap/Q82/JC00/j2ee/cluster/dispatcher
    -> class path         : ./bin/boot/boot.jar:./bin/system/bytecode.jar:.
    -> OS libs path       : /usr/sap/Q82/JC00/j2ee/os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : /usr/sap/Q82/JC00/exe/jstartup.jar:/usr/sap/Q82/JC00/exe/jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50000
    -> shutdown timeout   : 120000
    [Thr  1] JLaunchISetDebugMode: set debug mode [no]
    [Thr 772] JLaunchIStartFunc: Thread 772 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [dispatcher]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Xj9
    -> arg[  4]: -Xgcpolicy.gencon
    -> arg[  5]: -verbose:gc
    -> arg[  6]: -Xmn70m
    -> arg[  7]: -Xdisableexplicitgc
    -> arg[  8]: -Djava.security.policy=.\java.policy
    -> arg[  9]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 10]: -Djco.jarm=1
    -> arg[ 11]: -Dsys.global.dir=/usr/sap/Q82/SYS/global
    -> arg[ 12]: -Dapplication.home=/usr/sap/Q82/JC00/exe
    -> arg[ 13]: -Djava.class.path=/usr/sap/Q82/JC00/exe/jstartup.jar:/usr/sap/Q82/JC00/exe/jvmx.jar:./bin/boot/boot.jar:./bin/system/bytecode.jar:.
    -> arg[ 14]: -Djava.library.path=/usr/java14_64/jre/bin:/usr/java14_64/jre/bin:/usr/java14_64/jre/bin/classic:/usr/java14_64/jre/bin:/usr/sap/Q82/JC00/exe:/usr/sap/Q82/JC00/exe:/usr/sap/Q82/SYS/exe/run:/oracle/client/10x_64/instantclient:/usr/sap/Q82/JC00/exe::/usr/lib:/usr/sap/Q82/JC00/j2ee/os_libs:/usr/sap/Q82/JC00/exe:/usr/sap/Q82/JC00/exe:/usr/lib:/lib:/usr/sap/Q82/SYS/exe/run:/oracle/client/10x_64/instantclient
    -> arg[ 15]: -Dmemory.manager=202M
    -> arg[ 16]: -Xmx202M
    -> arg[ 17]: -Xms202M
    -> arg[ 18]: -DLoadBalanceRestricted=no
    -> arg[ 19]: -Djstartup.mode=JCONTROL
    -> arg[ 20]: -Djstartup.ownProcessId=1192142
    -> arg[ 21]: -Djstartup.ownHardwareId=R1572408088
    -> arg[ 22]: -Djstartup.whoami=dispatcher
    -> arg[ 23]: -Djstartup.debuggable=no
    -> arg[ 24]: -DSAPINFO=Q82_00_dispatcher
    -> arg[ 25]: -DSAPSTARTUP=1
    -> arg[ 26]: -DSAPSYSTEM=00
    -> arg[ 27]: -DSAPSYSTEMNAME=Q82
    -> arg[ 28]: -DSAPMYNAME=sapQ82_Q82_00
    -> arg[ 29]: -DSAPDBHOST=sapQ82
    -> arg[ 30]: -Dj2ee.dbhost=sapQ82
    [Thr 772] *** ERROR => JHVM_LoadJavaVM: Cannot create Java VM (rc=-6) [jhvmxx_mt.c  542]
    [Thr 772] *** ERROR => Cannot load Java VM (server) (rc=-1) [jlnchxxi_mt. 752]
    [Thr 772] **********************************************************************
    ERROR => Java VM initialization failed.
    Please see SAP Note 943602 , section 'Java VM initialization issues'
    for additional information and trouble shooting.
    [Thr 772] SigISetIgnoreAction : SIG_IGN for signal 20
    [Thr 772] JLaunchCloseProgram: good bye (exitcode = -1)
    Does somebody has any ideas?
    Regards Peter

    Hi folks,
    i solved it by myself. There was a wrong javaparameter in the settings of the dispatcher.
    -Xgcpolicy.gencon instead of -Xgcpolicy:gencon, my colleague has found it out.
    Regards Peter

  • J2ee engine does not start - error 503

    have a dual stack NetWeaver installation. I can start/connect to the ABAP stack fine, but I cannot connect to the Java stack.
    When I do http://<machine name>:50000 or http://<machine name>:50000/irj/portal ... I get a "503 service unavailable. Application stopped" message.
    searching through the j2ee logs did not reveal any problems (All j2ee services look like they are started successfully).

    Tiberiu,
    Check ume service : com.sap.security.core.ume.service started or not?
    I think it may be very slow and this may cause a lot of services to time out.
    Changed settings in config tool:
    1.instance_IDXXX -> server -> managers -> Service manager -> LoadTimeout from 5 to 15.
    2.instance_IDXXX -> server -> managers -> ApplicationThreadManager there change InitialThreadCount, MinThreadCount and MaxThreadCount to 350.
    3.Restart the server.
    Regards,
    Karthick Eswaran
    *Do not forget to Reward points for helpful answers

  • J2EE engine Dispatcher not starting

    I installed Developer Workplace 2004s SR2 (Java) on MS SQL server, in Windows XP Professional. It worked fine and I was able to start the engine. When I patched it to SP10 , dispatcher is not starting and it is greyed out. All the log files has no errors reported except one file which has an error message logged in work/jvm_dispatcher.log. Here is the message:
    Error - ID:000000. Error in loading com.sap.engine.core.Framework class. Class not found.
    Any Clue

    Are all SCA needed for SP10 deployed successfully?
    I think some sca files were not properly deployed...

  • J2ee engine does not start up after system copy

    Dear All,
    I have done a system copy of BW3.5 (NW04). I installed the BW.3.5 and then replaced the data and control files.
    This has ABAP + java.
    Now after system copy when i am starting the server, the J2ee instance doesnt start up.
    ABAP is running and DB is up too.
    I am getting the following error in log_bootstrap file:-
    Exception occured:
    com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
            at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:422)
            at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
            at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:813)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
            at java.lang.reflect.Method.invoke(Method.java:391)
            at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    ==[ Caused by: ]==----
    com.sap.engine.bootstrap.SynchronizationException: No such Dialog Instance (ID1125100) in the database! Check
    database consistency or local Bootstrap properties!
            at com.sap.engine.bootstrap.Synchronizer.getElementType(Synchronizer.java:81)
            at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:420)
            at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
            at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:813)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
            at java.lang.reflect.Method.invoke(Method.java:391)
            at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    [Aug 26, 2008 2:00:26 PM ] [Bootstrap module]> Problem occured while performing synchronization.
    [Aug 26, 2008 2:00:42 PM ] -
    [Aug 26, 2008 2:00:42 PM ] Bootstrap MODE:
    [Aug 26, 2008 2:00:42 PM ] <INSTANCE GLOBALS>
    [Aug 26, 2008 2:00:42 PM ]  determined by parameter [ID0011251].
    [Aug 26, 2008 2:00:42 PM ] -
    [Aug 26, 2008 2:00:46 PM ] Exception occured:
    com.sap.engine.frame.core.configuration.NameNotFoundException: A configuration with the path "cluster_data/di
    spatcher/ID1125100" does not exist.
            at com.sap.engine.core.configuration.impl.ConfigurationDataCacheAllImpl.getSubConfiguration(Configura
    tionDataCacheAllImpl.java:107)
            at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getSubConfiguration(ReadAccessConfi
    guration.java:715)
            at com.sap.engine.bootstrap.Synchronizer.getConfiguration(Synchronizer.java:365)
            at com.sap.engine.bootstrap.Synchronizer.getElementType(Synchronizer.java:78)
            at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:420)
            at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
            at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:813)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
            at java.lang.reflect.Method.invoke(Method.java:391)
            at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    What could the problem?. Do I need to do some other settings for system copy of JVA instance?
    Kindly help
    Thanks
    Tajinder

    Hi,
    I already checked that note. It did not help.
    I am pasting mine dev_jcontrol file:--
    trc file: "/usr/sap/BD1/DVEBMGS00/work/dev_jcontrol", trc level: 1, release: "640"
    node name   : jcontrol
    pid         : 868524
    system name : BD1
    system nr.  : 00
    started at  : Tue Aug 26 16:27:10 2008
    arguments   :
        arg[00] : jcontrol
        arg[01] : pf=/usr/sap/BD1/SYS/profile/BD1_DVEBMGS00_BWQAS
        arg[02] : -DSAPSTART=1
        arg[03] : -DCONNECT_PORT=64380
        arg[04] : -DLISTEN_PORT=64381
        arg[05] : -DSAPSYSTEM=00
        arg[06] : -DSAPSYSTEMNAME=BD1
        arg[07] : -DSAPMYNAME=BWQAS_BD1_00
        arg[08] : -DSAPPROFILE=/usr/sap/BD1/SYS/profile/BD1_DVEBMGS00_BWQAS
        arg[09] : -DFRFC_FALLBACK=ON
        arg[10] : -DFRFC_FALLBACK_HOST=localhost
    JStartupReadInstanceProperties: read instance properties [/usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.proper
    ties:/usr/sap/BD1/DVEBMGS00/SDM/program/config/sdm_jstartup.properties]
    -> ms host    : BWQAS
    -> ms port    : 3601
    -> OS libs    : /usr/sap/BD1/DVEBMGS00/j2ee/os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : /usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
    -> files [01] : /usr/sap/BD1/DVEBMGS00/SDM/program/config/sdm_jstartup.properties
    Instance properties
    -> ms host    : BWQAS
    -> ms port    : 3601
    -> os libs    : /usr/sap/BD1/DVEBMGS00/j2ee/os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : /usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
    -> [01] bootstrap_ID1125100  : /usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
    -> [02] bootstrap_ID1125150  : /usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
    Worker nodes
    -> [00] ID1125100            : /usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
    -> [01] ID1125150            : /usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
    -> [02] sdm                  : /usr/sap/BD1/DVEBMGS00/SDM/program/config/sdm_jstartup.properties
    [Thr 01] Tue Aug 26 16:27:10 2008
    [Thr 01] SigISetDefaultAction : default handling for signal 20
    [Thr 01] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
    [Thr 258] JControlDPMessageFunc: Thread 258 started as handler thread for R/3 dispatcher messages.
    [Thr 01] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) -
    using -Xmx512m [jstartxx_mt. 2282]
    [Thr 01] [Node: bootstrap] java home is set by profile parameter
            Java Home: /usr/java14_64
    JStartupIReadSection: read node properties [bootstrap]
    -> node name       : bootstrap
    -> node type       : bootstrap
    -> java path       : /usr/java14_64
    -> java parameters : -Djco.jarm=1 -Djco.jarm=1
    -> java vm version : J2RE 1.4.2 IBM AIX 5L for PowerPC (64 bit JVM) build caix64142-20060421 (SR5) (JIT enabl
    ed: jitc)
    -> java vm vendor  : Classic VM (IBM Corporation)
    -> java vm type    : <default>
    -> java vm cpu     : ppc64
    -> heap size       : 512M
    -> root path       : /usr/sap/BD1/DVEBMGS00/j2ee/cluster
    -> class path      : ./bootstrap/launcher.jar
    -> OS libs path    : /usr/sap/BD1/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  : /usr/sap/BD1/DVEBMGS00/j2ee/os_libs/jstartup.jar
    -> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0011251
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    JStartupStartJLaunch: program = /usr/sap/BD1/DVEBMGS00/j2ee/os_libs/jlaunch
    -> arg[00] = /usr/sap/BD1/DVEBMGS00/j2ee/os_libs/jlaunch
    -> arg[01] = pf=/usr/sap/BD1/SYS/profile/BD1_DVEBMGS00_BWQAS
    -> arg[02] = -DSAPINFO=BD1_00_bootstrap
    -> arg[03] = -file=/usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
    -> arg[04] = -nodeName=bootstrap
    -> arg[05] = -nodeId=-1
    -> arg[06] = -syncSem=12582961
    -> arg[07] = -jvmOutFile=/usr/sap/BD1/DVEBMGS00/work/jvm_bootstrap.out
    -> arg[08] = -stdOutFile=/usr/sap/BD1/DVEBMGS00/work/std_bootstrap.out
    -> arg[09] = -locOutFile=/usr/sap/BD1/DVEBMGS00/work/dev_bootstrap
    -> arg[08] = -stdOutFile=/usr/sap/BD1/DVEBMGS00/work/std_bootstrap.out
    -> arg[09] = -locOutFile=/usr/sap/BD1/DVEBMGS00/work/dev_bootstrap
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=/usr/sap/BD1/SYS/profile/BD1_DVEBMGS00_BWQAS
    -> arg[12] = -DSAPSTART=1
    -> arg[13] = -DCONNECT_PORT=64382
    -> arg[14] = -DLISTEN_PORT=64381
    -> arg[15] = -DSAPSYSTEM=00
    -> arg[16] = -DSAPSYSTEMNAME=BD1
    -> arg[17] = -DSAPMYNAME=BWQAS_BD1_00
    -> arg[18] = -DSAPPROFILE=/usr/sap/BD1/SYS/profile/BD1_DVEBMGS00_BWQAS
    -> arg[19] = -DFRFC_FALLBACK=ON
    -> arg[20] = -DFRFC_FALLBACK_HOST=localhost
    -> lib path = LIBPATH=/usr/java14_64/jre/bin:/usr/java14_64/jre/bin/classic:/usr/java14_64/jre/bin:/usr/sap/B
    D1/DVEBMGS00/j2ee/os_libs:/usr/sap/BD1/SYS/exe/run:/usr/sap/BD1/SYS/exe/runU:/usr/lib:/usr/sap/BD1/DVEBMGS00/
    j2ee/os_libs:/usr/sap/BD1/DVEBMGS00/j2ee/os_libs:/usr/lib:/lib:/usr/sap/BD1/SYS/exe/run:/usr/sap/BD1/SYS/exe/
    runU
    -> exe path = PATH=/usr/java14_64/bin:/usr/sap/BD1/DVEBMGS00/j2ee/os_libs:/oracle/BD1/920_64/bin:/usr/java14_
    64/bin:/home/bd1adm:/usr/sap/BD1/SYS/exe/runU:/usr/sap/BD1/SYS/exe/run:/usr/bin:/etc:/usr/sbin:/usr/ucb:/home
    /bd1adm/bin:/usr/bin/X11:/sbin:.
    [Thr 01] JStartupICreateProcess: fork process (pid 893002)
    [Thr 01] Tue Aug 26 16:27:18 2008
    [Thr 01] *** ERROR => invalid return code of process [bootstrap] (exitcode=66) [jstartxx_mt. 1433]
    [Thr 01] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc=66)
    [Thr 01] JControlCloseProgram: started (exitcode = 66)
    [Thr 01] JControlCloseProgram: good bye... (exitcode=66)
    DO i have to change the some settingdsin any file for java instance after system copy.
    Thanks
    Tajinder

  • J2EE engine does not start and then visual administartor gives error

    I am trying to start the SAP J2EE GUI after entering User J2EE_ADMIN and
    password it hardly goestill 5% and gives following task error:
    "com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
    create new RemoteLoginContext".
    I have also applied 701654 as suggested by you earlier but I have never
    changed the password, However I have updated the Secure storage also
    using configuration tool.

    I am trying to start the SAP J2EE GUI after entering User J2EE_ADMIN and
    password it hardly goestill 5% and gives following task error:
    "com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
    create new RemoteLoginContext".
    I have also applied 701654 as suggested by you earlier but I have never
    changed the password, However I have updated the Secure storage also
    using configuration tool.

  • J2EE server will not start

    Hello all,
    An attempt was made to start an ECC 6.0 box (with J2EE and ABAP stacks). The ABAP portion starts fine (as one can log into it) but the J2EE portion has failed. Below are files that were gathered. It looks like it is due to a UME error.
    TIA

    file: security.0.log
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[./log/system/security.log]/>
    <!PATTERN[security.log]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[UTF8]/>
    <!FILESET[0, 5, 10485760]/>
    <!PREVIOUSFILE[security.4.log]/>
    <!NEXTFILE[security.1.log]/>
    <!LOGHEADER[END]/>
    #1.5^H#002268378E4200230000000000001E47000468B3C171167E#1241021160691#/System/Security/Usermanagement##com.sap.security.core.persistence#######SAPEngine_System_Thread[impl:5]_34##0#0#Error#1#com.sap.security.core.persistence#Java#User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "".##User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "".#2#Password logon no longer possible - too many failed attempts#{
      passwd=********
      lang=EN
      receiverid=master
      sysnr=$$
      client=001
      poolmaxsize=10
      user=SAPJSF
      receiverid_guest=master
      ashost=localhost
      poolmaxwait=10000
    #1.5^H#002268378E4200230000000300001E47000468B3C1711C36#1241021160692#/System/Security/Usermanagement##com.sap.security.core.persistence#######SAPEngine_System_Thread[impl:5]_34##0#0#Error#1#com.sap.security.core.persistence#Java#An exception was thrown in the UME/ABAP user management connector that was caused by unavailability of the RFC communication with the backend system: "". ##An exception was thrown in the UME/ABAP user management connector that was caused by unavailability of the RFC communication with the backend system: "". #1#Password logon no longer possible - too many failed attempts#
    #1.5^H#002268378E4200230000000500001E47000468B3C1711F80#1241021160692#/System/Security/Usermanagement##com.sap.security.core.persistence#######SAPEngine_System_Thread[impl:5]_34##0#0#Fatal#1#com.sap.security.core.persistence#Java#Initialization of ABAP data source () failed: "". This message is critical if it appears during the startup of the AS Java.##Initialization of ABAP data source () failed: "". This message is critical if it appears during the startup of the AS Java.#2#com.sap.security.core.persistence.datasource.imp.R3Persistence#Password logon no longer possible - too many failed attempts#
    #1.5^H#002268378E4200230000000A00001E47000468B3C1712696#1241021160695#/System/Security/Usermanagement##com.sap.security.core.server.ume.service.UMEServiceFrame#######SAPEngine_System_Thread[impl:5]_34##0#0#Fatal#1#com.sap.security.core.server.ume.service.UMEServiceFrame#Plain#Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Password logon no longer possible - too many failed attempts###

  • 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

  • Engine Service will not start - New Install

    Trying to install NSM on a Windows 2008 r2 server and the Engine service will not start after the files are installed.
    File Resource Manager is installed along with fully patched .NET 4.
    Windows Logs give the below error before the service not starting failure.
    Activation context generation failed for "C:\Program Files\Novell\Storage Manager\Engine\sqlite3.dll". Dependent Assembly Microsoft.VC90.CRT,processorArchitecture="amd64",p ublicKeyToken="1fc8b3b9a1e18e3b",type="win32",vers ion="9.0.21022.8" could not be found. Please use sxstrace.exe for detailed diagnosis.

    Fixed. I missed the .NET 3.5 requirement.

  • J2EE server does not start during installation

    Hi,
    I am installing WebAS JAVA 640 (NW04 SR1) on a Windows 2003/MSSQL server. I am using JAVA SDK 1.4.2_9. The installation stops at step 24/25 whereby the installer waits for the J2EE engine to start. After making 3 attempts to start the J2EE server, the installation process just hangs and I have to Cancel the installation.
    BTW, I am specifying a heap size of 1024 MB and using the "Database Only" option as UME data store during installation.
    Having checked the trace and log files, it seems the UME service fails to start, throws an exception and the message "the start of a core service failed, Web AS will not start".
    According to the information available  <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/20/361941edd5ef23e10000000a155106/content.htm">here</a>, I have checked the settings and it seems that option 2, <b>"User or group data is missing"</b> is causing the problem since database content of UME is missing. I have tried selecting entries from table UME_STRINGS but this table is empty.
    Now, the same link says that I should login to UME web application as SAP* but the problem is that without the J2EE engine starting up, I cannot login and create missing users/groups.
    Any ideas???
    Regards
    Shehryar

    Thanks to all who replied. I have actually tried all options suggested like waiting for retries until the box appears, trying to manually start the server, and reducing heap size. None worked for me. For your information, I have a 2.4 GHz machine with 4GB RAM so I think heap size should not be an issue. I checked SAP Note regarding heap size issues in Win 2003 but that does not seem to apply in my case since my system does not behave abnormally with JVM settings.
    Thanks again and I'll give it another shot.
    Regards
    Shehryar

  • SLD server will not start

    Hi, I am having an issue with my SLD server.  The java will not start completely.  This is the log i get:
    If you have any clue that would be great.
    thanks
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[./log/defaultTrace.trc]/>
    <!PATTERN[defaultTrace.trc]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[Cp1252]/>
    <!FILESET[0, 20, 10485760]/>
    <!PREVIOUSFILE[defaultTrace.19.trc]/>
    <!NEXTFILE[defaultTrace.1.trc]/>
    <!LOGHEADER[END]/>
    #1.5#000BCDEF4B75001E0000000100000B4400046A834059524E#1243011859688#com.sap.di.sdic.srv.java.SDICServiceFrame##com.sap.di.sdic.srv.java.SDICServiceFrame#######SAPEngine_System_Thread[impl:5]_70##0#0#Error#1#/Applications/SDIC/Service#Java###Failed to initialize the SDIC service. An unanticipated error has occured; Error description - #1#com.sap.di.sdic.exception.DiException: StateStore Initialization requires the values to be specified for the properties"sdic.state.store.storeManager" and "sdic.nwdiservers.admin.user"#
    #1.5#000BCDEF4B75001E0000000300000B4400046A8340596B1D#1243011859688#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_70##0#0#Error#1#/System/Server#Plain###Service tcdisdic~srv error. Nested exception is: com.sap.engine.frame.ServiceException: StateStore Initialization requires the values to be specified for the properties"sdic.state.store.storeManager" and "sdic.nwdiservers.admin.user"
         at com.sap.di.sdic.srv.java.SDICServiceFrame.start(SDICServiceFrame.java:162)
         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.di.sdic.exception.DiException: StateStore Initialization requires the values to be specified for the properties"sdic.state.store.storeManager" and "sdic.nwdiservers.admin.user"
         at com.sap.di.sdic.srv.java.SDICServiceFrame.start(SDICServiceFrame.java:149)
         ... 5 more
    Caused by: java.lang.Exception: StateStore Initialization requires the values to be specified for the properties"sdic.state.store.storeManager" and "sdic.nwdiservers.admin.user"
         ... 6 more
    #1.5#000BCDEF4B7500260000000000000B4400046A8340A5D8ED#1243011864701#com.sap.caf.um.metadata.imp.MetaDataTools##com.sap.caf.um.metadata.imp.MetaDataTools.MetaDataTools()#######SAPEngine_System_Thread[impl:5]_54##0#0#Info#1#/System/Server#Plain###sap.com caf/um/metadata/imp MAIN_APL70VAL_C 963656#
    #1.5#000BCDEF4B75002F0000000100000B4400046A8340D0C614#1243011867513#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.newProperties(int prcs, int conn)#######SAPEngine_System_Thread[impl:5]_35##0#0#Error#1#/System/Server#Java###enter  newProperties()##
    #1.5#000BCDEF4B75002F0000000300000B4400046A8340D702A6#1243011867919#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_35##0#0#Error#1#/System/Server#Java###SNC properties not found ##
    #1.5#000BCDEF4B7500300000000000000B4400046A8340F313F1#1243011869762#com.sap.caf.um.relgroups.imp.persistence.DataSource##com.sap.caf.um.relgroups.imp.persistence.DataSource.DataSource()#######SAPEngine_System_Thread[impl:5]_4##0#0#Info#1#/System/Server#Plain###sap.com caf/um/relgroups/imp MAIN_APL70VAL_C 963842#
    #1.5#000BCDEF4B7500380000000100000B4400046A83412AA249#1243011873402#com.adobe.service.sap.configuration##com.adobe.service.sap.configuration#######OrderedChannel for service##0#0#Error#1#/System/Security#Plain###Error while reading trusted anchor configuration information:
    com.sap.security.core.server.securestorage.exception.ObjectRetrievalException: Could not find clientID servicescomadobeDocumentServicesConfigurationAdobeConfigurationService~jar
         at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.getClientsStorageLocation(RemoteSecureStorageClientContextImpl.java:231)
         at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.retrieveObject(RemoteSecureStorageClientContextImpl.java:724)
         at com.adobe.service.sap.configuration.ConfigurationService.readXML(Unknown Source)
         at com.adobe.service.sap.configuration.ConfigurationService.<init>(Unknown Source)
         at com.adobe.service.sap.configuration.ServiceFrame.start(Unknown Source)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    #1.5#000BCDEF4B7500380000000300000B4400046A83412AAC7B#1243011873402#com.adobe.service.sap.configuration##com.adobe.service.sap.configuration#######OrderedChannel for service##0#0#Error#1#/System/Security#Plain###Error while reading credential configuration information:
    com.sap.security.core.server.securestorage.exception.ObjectRetrievalException: Could not find clientID servicescomadobeDocumentServicesConfigurationAdobeConfigurationService~jar
         at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.getClientsStorageLocation(RemoteSecureStorageClientContextImpl.java:231)
         at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.retrieveObject(RemoteSecureStorageClientContextImpl.java:724)
         at com.adobe.service.sap.configuration.ConfigurationService.readXML(Unknown Source)
         at com.adobe.service.sap.configuration.ConfigurationService.<init>(Unknown Source)
         at com.adobe.service.sap.configuration.ServiceFrame.start(Unknown Source)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    #1.5#000BCDEF4B7500380000000500000B4400046A83412AB51D#1243011873402#com.adobe.service.sap.configuration##com.adobe.service.sap.configuration#######OrderedChannel for service##0#0#Error#1#/System/Security#Plain###Error while reading CRL configuration information:
    com.sap.security.core.server.securestorage.exception.ObjectRetrievalException: Could not find clientID servicescomadobeDocumentServicesConfigurationAdobeConfigurationService~jar
         at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.getClientsStorageLocation(RemoteSecureStorageClientContextImpl.java:231)
         at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.retrieveObject(RemoteSecureStorageClientContextImpl.java:724)
         at com.adobe.service.sap.configuration.ConfigurationService.readXML(Unknown Source)
         at com.adobe.service.sap.configuration.ConfigurationService.<init>(Unknown Source)
         at com.adobe.service.sap.configuration.ServiceFrame.start(Unknown Source)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    #1.5#000BCDEF4B7500380000000700000B4400046A83412ABDBE#1243011873402#com.adobe.service.sap.configuration##com.adobe.service.sap.configuration#######OrderedChannel for service##0#0#Error#1#/System/Security#Plain###Error while reading password configuration information:
    com.sap.security.core.server.securestorage.exception.ObjectRetrievalException: Could not find clientID servicescomadobeDocumentServicesConfigurationAdobeConfigurationService~jar
         at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.getClientsStorageLocation(RemoteSecureStorageClientContextImpl.java:231)
         at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.retrieveObject(RemoteSecureStorageClientContextImpl.java:724)
         at com.adobe.service.sap.configuration.ConfigurationService.readXML(Unknown Source)
         at com.adobe.service.sap.configuration.ConfigurationService.<init>(Unknown Source)
         at com.adobe.service.sap.configuration.ServiceFrame.start(Unknown Source)
         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)
    Jean Seguin

    Hi,
    The user SAPJSF is not lock and here is the output of the Stdserver.out
    stdout/stderr redirect
    node name   : server0
    pid         : 5800
    system name : IS1
    system nr.  : 01
    started at  : Fri May 22 14:50:38 2009
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 5756] Fri May 22 14:50:39 2009
    [Thr 5756] 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...
    Loading: LogManager ... 6420 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 440 ms.
    Loading: ThreadManager ... 76 ms.
    Loading: IpVerificationManager ... 46 ms.
    Loading: ClassLoaderManager ... 30 ms.
    Loading: ClusterManager ... 638 ms.
    Loading: LockingManager ... 227 ms.
    Loading: ConfigurationManager ... 8136 ms.
    Loading: LicensingManager ... 76 ms.
    Loading: CacheManager ... 410 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service memory started. (45 ms).
      Service cross started. (243 ms).
      Service file started. (289 ms).
      Service runtimeinfo started. (30 ms).
      Service timeout started. (106 ms).
      Service trex.service started. (106 ms).
      Service p4 started. (744 ms).
      Service classpath_resolver started. (30 ms).
      Service userstore started. (243 ms).
      Service jmx_notification started. (532 ms).
      Service log_configurator started. (24331 ms).
      Service locking started. (15 ms).
      Service http started. (759 ms).
      Service naming started. (1775 ms).
      Service appclient started. (228 ms).
      Service failover started. (213 ms).
      Service jmsconnector started. (304 ms).
      Service javamail started. (410 ms).
      Service ts started. (349 ms).
      Service licensing started. (30 ms).
      Service connector started. (380 ms).
      Service iiop started. (652 ms).
      Service webservices started. (1700 ms).
      Service deploy started. (31390 ms).
      Service configuration started. (61 ms).
      Service MigrationService started. (106 ms).
      Service bimmrdeployer started. (30 ms).
      Service dbpool started. (6041 ms).
      Service com.sap.security.core.ume.service started. (7680 ms).
      Service tcdisdic~srv started. (1776 ms).
      Service security started. (4068 ms).
      Service classload started. (228 ms).
      Service applocking started. (228 ms).
      Service shell started. (379 ms).
      Service ejb started. (547 ms).
      Service tceCATTPingservice started. (425 ms).
      Service telnet started. (501 ms).
      Service dsr started. (1062 ms).
      Service servlet_jsp started. (1791 ms).
      Service webdynpro started. (1426 ms).
      Service cafummetadata~imp started. (2095 ms).
      Service keystore started. (2474 ms).
      Service ssl started. (15 ms).
      Service cafruntimeconnectivity~impl started. (50818 ms).
      Service jmx started. (3111 ms).
      Service tcsecsecurestorage~service started. (1199 ms).
      Service tcsecwssec~service started. (835 ms).
      Service cafumrelgroups~imp started. (4099 ms).
      Service CUL started. (2550 ms).
      Service tcsecdestinations~service started. (2824 ms).
      Service apptracing started. (1351 ms).
      Service com.adobe~DataManagerService started. (3187 ms).
      Service pmi started. (1138 ms).
      Service tcsecvsi~service started. (1988 ms).
      Service sld started. (5525 ms).
      Service basicadmin started. (4568 ms).
      Service com.adobe~DocumentServicesDestProtoService started. (1548 ms).
      Service com.adobe~DocumentServicesBinaries2 started. (1624 ms).
      Service com.adobe~DocumentServicesLicenseSupportService started. (1336 ms).
      Service adminadapter started. (364 ms).
      Service com.adobe~LicenseService started. (470 ms).
      Service monitor started. (1564 ms).
      Service com.adobe~DocumentServicesConfiguration started. (2762 ms).
      Service com.adobe~TrustManagerService started. (182 ms).
      Service com.adobe~PDFManipulation started. (4888 ms).
      Service tc.CBS.Service started. (10564 ms).
      Service com.adobe~FontManagerService started. (10049 ms).
      Service com.sap.aii.af.cpa.svc started. (9821 ms).
      Service com.sap.aii.af.security.service started. (31 ms).
      Service tc.monitoring.logviewer started. (19216 ms).
      Service com.sap.aii.af.svc started. (2808 ms).
      Service com.sap.aii.af.ms.svc started. (1366 ms).
      Service com.adobe~XMLFormService started. (6315 ms).
      Service com.sap.aii.adapter.bc.svc started. (106 ms).
      Service com.sap.aii.adapter.marketplace.svc started. (243 ms).
      Service com.sap.aii.adapter.xi.svc started. (182 ms).
      Service com.sap.aii.adapter.file.svc started. (304 ms).
      Service com.sap.aii.adapter.jdbc.svc started. (288 ms).
      Service com.sap.aii.adapter.rfc.svc started. (122 ms).
      Service jms_provider started. (22373 ms).
      Service com.sap.aii.adapter.mail.svc started. (1442 ms).
      Service com.sap.aii.adapter.jms.svc started. (895 ms).
      Service com.sap.aii.af.ispeak.svc started. (728 ms).
      Service rfcengine started. (73524 ms).
    ServiceManager started for 148445 ms.
    Framework started for 166083 ms.
    SAP J2EE Engine Version 7.00   PatchLevel is running!
    PatchLevel October 23, 2006 07:41 GMT

  • Server0 will not start. client 100 does not exist.

    On my NetWeaver 7.0 system with Solution Mgr 7.0 (build from IDES 600 image) on a HPUX 11.23 IA & Oracle with Java 1.4.2.15 installed, I'm going thru the basic setup steps for configuring MOPZ and get to the step
    Following IMG basic install steps (basic settings->SAP Solution Manager System->System Landscape(SLD)->Specify service for comm. w/ SLD in Visual Admin), unable to connect to J2EE engine via Visual Admin.
    The dev_server0 log:
    [Thr  6] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr  6] **********************************************************************
    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.
    Std_server0.out log:
    ===========================================================
    Apr 27, 2009 8:14:20 AM  ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_73] Fatal:
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed"
    . Technical details: Client 100 is not available in this system
    I ran JCmon to restart the instance.
    cd /usr/sap/SMA/ DVEBMGS00/j2ee/os_lib
    jcmon pf= /usr/sap/SMA/SYS/profile/SMA_DVEBMGS00_pax3
      20: local Admin.
    Restarted instance, but same error, client 100 is not available in this system.
    std_server0.out details
    ===============================================================
    Apr 30, 2009 4:24:50 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_97] Fatal: Initialization of ABAP data
    source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "Client 100 is not available in this system". This message
    is critical if it appears during the startup of the AS Java.
    Apr 30, 2009 4:24:50 PM  ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_97] 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: Cli
    ent 100 is not available in this system
            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:81)
            at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:107)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Client 100 is not available in this system
            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:445)
            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: Cli
    ent 100 is not available in this system
            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:81)
            at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:107)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Client 100 is not available in this system
            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:445)
            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.
    Apr 30, 2009 4:24:50 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_97] Fatal: Critical shutdown was invoke
    d. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    ============================================================
    Solution maybe obvious, create a client 100. But server0 was running fine on this node when I first installed Solution Mgr,  and it is running fine on my ERP / BI system that II built from the same IDES media, ofwhich it does not have a client 100 and Java WebAS is running fine. Also, able to connect to portal via http://host:50000/irj.  Only difference is I have java 1.4.2.20 installed on the BI system.
    So is there some other reason why server0 will not come up?

    Using the search tool for property name containing "client", the only client defs in the configtool are ume.r3.connection.001-004.client under
    cluster-data->Global server configuration->services->com.sap.security.core.ume.service. Values are blank. This is the same on my failing system SMA (SolMgr) and working system BIF(BI system).
    The ume.r3.connection.master.client has custom value of 100. I set it to one and restarted the cluster.
    The WebAS is up and running again. Don't know what could of changed it to 100.
    Thanks for all your help.
    -Don.

Maybe you are looking for

  • Time Machine general issues!

    Hi all! ok, i tried time machine out and im very disappointed with the experience. I have a Airport Extreme (newest) and a USB harddrive and running snow leopard. All versions of everything is the latest. At first when i start the first backup, it do

  • Final Cut HD

    I am thinking to buy an Apple server and would like to put Final Cut HD on it so as to access and edit from remote loction by my team! Is this possible over the internet. Rod

  • What's the Meaning of Dimension in SAP B1?

    Sir, What's the Meaning of Dimension in SAP B1? And how it is used in Profit Centre ? plz tell me ......!

  • How to skip validation for tag file, or jsp fragment?

    hi I have some jsp fragment and tag file in a workshop 10 project workshop blame me about the jsp fragment (no start/end tag) and unable to publish to server is there a way to skip validation on some files? I do found an check box call "validate JSP

  • Unable to query enter and maintain form

    Hi Everyone, I have an issue wherein i am not able to query few employees in the Enter and Maintain screen in HRMS. The form shows below error: FRM-40212: Invalid value for field FULL_NAME Can you please suggest if there is any profile setup which af