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

Similar Messages

  • J2EE Server does not start  -  jcontrol.exe  stopped

    Hello,
    I have read a lot of messages on this topic on SDN. But I did not find any dealing exactly with my problem.
    Indeed, I got these two following errors :
    <b>** in log file dev_bootstrap</b> :
    [Thr 3720] *** ERROR => JHVM_LoadJavaVM: Cannot create Java VM (rc=-6) [jhvmxx.c     485]
    [Thr 3720] *** ERROR => Cannot load Java VM (server) (rc=-1) [jlnchxxi.c   591]
    [Thr 3720] JLaunchCloseProgram: good bye (exitcode=-1)
    and
    <b>** in log file dev_jcontrol :</b>
    [Thr 2288] *** ERROR => invalid return code of process [bootstrap] (exitcode=-1) [jstartxx.c   1452]
    [Thr 2288] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc=-1)
    [Thr 2288] JControlCloseProgram: started (exitcode = -1)
    [Thr 2288] JControlCloseProgram: good bye... (exitcode=-1)
    Does any one met this problem?
    I thank you in davance for the help you could give me.
    Regards.
    Karine TAVERNIER

    Hello Dan,
    I can only thank you!
    It was not easy to solve that problem, because people who installed that SAP instance has left the company, without having given any documentation or information.
    Then, thanks to OSS notes 723909/716604/736557, I solved my problem.
    What I did :
    As "my server" (MS Windows 2000) only got 500 Mo of RAM!, I must adapted some values, compraing with SAP notes.
    According to note 723909, for the dispatcher node, I increased the heap size to 70 Mo to 170 Mo .
    According to note 716604, for the serverID, I put the PermSize and MaxPermsize to 192 Mo.
    I decreased the Max Heap Size from 256 to 128 Mo.
    And the most important to my mind, as described in note 736557, I suppressed in file <i>instance.properties</i>, the line <i>bootstrap.MaxHeapSize=0</i> (and not 16 as in note!).
    Through the config tool, I put this value to 128 (instance node, instance_IDxx / Message Server & Bootstrap -> Max heap size).
    Then, at last, the J2EE Server started.
    I think some values may be changed to improve the respone time or the general behaviour of the application.
    I hope this message may help some other people.
    Many thanks.
    Kind regards.
    Karine.<i></i><i></i>

  • J2EE Server does not start

    Hi,
    I get the following trace when I try to start a newly installed J2EE Server. (sp11).
    The only errors I see are :
    [Thr 2108] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
    [Thr 2108] *** ERROR => Invalid property value [box.number/J2EJC00PALN00404448A] [jstartxx.c   789]
    Appreciate any help
    trc file: "C:\usr\sap\J2E\JC00\work\dev_jcontrol", trc level: 1, release: "640"
    node name   : jcontrol
    pid         : 3852
    system name : J2E
    system nr.  : 00
    started at  : Tue Sep 13 11:09:34 2005
    arguments   :
        arg[00] : C:\usr\sap\J2E\JC00\j2ee\os_libs\jcontrol.exe
        arg[01] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    [Thr 2108] Tue Sep 13 11:09:34 2005
    [Thr 2108] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
    [Thr 2108] *** ERROR => Invalid property value [box.number/J2EJC00PALN00404448A] [jstartxx.c   789]
    JStartupReadInstanceProperties: read instance properties [C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties;C:\usr\sap\J2E\JC00\SDM\program\config\sdm_jstartup.properties]
    -> ms host    : PALN00404448A
    -> ms port    : 3601
    -> OS libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> files [01] : C:\usr\sap\J2E\JC00\SDM\program\config\sdm_jstartup.properties
    Instance properties
    -> ms host    : PALN00404448A
    -> ms port    : 3601
    -> os libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap_ID5336850  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID5336800  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID5336850            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] ID5336800            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [02] sdm                  : C:\usr\sap\J2E\JC00\SDM\program\config\sdm_jstartup.properties
    [Thr 2108] Tue Sep 13 11:09:35 2005
    [Thr 2108] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
    [Thr 2108] [Node: bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [bootstrap]
    -> node name       : bootstrap
    -> node type       : bootstrap
    -> java path       : C:\j2sdk1.4.2_08
    -> java parameters : -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 512M
    -> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster
    -> class path      : .\bootstrap\launcher.jar
    -> OS libs path    : C:\usr\sap\J2E\JC00\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  : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0053368
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    JStartupStartJLaunch: program = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> arg[02] = -DSAPINFO=J2E_00_bootstrap
    -> arg[03] = -file=C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=bootstrap
    -> arg[05] = -nodeId=-1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_3852
    -> arg[07] = -jvmOutFile=C:\usr\sap\J2E\JC00\work\jvm_bootstrap.out
    -> arg[08] = -stdOutFile=C:\usr\sap\J2E\JC00\work\std_bootstrap.out
    -> arg[09] = -locOutFile=C:\usr\sap\J2E\JC00\work\dev_bootstrap
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> lib path = PATH=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    -> exe path = PATH=C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    [Thr 2108] Tue Sep 13 11:18:11 2005
    [Thr 2108] JControlExecuteBootstrap: read instance values after global bootstrap
    [Thr 2108] *** ERROR => Invalid property value [box.number/J2EJC00PALN00404448A] [jstartxx.c   789]
    [Thr 2108] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
    JStartupReadInstanceProperties: read instance properties [C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties;C:\usr\sap\J2E\JC00\SDM\program\config\sdm_jstartup.properties]
    -> ms host    : PALN00404448A
    -> ms port    : 3601
    -> OS libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    [Thr 2108] JControlExecuteBootstrap: enumerate the nodes after global bootstrap
    Used property files
    -> files [00] : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> files [01] : C:\usr\sap\J2E\JC00\SDM\program\config\sdm_jstartup.properties
    Instance properties
    -> ms host    : PALN00404448A
    -> ms port    : 3601
    -> os libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID5336800  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID5336850  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID5336800            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] ID5336850            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [02] sdm                  : C:\usr\sap\J2E\JC00\SDM\program\config\sdm_jstartup.properties
    [Thr 2108] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID5336800]
    [Thr 2108] INFO: Invalid property value [JLaunchParameters/]
    [Thr 2108] [Node: dispatcher bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [bootstrap_ID5336800]
    -> node name       : dispatcher bootstrap
    -> node type       : bootstrap
    -> java path       : C:\j2sdk1.4.2_08
    -> java parameters : -Djco.jarm=1 -Djco.jarm=1
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 170M
    -> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster
    -> class path      : .\bootstrap\launcher.jar
    -> OS libs path    : C:\usr\sap\J2E\JC00\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  : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID005336800
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    JStartupStartJLaunch: program = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> arg[02] = -DSAPINFO=J2E_00_bootstrap
    -> arg[03] = -file=C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=bootstrap_ID5336800
    -> arg[05] = -nodeId=-1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_3852
    -> arg[07] = -jvmOutFile=C:\usr\sap\J2E\JC00\work\jvm_bootstrap_ID5336800.out
    -> arg[08] = -stdOutFile=C:\usr\sap\J2E\JC00\work\std_bootstrap_ID5336800.out
    -> arg[09] = -locOutFile=C:\usr\sap\J2E\JC00\work\dev_bootstrap_ID5336800
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> lib path = PATH=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    -> exe path = PATH=C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    [Thr 2108] Tue Sep 13 11:19:24 2005
    [Thr 2108] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID5336850]
    [Thr 2108] INFO: Invalid property value [JLaunchParameters/]
    [Thr 2108] [Node: server0 bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [bootstrap_ID5336850]
    -> node name       : server0 bootstrap
    -> node type       : bootstrap
    -> java path       : C:\j2sdk1.4.2_08
    -> java parameters : -Djco.jarm=1 -Djco.jarm=1
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 512M
    -> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster
    -> class path      : .\bootstrap\launcher.jar
    -> OS libs path    : C:\usr\sap\J2E\JC00\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  : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID005336850
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    JStartupStartJLaunch: program = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> arg[02] = -DSAPINFO=J2E_00_bootstrap
    -> arg[03] = -file=C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=bootstrap_ID5336850
    -> arg[05] = -nodeId=-1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_3852
    -> arg[07] = -jvmOutFile=C:\usr\sap\J2E\JC00\work\jvm_bootstrap_ID5336850.out
    -> arg[08] = -stdOutFile=C:\usr\sap\J2E\JC00\work\std_bootstrap_ID5336850.out
    -> arg[09] = -locOutFile=C:\usr\sap\J2E\JC00\work\dev_bootstrap_ID5336850
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> lib path = PATH=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    -> exe path = PATH=C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    [Thr 2108] Tue Sep 13 11:25:08 2005
    [Thr 2108] JControlIBuildProcessList: Maximum error count is set to 4
    [Thr 2108] INFO: Invalid property value [JLaunchParameters/]
    [Thr 2108] [Node: dispatcher] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_08
    [Thr 1000] JControlRequestFunc: Thread 1000 started as listener thread for np messages.
    JStartupIReadSection: read node properties [ID5336800]
    -> node name       : dispatcher
    -> node type       : dispatcher
    -> java path       : C:\j2sdk1.4.2_08
    -> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Djco.jarm=1 -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=C:/usr/sap/J2E/SYS/global -XX:NewSize=28m -XX:MaxNewSize=28m -XX:+DisableExplicitGC
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 170M
    -> init heap size  : 170M
    -> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster\dispatcher
    -> class path      : .\bin\boot\boot.jar;.\bin\system\bytecode.jar;.
    -> OS libs path    : C:\usr\sap\J2E\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  : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      :
    -> debuggable      : no
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    [Thr 2108] INFO: Invalid property value [JLaunchParameters/]
    [Thr 2108] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [ID5336850]
    -> node name       : server0
    -> node type       : server
    -> java path       : C:\j2sdk1.4.2_08
    -> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djco.jarm=1 -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -verbose:gc -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=C:/usr/sap/J2E/SYS/global -XX:NewSize=85m -XX:MaxNewSize=85m -XX:MaxPermSize=192m -XX:PermSize=192m -XX:DisableExplicitGC -XX:UseParNewGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 512M
    -> init heap size  : 512M
    -> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster\server0
    -> class path      : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path    : C:\usr\sap\J2E\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  : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      :
    -> debuggable      : no
    -> debug mode      : no
    -> debug port      : 50021
    -> shutdown timeout: 120000
    [Thr 2108] Tue Sep 13 11:25:09 2005
    [Thr 2108] [Node: SDM] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [sdm]
    -> node name       : SDM
    -> node type       : sdm
    -> java path       : C:\j2sdk1.4.2_08
    -> java parameters :
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 128M
    -> root path       : C:\usr\sap\J2E\JC00\SDM\program
    -> class path      : C:\usr\sap\J2E\JC00\SDM\program\bin\SDM.jar
    -> OS libs path    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> main class      : SDMInternal
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
    -> shutdown class  : com.sap.sdm.jstartup.shutdown.InternalShutDown
    -> parameters      : server sdmhome=C:\usr\sap/J2E/JC00/SDM/program
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    [Thr 2108] Tue Sep 13 11:25:10 2005
    [Thr 2108] JControlMSConnect: attached to message server (PALN00404448A/3601)
    JStartupStartJLaunch: program = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> arg[02] = -DSAPINFO=J2E_00_dispatcher
    -> arg[03] = -file=C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=ID5336800
    -> arg[05] = -nodeId=0
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_3852
    -> arg[07] = -jvmOutFile=C:\usr\sap\J2E\JC00\work\jvm_dispatcher.out
    -> arg[08] = -stdOutFile=C:\usr\sap\J2E\JC00\work\std_dispatcher.out
    -> arg[09] = -locOutFile=C:\usr\sap\J2E\JC00\work\dev_dispatcher
    -> arg[10] = -mode=JCONTROL
    -> arg[11] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> lib path = PATH=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    -> exe path = PATH=C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    [Thr 2876] JControlMSMessageFunc: Thread 2876 started as listener thread for ms messages.
    [Thr 2108] JControlICheckProcessList: process dispatcher started (PID:3248)
    JStartupStartJLaunch: program = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> arg[02] = -DSAPINFO=J2E_00_server
    -> arg[03] = -file=C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=ID5336850
    -> arg[05] = -nodeId=1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_3852
    -> arg[07] = -locOutFile=C:\usr\sap\J2E\JC00\work\dev_server0
    -> arg[08] = -mode=JCONTROL
    -> arg[09] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> lib path = PATH=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    -> exe path = PATH=C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    [Thr 2108] JControlICheckProcessList: process server0 started (PID:4084)
    JStartupStartJLaunch: program = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> arg[02] = -DSAPINFO=J2E_00_sdm
    -> arg[03] = -file=C:\usr\sap\J2E\JC00\SDM\program\config\sdm_jstartup.properties
    -> arg[04] = -nodeName=sdm
    -> arg[05] = -nodeId=2
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_3852
    -> arg[07] = -jvmOutFile=C:\usr\sap\J2E\JC00\work\jvm_sdm.out
    -> arg[08] = -stdOutFile=C:\usr\sap\J2E\JC00\work\std_sdm.out
    -> arg[09] = -locOutFile=C:\usr\sap\J2E\JC00\work\dev_sdm
    -> arg[10] = -mode=JCONTROL
    -> arg[11] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> lib path = PATH=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    -> exe path = PATH=C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    [Thr 2108] JControlICheckProcessList: process SDM started (PID:3776)
    [Thr 2876] Tue Sep 13 11:25:32 2005
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] Tue Sep 13 11:25:44 2005
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] Tue Sep 13 11:27:18 2005
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server

    Hi,
    I get the following trace when I try to start a newly installed J2EE Server. (sp11).
    The only errors I see are :
    [Thr 2108] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
    [Thr 2108] *** ERROR => Invalid property value [box.number/J2EJC00PALN00404448A] [jstartxx.c   789]
    Appreciate any help
    trc file: "C:\usr\sap\J2E\JC00\work\dev_jcontrol", trc level: 1, release: "640"
    node name   : jcontrol
    pid         : 3852
    system name : J2E
    system nr.  : 00
    started at  : Tue Sep 13 11:09:34 2005
    arguments   :
        arg[00] : C:\usr\sap\J2E\JC00\j2ee\os_libs\jcontrol.exe
        arg[01] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    [Thr 2108] Tue Sep 13 11:09:34 2005
    [Thr 2108] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
    [Thr 2108] *** ERROR => Invalid property value [box.number/J2EJC00PALN00404448A] [jstartxx.c   789]
    JStartupReadInstanceProperties: read instance properties [C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties;C:\usr\sap\J2E\JC00\SDM\program\config\sdm_jstartup.properties]
    -> ms host    : PALN00404448A
    -> ms port    : 3601
    -> OS libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> files [01] : C:\usr\sap\J2E\JC00\SDM\program\config\sdm_jstartup.properties
    Instance properties
    -> ms host    : PALN00404448A
    -> ms port    : 3601
    -> os libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap_ID5336850  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID5336800  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID5336850            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] ID5336800            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [02] sdm                  : C:\usr\sap\J2E\JC00\SDM\program\config\sdm_jstartup.properties
    [Thr 2108] Tue Sep 13 11:09:35 2005
    [Thr 2108] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
    [Thr 2108] [Node: bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [bootstrap]
    -> node name       : bootstrap
    -> node type       : bootstrap
    -> java path       : C:\j2sdk1.4.2_08
    -> java parameters : -Djco.jarm=1 -Djco.jarm=1 -Djco.jarm=1
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 512M
    -> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster
    -> class path      : .\bootstrap\launcher.jar
    -> OS libs path    : C:\usr\sap\J2E\JC00\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  : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0053368
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    JStartupStartJLaunch: program = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> arg[02] = -DSAPINFO=J2E_00_bootstrap
    -> arg[03] = -file=C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=bootstrap
    -> arg[05] = -nodeId=-1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_3852
    -> arg[07] = -jvmOutFile=C:\usr\sap\J2E\JC00\work\jvm_bootstrap.out
    -> arg[08] = -stdOutFile=C:\usr\sap\J2E\JC00\work\std_bootstrap.out
    -> arg[09] = -locOutFile=C:\usr\sap\J2E\JC00\work\dev_bootstrap
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> lib path = PATH=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    -> exe path = PATH=C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    [Thr 2108] Tue Sep 13 11:18:11 2005
    [Thr 2108] JControlExecuteBootstrap: read instance values after global bootstrap
    [Thr 2108] *** ERROR => Invalid property value [box.number/J2EJC00PALN00404448A] [jstartxx.c   789]
    [Thr 2108] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
    JStartupReadInstanceProperties: read instance properties [C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties;C:\usr\sap\J2E\JC00\SDM\program\config\sdm_jstartup.properties]
    -> ms host    : PALN00404448A
    -> ms port    : 3601
    -> OS libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    [Thr 2108] JControlExecuteBootstrap: enumerate the nodes after global bootstrap
    Used property files
    -> files [00] : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> files [01] : C:\usr\sap\J2E\JC00\SDM\program\config\sdm_jstartup.properties
    Instance properties
    -> ms host    : PALN00404448A
    -> ms port    : 3601
    -> os libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID5336800  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID5336850  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID5336800            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] ID5336850            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [02] sdm                  : C:\usr\sap\J2E\JC00\SDM\program\config\sdm_jstartup.properties
    [Thr 2108] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID5336800]
    [Thr 2108] INFO: Invalid property value [JLaunchParameters/]
    [Thr 2108] [Node: dispatcher bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [bootstrap_ID5336800]
    -> node name       : dispatcher bootstrap
    -> node type       : bootstrap
    -> java path       : C:\j2sdk1.4.2_08
    -> java parameters : -Djco.jarm=1 -Djco.jarm=1
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 170M
    -> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster
    -> class path      : .\bootstrap\launcher.jar
    -> OS libs path    : C:\usr\sap\J2E\JC00\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  : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID005336800
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    JStartupStartJLaunch: program = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> arg[02] = -DSAPINFO=J2E_00_bootstrap
    -> arg[03] = -file=C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=bootstrap_ID5336800
    -> arg[05] = -nodeId=-1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_3852
    -> arg[07] = -jvmOutFile=C:\usr\sap\J2E\JC00\work\jvm_bootstrap_ID5336800.out
    -> arg[08] = -stdOutFile=C:\usr\sap\J2E\JC00\work\std_bootstrap_ID5336800.out
    -> arg[09] = -locOutFile=C:\usr\sap\J2E\JC00\work\dev_bootstrap_ID5336800
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> lib path = PATH=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    -> exe path = PATH=C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    [Thr 2108] Tue Sep 13 11:19:24 2005
    [Thr 2108] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID5336850]
    [Thr 2108] INFO: Invalid property value [JLaunchParameters/]
    [Thr 2108] [Node: server0 bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [bootstrap_ID5336850]
    -> node name       : server0 bootstrap
    -> node type       : bootstrap
    -> java path       : C:\j2sdk1.4.2_08
    -> java parameters : -Djco.jarm=1 -Djco.jarm=1
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 512M
    -> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster
    -> class path      : .\bootstrap\launcher.jar
    -> OS libs path    : C:\usr\sap\J2E\JC00\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  : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID005336850
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    JStartupStartJLaunch: program = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> arg[02] = -DSAPINFO=J2E_00_bootstrap
    -> arg[03] = -file=C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=bootstrap_ID5336850
    -> arg[05] = -nodeId=-1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_3852
    -> arg[07] = -jvmOutFile=C:\usr\sap\J2E\JC00\work\jvm_bootstrap_ID5336850.out
    -> arg[08] = -stdOutFile=C:\usr\sap\J2E\JC00\work\std_bootstrap_ID5336850.out
    -> arg[09] = -locOutFile=C:\usr\sap\J2E\JC00\work\dev_bootstrap_ID5336850
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> lib path = PATH=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    -> exe path = PATH=C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    [Thr 2108] Tue Sep 13 11:25:08 2005
    [Thr 2108] JControlIBuildProcessList: Maximum error count is set to 4
    [Thr 2108] INFO: Invalid property value [JLaunchParameters/]
    [Thr 2108] [Node: dispatcher] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_08
    [Thr 1000] JControlRequestFunc: Thread 1000 started as listener thread for np messages.
    JStartupIReadSection: read node properties [ID5336800]
    -> node name       : dispatcher
    -> node type       : dispatcher
    -> java path       : C:\j2sdk1.4.2_08
    -> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Djco.jarm=1 -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=C:/usr/sap/J2E/SYS/global -XX:NewSize=28m -XX:MaxNewSize=28m -XX:+DisableExplicitGC
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 170M
    -> init heap size  : 170M
    -> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster\dispatcher
    -> class path      : .\bin\boot\boot.jar;.\bin\system\bytecode.jar;.
    -> OS libs path    : C:\usr\sap\J2E\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  : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      :
    -> debuggable      : no
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    [Thr 2108] INFO: Invalid property value [JLaunchParameters/]
    [Thr 2108] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [ID5336850]
    -> node name       : server0
    -> node type       : server
    -> java path       : C:\j2sdk1.4.2_08
    -> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djco.jarm=1 -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -verbose:gc -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=C:/usr/sap/J2E/SYS/global -XX:NewSize=85m -XX:MaxNewSize=85m -XX:MaxPermSize=192m -XX:PermSize=192m -XX:DisableExplicitGC -XX:UseParNewGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 512M
    -> init heap size  : 512M
    -> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster\server0
    -> class path      : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path    : C:\usr\sap\J2E\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  : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      :
    -> debuggable      : no
    -> debug mode      : no
    -> debug port      : 50021
    -> shutdown timeout: 120000
    [Thr 2108] Tue Sep 13 11:25:09 2005
    [Thr 2108] [Node: SDM] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [sdm]
    -> node name       : SDM
    -> node type       : sdm
    -> java path       : C:\j2sdk1.4.2_08
    -> java parameters :
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 128M
    -> root path       : C:\usr\sap\J2E\JC00\SDM\program
    -> class path      : C:\usr\sap\J2E\JC00\SDM\program\bin\SDM.jar
    -> OS libs path    : C:\usr\sap\J2E\JC00\j2ee\os_libs
    -> main class      : SDMInternal
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
    -> shutdown class  : com.sap.sdm.jstartup.shutdown.InternalShutDown
    -> parameters      : server sdmhome=C:\usr\sap/J2E/JC00/SDM/program
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    [Thr 2108] Tue Sep 13 11:25:10 2005
    [Thr 2108] JControlMSConnect: attached to message server (PALN00404448A/3601)
    JStartupStartJLaunch: program = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> arg[02] = -DSAPINFO=J2E_00_dispatcher
    -> arg[03] = -file=C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=ID5336800
    -> arg[05] = -nodeId=0
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_3852
    -> arg[07] = -jvmOutFile=C:\usr\sap\J2E\JC00\work\jvm_dispatcher.out
    -> arg[08] = -stdOutFile=C:\usr\sap\J2E\JC00\work\std_dispatcher.out
    -> arg[09] = -locOutFile=C:\usr\sap\J2E\JC00\work\dev_dispatcher
    -> arg[10] = -mode=JCONTROL
    -> arg[11] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> lib path = PATH=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    -> exe path = PATH=C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    [Thr 2876] JControlMSMessageFunc: Thread 2876 started as listener thread for ms messages.
    [Thr 2108] JControlICheckProcessList: process dispatcher started (PID:3248)
    JStartupStartJLaunch: program = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> arg[02] = -DSAPINFO=J2E_00_server
    -> arg[03] = -file=C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=ID5336850
    -> arg[05] = -nodeId=1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_3852
    -> arg[07] = -locOutFile=C:\usr\sap\J2E\JC00\work\dev_server0
    -> arg[08] = -mode=JCONTROL
    -> arg[09] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> lib path = PATH=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    -> exe path = PATH=C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    [Thr 2108] JControlICheckProcessList: process server0 started (PID:4084)
    JStartupStartJLaunch: program = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> arg[02] = -DSAPINFO=J2E_00_sdm
    -> arg[03] = -file=C:\usr\sap\J2E\JC00\SDM\program\config\sdm_jstartup.properties
    -> arg[04] = -nodeName=sdm
    -> arg[05] = -nodeId=2
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_3852
    -> arg[07] = -jvmOutFile=C:\usr\sap\J2E\JC00\work\jvm_sdm.out
    -> arg[08] = -stdOutFile=C:\usr\sap\J2E\JC00\work\std_sdm.out
    -> arg[09] = -locOutFile=C:\usr\sap\J2E\JC00\work\dev_sdm
    -> arg[10] = -mode=JCONTROL
    -> arg[11] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_PALN00404448A
    -> lib path = PATH=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    -> exe path = PATH=C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\apache-ant-1.6.3\bin;C:\usr\sap\Python\.;C:\j2sdk1.4.2_06\bin;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Studio Max;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\MySQL\MySQL Server 4.1\bin;C:\Program Files\Perforce;C:\Program Files\Common Files\OpSession\Shared;C:\Program Files\Common Files\OpSession\Viewer Shared
    [Thr 2108] JControlICheckProcessList: process SDM started (PID:3776)
    [Thr 2876] Tue Sep 13 11:25:32 2005
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] Tue Sep 13 11:25:44 2005
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] Tue Sep 13 11:27:18 2005
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2876] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server

  • J2EE Does Not Start During JAVA Add-In Installation

    I'm installing Java Add-In onto ERP 2004 (Windows 2000, Oracle 9.2, Java 2 SDK 1.4.2_08).
    The J2EE does not start during the installation. It gives up after some time. java -version shows the correct path.
    dev_jcontrol shows the following:
    [Thr 2624] Tue Aug 02 09:49:32 2005
    [Thr 2624] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
    [Thr 2624] [Node: bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_08
    [Thr 2624] *** ERROR => JStartupIGetJDKInfo: Cannot find Java class file [./JdkDetection_3516.class]. [jstartxxi.c  899]
    [Thr 2624] *** ERROR => can't get JDK information (rc=-1) [jstartxxi.c  1096]
    [Thr 2624] *** ERROR => node [bootstrap] not found [jstartxx.c   1388]
    [Thr 2624] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc=-18)
    [Thr 2624] JControlCloseProgram: started (exitcode = -18)
    [Thr 2624] JControlCloseProgram: good bye... (exitcode=-18)

    In that case, do u have multiple versions of JDKs installed ?
    Maybe some earlier version is installed too ! In that case there is a program that comes along with the JDK to choose the version of the JDK that needs to be loaded into memory.
    We faced this problem when we were doing our stints with JAVA Add-In wherein the system required the newest version of java where as some tool which was installed on the system required the older version.
    So we used the java program to select the version to be loaded whenever the operating system tried loading the jdk.

  • J2EE 5 sneak preview:Server does not start

    Hi,
    I need some help since after installation of the sneak preview 5 I could not start the server.
    The db and the central instance are running but not the server.
    1)I get always time out error"StartWait
    FAIL: process jstart.exe J2EE Server not running
    The WAS is installed on a USB2 hard disk.
    2)Furtheremore I cannot operate on the SAP management Console since I get Authorization error.
    I installed the was with windows user IT/paceg
    which is by Domain IT accessible even if I am not in the Domain.
    Anyone can help me,please?
    thanks
    Bye,
    Giamma
    ===================================================
    ============== Starting System JP1 ================
    ===================================================
    =============== Starting database instance ...
    Servizio richiesto già avviato.
    Ulteriori informazioni sono disponibili digitando NET HELPMSG 2182.
    The MaxDB Database Starter, Version 7.6.00.33
    Copyright 2000-2006 by SAP AG
    OK
    ============== Starting central services instance ...
    09.10.2006 12:37:21
    Start
    OK
    09.10.2006 12:37:21
    StartWait
    OK
    ============== Starting java instance ...
    09.10.2006 12:37:21
    Start
    OK
    09.10.2006 12:38:36
    StartWait
    FAIL: process jstart.exe J2EE Server not running
    ============== Start operation timed out !
    Premere un tasto per continuare . . .

    Just for update:
    The error means that the message server is not able to translate the IP address into the hostname (reverse name lookup). If this fails the Startup Framework cannot connect to the message server and the server does not start. Please check the network setup on this host.
    Replay:
    thanks to all.
    all is done:Just insert my loopback ip 10.10.0.10 in file host resolving on my host name romnb120.
    Regards Galin

  • 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

  • HTTP Server does not start -- 9ias 1.0.2.2.0

    HTTP Server does not start -- 9ias 1.0.2.2.0
    Installed 9iAS Enterprise Edition. Whole installation went well. Finally when I reboot the machine, the HTTP Service does not start.
    When I try to start the service it gives "Could not start OracleiSuitesHTTP server service on \\clwrd1 Error: 2140 An internal Windows NT Error Occured"
    Event log does not show any errors..
    Any help is appreciated.
    Thanks
    Bala

    I have Oracle 9iAS installed but sometimes the HTTP server stops responding. it searches for all the .html files. but it can not find the .jsp files in the specified path. is there anything wrong with the apache configuration?
    httpd.conf is perfectly alright.
    It give the following error
    Request URI:/testFile.jsp
    Exception:
    javax.servlet.ServletException: java.io.FileNotFoundException: ...\testFile.jsp (The system cannot find the file specified)
    now what to do??
    plz help
    thanx
    ketan malekar
    ([email protected])

  • Application server does not start for DMO

    Hi,
    I have a HR91DMO system on Win 2008.
    Application server does not start. From Tuxedolog :
    105938.IRNTSV-DVPSPJ2!PSAPPSRV.4728.4944.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
    105938.IRNTSV-DVPSPJ2!tmboot.244.3628.-2: tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handlerAnd here is my cfg file :
    ;=========================================================================
    ; Database Signon settings
    ;=========================================================================
    DBName=MYDB
    DBType=ORACLE
    UserId=PTWEBSERVER
    UserPswd=***
    ConnectId=people
    ConnectPswd=***people user can connect in sqlplus to DB. SYSADM can connect via datamover.
    Any help ? thank you.

    SELECT CLASSID, STARTAPPSERVER FROM PSCLASSDEFN
    WHERE CLASSID IN (SELECT OPRCLASS FROM PSOPRCLS WHERE OPRID='<OPRID>')
    If above sql returns a row where STARTAPPSERVER=1, then the user <OPRID> can start the application server.
    If not update a permission list <CLASSID> that is assigned to <OPRID> (result aboce sql), using below sql.
    UPDATE PSCLASSDEFN SET STARTAPPSERVER=1 WHERE CLASSID='<CLASSID>'
    Also see the installation manual CHAPTER 8A - Configuring the Application Server on Windows - Prerequisites
    Hakan

  • The Connection Server does not start after an upgrade to BO4.1 SP3

    Hello guys,
    The Connection Server does not start after an upgrade to BO4.1 SP3
    We are in process to upgrade our Business Objects environments to BO4.1 SP3
    The first 2 environments , the upgrade went fine. But the third environment de connection server won’t start.
    When I always try to start it returns me a failed status and shows me that the server is considered failed because it has stopped 5 time(s) in 60 minute(s).
    Our OS is AIX
    Uncaught Exception in SilentScope: [CS] Ser
    verInitialization::InitManager::Initialize: 0.007^^
    The CS initialization failed within the CS server. Aborting
    trc file: "connectionserver_BIO.ConnectionServer_ncs.trc", trc level: 1, release: "720"
    Gerd

    Hi Amine
    The File seems ok
    File from the failing connection server
    -rw-rw---- 1 bioadm bosys 43993 Apr 11 11:29 boconfig.cfg
    File from our test system
    -rw-rw---- 1 bitadm bosys 43892 Apr 14 10:56 boconfig.cfg
    I created a new connectieserver(by the copy function), but the new server won't start.
    Regards
    Gerd
    Log
    |89d4a6e0-2a89-7a05-3020-a51d517ab872|2014 04 14 11:54:30:113|+0200|Error| |>>|E| |connectionserver_BIO.ConnectionServer|28246236|3097|| |0|0|0|0|-|-|-|-|-|-||||||||||||[CS] Unhandled exception raised during CS initialization.
    init_srv.cpp:95:-: TraceLog message 3
    |4dcf04b1-1e1d-df13-48ad-a67f06e29864|2014 04 14 11:54:30:113|+0200|Error| |<<|E|X|connectionserver_BIO.ConnectionServer|28246236|3097|| |0|0|0|0|-|-|-|-|-|-||||||||||||Uncaught Exception in SilentScope: [CS] ServerInitialization::InitManager::Initialize: 0.003
    |77ad78f4-37f7-3013-3b50-85cce9fbe7b8|2014 04 14 11:54:30:113|+0200|Error| |>>|E| |connectionserver_BIO.ConnectionServer|28246236|3097|| |0|0|0|0|-|-|-|-|-|-||||||||||||[CS] The CS initialization failed within the CS server. Aborting.

  • Crstal Report Server does not working on installation of Crystal Design

    Hi,
    I had installed Crystal Report Server 2008 on a machine, I was able to login and open the CMC console as well but on installation of Crystal Desing the CMC and inforview are not opening. its displaying some dll file is missing.
    Kindly inform whether Server does not work after installation of Design on the same machine.
    Thanks & Regards
    PNN  Murthy

    Questions related to ASP.NET should be posted in the ASP.NET forums (http://forums.asp.net ).

  • Oracle service, Listener and http server does not start automatically

    Hello,
    I have Oracle 9i release 2 installed on Unix HP box if system restart in case of power failure the Oracle service, Listener and http server does not start automatically, is there any ready reference available to check what's wrong is happening(I don't have knowledge of Unix).
    Thanks, Khawar.

    Hi Rajesh,
    Thanks for reply, I will check this link and will be back if facing problem.
    Regards, Khawar.

  • Connection Server does not start

    Hello guys,
    The Connection Server does not start anymore.
    When I always try to start it returns me a failed status and shows me that the server is considered failed because it has stopped 5 time(s) in 60 minute(s).
    It's a BOE XI 3.1 SP2 with IK 3.1 SP2 installed on a Windows 2003 Server.
    BO XI database is on a SQL Server and all tables are there and seems to be OK
    The log file for the connectserver via trace is below :
    2010/01/28 19:06:43.339|>>| | | 4524|4528| |||||||||||||||TraceLog::Admin: logdir ('C:/Program Files/Business Objects/BusinessObjects Enterprise 12.0/Logging/')
    2010/01/28 19:06:43.339|>>| | | 4524|4528| |||||||||||||||TraceLog::Admin: update ()
    2010/01/28 19:06:43.339|==| | | 4524|4528| |||||||||||||||TraceBridge::Initialize: pullable set to 1
    2010/01/28 19:06:43.339|==| | | 4524|4528| |||||||||||||||TraceLog state:
    // device_info
    // process        (process#pid)   = ConnectionServer#4524
    // device         (name#deviceid) = ConnectionServer#MainDevice
    // pull/push      (pullable)      = Pull
    // pull mode settings
    //   configfile   (ini)           = C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\Logging\logConfig\BO_trace.ini
    //   every ... s  (period)        = 60
    // config
    active        = true;
    severity      = 'W';
    importance    = '<<';
    keep          = true;
    always_close  = false;
    log_dir       = "C:/Program Files/Business Objects/BusinessObjects Enterprise 12.0/Logging/";
    2010/01/28 19:06:43.402|==| | | 4524|4528| |||||||||||||||SIServerController:run: Fail to initialize or uninitialize.  Reason is The root server reported an error Unknown.:
    2010/01/28 19:06:43.402|==| | | 4524|4544| |||||||||||||||SIServiceStopThread::run: SIServiceStopThread::run exited
    2010/01/28 19:06:43.402|==| | | 4524|4528| |||||||||||||||CsContainer::uninitialize
    2010/01/28 19:06:43.402|==| | | 4524|4528| |||||||||||||||TransientObjectMonitor stopMonitor()...
    .\siserver.cpp:974: TraceLog message 11
    2010/01/28 19:06:43.402|>>|A| | 4524|4528| |||||||||||||||assert failure: (.\siserver.cpp:974). (false : SIServerController::run: Unknown exception caught in server's uninitialization function).
    Any help please?!
    thank you very much.
    Cesar

    Hello,
    I have the same problem (Connection Server does not start).
    I'am under BOXI R2 SP6 (unix) and i have this error in my log when i want to start ConnectionServer :
    Timestamp       ProcessID       ThreadID        Message
    [Fri May  7 07:37:09 2010]      31154   1103673168      Log: level=3 cat=1 msg=35100 p=ConnectionServer started
    [Fri May  7 07:37:09 2010]      31154   1103673168      trace message: SIServerController::run: Before initialize
    [Fri May  7 07:37:09 2010]      31154   1103673168      (sidaemon.cpp:416): trace message: SUNIXDaemon::init: starting
    [Fri May  7 07:37:09 2010]      31154   1103673168      trace message: SUNIXDaemon::init: redirecting stdio to /dev/null
    [Fri May  7 07:37:09 2010]      31154   1103673168      (sidaemon.cpp:209): trace message: installing fg terminiation handler
    [Fri May  7 07:37:09 2010]      31154   1103673168      (sidaemon.cpp:220): trace message: installing abnormal sys handler
    [Fri May  7 07:37:09 2010]      31154   1103673168      (sidaemon.cpp:506): trace message: SUNIXDaemon::init: finished
    [Fri May  7 07:37:09 2010]      31154   1103673168      Log: level=0 cat=14 msg=35101 p=The root server reported an error Unknown.
    [Fri May  7 07:37:09 2010]      31154   1103673168      trace message: SIServerController:run: Fail to initialize or uninitialize.  Reason is The root server reported an error Un
    known.:
    [Fri May  7 07:37:09 2010]      31154   1103673168      trace message: CsContainer::uninitialize
    [Fri May  7 07:37:09 2010]      31154   1103673168      trace message: TransientObjectMonitor stopMonitor()...
    [Fri May  7 07:37:09 2010]      31154   1103673168      Log: level=0 cat=14 msg=35101 p=The root server reported an error Internal Error. (Reason: Unknown exception caught in ser
    ver).
    [Fri May  7 07:37:09 2010]      31154   1103673168      assert failure: (siserver.cpp:953). (false : SIServerController::run: Unknown exception caught in server's uninitializatio
    n function
    [Fri May  7 07:37:09 2010]      31154   1103673168      Log: level=3 cat=1 msg=35100 p=ConnectionServer stopped
    Any idea ?
    Thanks.

  • Calendar server does not start

    We installed an OCS onebox 90411 on Win 2000 Server in january. Since last week calendar server does not start:
    D:\ocs_onebox\mtier\ocal\bin\unistart
    unistart: Oracle Calendar Server 9.0.4
    unistart: Copyright (c) 1993, 2003, Oracle.
    unistart: All rights reserved.
    unistart:
    unistart: Starting the Calendar Lock Manager
    unistart [error]: Error starting the Calendar Lock Manager
    unistart [error]: More details can be found in 'D:\ocs_onebox\mtier\ocal\log\unistart.log'
    unistart [error]: and in 'D:\ocs_onebox\mtier\ocal\log\lck.log'.
    Last entry in lck.log is from january.
    Last entries in unistart.log:
    DATE = Wed Apr 14 21:44:02.718 2004
    PID = 5336; TID = 5332
    ERROR CODE -> 0x50B05
    FUNCTION NAME -> ADM_Service::Start()
    SIS_ServerStart failed ((unilckd) SIS_ServerStart: StartService error :1069,Der Dienst konnte wegen einer fehlerhaften Anmeldung nicht gestartet werden. )
    DATE = Wed Apr 14 21:44:02.734 2004
    PID = 5336; TID = 5332
    ERROR CODE -> 0x50B05
    FUNCTION NAME -> Unistart::ProcessLocalStartServer()
    Error starting the Calendar Lock Manager. (unilckd) SIS_ServerStart: StartService error :1069,Der Dienst konnte wegen einer fehlerhaften Anmeldung nicht gestartet werden.
    Any idea ?

    Hi,
    Please log a TAR for this issue.
    Thanks,
    Lily

  • Oracle Fulfillment server does not start and also my concurrent manager is

    The oracle Fulfillment server does not start and also my concurrent manager is down, when ever iam trying to start them i getting error.
    even i restarted my laptop many times
    Iam using WINXP on my laptop.
    Pls help someone
    hsawwan
    Posts: 11,859
    Registered: 03/13/06
    Re: oracle Fulfillment server and concurrent manager problem
    Posted: Oct 13, 2008 9:26 AM in response to: user578071 Reply
    What is the error?
    What does CM log file say?
    Please run cmclean.sql and try to start the CM then.
    Note: 134007.1 - CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables
    https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=134007.1
    where should i run in apps schema or some other schema, where can i find the log
    as iam using r12

    Duplicate thread ..
    oracle Fulfillment server and concurrent manager problem
    Re: oracle Fulfillment server and concurrent manager problem

  • 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.

Maybe you are looking for

  • How to find custom forms in FND_FORM

    Hi All, I Retrieved data from fnd_form table.I got total forms.But i want only custom forms.How to find custom forms.How to retrieve only custom forms. Thanks& Regards, Raghu

  • Load balancing with A-Gate

    Hi All, I wish to configure my single W-Gate (Linux) to load balance with 2 A-Gate (Window). Can anyone help? Regards Lauran

  • IfsSession.disconnect( ) is throwin an exception. why

    ifsSession.disconnect() is throwin the following exception.. what's the reason for this?? Exception in thread "main" org.omg.CORBA.BAD_OPERATION: The delegate has not been set! minor code: 0 completed: No at org.omg.CORBA.portable.ObjectImpl._get_del

  • OS System

    Hi, I have a Macbook with OS system Mac OS X 10.6.8 (10K549) and shall update to the new lion. This Mac OS X 10.6.8 is Snow Leopard or? It says I have to have this version so I just need to be sure.

  • Why is the centroid calculating incorrectly?

    I have an image which is a signed int16 with no mask hooked up (externally masked). The IMAQ centroid vi is reporting the center of the ROI instead of providing the answer to the centroid. Why is it doing this? Solved! Go to Solution.