Server Process  is not running in the  WAS  JAVA

Hi,
The WAS JAVA  have the resources Netweaver7.0 and java is j2sdk1.4.2_13 version Operating system is Windows2003 and database server is SQLserver2005.
Previously it was running properly Now it giving the following Error.
Any one of you please give me suggestions how to solve it .
Devolper trace for the jcontol.exe process is as follows
trc file: "D:\usr\sap\NW2\JC02\work\dev_jcontrol", trc level: 1, release: "700"
node name   : jcontrol
pid         : 4516
system name : NW2
system nr.  : 02
started at  : Mon Mar 24 17:07:20 2008
arguments       :
       arg[00] : D:\usr\sap\NW2\JC02\exe\jcontrol.EXE
       arg[01] : pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] *** WARNING => INFO: Unknown property [instance.box.number=NW2JC02mmsr17] [jstartxx.c   841]
[Thr 4512] *** WARNING => INFO: Unknown property [instance.en.host=mmsr17] [jstartxx.c   841]
[Thr 4512] *** WARNING => INFO: Unknown property [instance.en.port=3203] [jstartxx.c   841]
[Thr 4512] *** WARNING => INFO: Unknown property [instance.system.id=2] [jstartxx.c   841]
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties;D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties]
-> ms host    : mmsr17
-> ms port    : 3903
-> OS libs    : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> Admin URL  :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Used property files
-> files [00] : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> files [01] : D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
Instance properties
-> ms host    : mmsr17
-> ms port    : 3903
-> os libs    : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> admin URL  :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Bootstrap nodes
-> [00] bootstrap            : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [01] bootstrap_ID28653700 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [02] bootstrap_ID28653750 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID28653700           : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [01] ID28653750           : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [02] sdm                  : D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
[Thr 4512] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
[Thr 4512] [Node: bootstrap] java home is set by profile parameter
     Java Home: C:\j2sdk1.4.2_13
[Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
JStartupIReadSection: read node properties [bootstrap]
-> node name          : bootstrap
-> node type          : bootstrap
-> node execute       : yes
-> java path          : C:\j2sdk1.4.2_13
-> java parameters    : -Djco.jarm=1
-> java vm version    : 1.4.2_13-b06
-> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : x86
-> heap size          : 256M
-> root path          : D:\usr\sap\NW2\JC02\j2ee\cluster
-> class path         : .\bootstrap\launcher.jar
-> OS libs path       : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> main class         : com.sap.engine.offline.OfflineToolStart
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : D:\usr\sap\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
-> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0286537
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120000
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=bootstrap
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_bootstrap.out
-> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_bootstrap.out
-> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_bootstrap
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlExecuteBootstrap: read instance values after global bootstrap
[Thr 4512] *** WARNING => INFO: Unknown property [instance.box.number=NW2JC02mmsr17] [jstartxx.c   841]
[Thr 4512] *** WARNING => INFO: Unknown property [instance.en.host=mmsr17] [jstartxx.c   841]
[Thr 4512] *** WARNING => INFO: Unknown property [instance.en.port=3203] [jstartxx.c   841]
[Thr 4512] *** WARNING => INFO: Unknown property [instance.system.id=2] [jstartxx.c   841]
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties;D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties]
-> ms host    : mmsr17
-> ms port    : 3903
-> OS libs    : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> Admin URL  :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
[Thr 4512] JControlExecuteBootstrap: enumerate the nodes after global bootstrap
Used property files
-> files [00] : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> files [01] : D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
Instance properties
-> ms host    : mmsr17
-> ms port    : 3903
-> os libs    : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> admin URL  :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Bootstrap nodes
-> [00] bootstrap            : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [01] bootstrap_ID28653700 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [02] bootstrap_ID28653750 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID28653700           : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [01] ID28653750           : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [02] sdm                  : D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
[Thr 4512] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID28653700]
[Thr 4512] [Node: dispatcher bootstrap] java home is set by profile parameter
     Java Home: C:\j2sdk1.4.2_13
[Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
JStartupIReadSection: read node properties [bootstrap_ID28653700]
-> node name          : dispatcher bootstrap
-> node type          : bootstrap
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\j2sdk1.4.2_13
-> java parameters    : -Djco.jarm=1
-> java vm version    : 1.4.2_13-b06
-> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : x86
-> heap size          : 256M
-> root path          : D:\usr\sap\NW2\JC02\j2ee\cluster
-> class path         : .\bootstrap\launcher.jar
-> OS libs path       : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> main class         : com.sap.engine.offline.OfflineToolStart
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : D:\usr\sap\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
-> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID028653700
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120000
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=bootstrap_ID28653700
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_bootstrap_ID28653700.out
-> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_bootstrap_ID28653700.out
-> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_bootstrap_ID28653700
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID28653750]
[Thr 4512] [Node: server0 bootstrap] java home is set by profile parameter
     Java Home: C:\j2sdk1.4.2_13
[Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
JStartupIReadSection: read node properties [bootstrap_ID28653750]
-> node name          : server0 bootstrap
-> node type          : bootstrap
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\j2sdk1.4.2_13
-> java parameters    : -Djco.jarm=1
-> java vm version    : 1.4.2_13-b06
-> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : x86
-> heap size          : 256M
-> root path          : D:\usr\sap\NW2\JC02\j2ee\cluster
-> class path         : .\bootstrap\launcher.jar
-> OS libs path       : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> main class         : com.sap.engine.offline.OfflineToolStart
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : D:\usr\sap\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
-> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID028653750
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120000
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=bootstrap_ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_bootstrap_ID28653750.out
-> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_bootstrap_ID28653750.out
-> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_bootstrap_ID28653750
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlIBuildProcessList: Maximum error count is set to 4
[Thr 5144] JControlRequestFunc: Thread 5144 started as listener thread for np messages.
[Thr 4512] [Node: dispatcher] java home is set by profile parameter
     Java Home: C:\j2sdk1.4.2_13
[Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
JStartupIReadSection: read node properties [ID28653700]
-> node name          : dispatcher
-> node type          : dispatcher
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\j2sdk1.4.2_13
-> 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 -XX:NewSize=57m -XX:MaxNewSize=57m -XX:NewRatio=3 -XX:DisableExplicitGC -verbose:gc -XX:UseConcMarkSweepGC
-> java vm version    : 1.4.2_13-b06
-> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : x86
-> heap size          : 170M
-> init heap size     : 170M
-> root path          : D:\usr\sap\NW2\JC02\j2ee\cluster\dispatcher
-> class path         : .\bin\boot\boot.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : D:\usr\sap\NW2\JC02\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     : D:\usr\sap\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
-> parameters         :
-> debuggable         : no
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120000
[Thr 4512] [Node: server0] java home is set by profile parameter
     Java Home: C:\j2sdk1.4.2_13
[Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
JStartupIReadSection: read node properties [ID28653750]
-> node name          : server0
-> node type          : server
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\j2sdk1.4.2_13
-> 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 -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> java vm version    : 1.4.2_13-b06
-> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : x86
-> heap size          : 1024M
-> init heap size     : 1024M
-> root path          : D:\usr\sap\NW2\JC02\j2ee\cluster\server0
-> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : D:\usr\sap\NW2\JC02\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     : D:\usr\sap\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
-> parameters         :
-> debuggable         : yes
-> debug mode         : yes
-> debug port         : 50221
-> shutdown timeout   : 120000
[Thr 4512] INFO: Invalid property value [Debbugable=yes]
[Thr 4512] [Node: SDM] java home is set by profile parameter
     Java Home: C:\j2sdk1.4.2_13
[Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
JStartupIReadSection: read node properties [sdm]
-> node name          : SDM
-> node type          : sdm
-> node execute       : yes
-> java path          : C:\j2sdk1.4.2_13
-> java parameters    :
-> java vm version    : 1.4.2_13-b06
-> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : x86
-> heap size          : 256M
-> root path          : D:\usr\sap\NW2\JC02\SDM\program
-> class path         : D:\usr\sap\NW2\JC02\SDM\program\bin\SDM.jar
-> OS libs path       : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> main class         : SDMInternal
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : D:\usr\sap\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
-> shutdown class     : com.sap.sdm.jstartup.shutdown.InternalShutDown
-> parameters         : server sdmhome=D:\usr\sap\NW2\JC02\SDM\program
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120000
[Thr 4512] JControlMSConnect: attached to message server (mmsr17/3903)
[Thr 5340] JControlMSMessageFunc: Thread 5340 started as listener thread for ms messages.
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_dispatcher
-> arg[03] = -nodeId=0
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653700
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_dispatcher.out
-> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_dispatcher.out
-> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_dispatcher
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process dispatcher started (PID:5444)
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[10] = -mode=JCONTROL
-> arg[11] = -debugMode=yes
-> arg[12] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:4684)
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_sdm
-> arg[03] = -nodeId=2
-> arg[04] = -file=D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=sdm
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_sdm.out
-> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_sdm.out
-> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_sdm
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process SDM started (PID:5472)
[Thr 4512] JControlMSSendLogon: delete SDM logon information (rc=0)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlMSSendLogon: insert SDM logon information (port=50218; rc=0)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:4684) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (1)
[Thr 4512] JControlICheckProcessList: running flight recorder:
     C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856249 -bz D:\usr\sap\NW2\SYS\global
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = -debugMode=yes
-> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:3944)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:3944) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (2)
[Thr 4512] JControlICheckProcessList: running flight recorder:
     C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856314 -bz D:\usr\sap\NW2\SYS\global
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = -debugMode=yes
-> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 started (PID:4308)
[Thr 4512]  Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:4308) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (3)
[Thr 4512] JControlICheckProcessList: running flight recorder:
     C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856350 -bz D:\usr\sap\NW2\SYS\global
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = -debugMode=yes
-> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:2616)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:2616) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (4)
[Thr 4512] JControlICheckProcessList: running flight recorder:
     C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856405 -bz D:\usr\sap\NW2\SYS\global
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:10, argument:1 from pid:0
[Thr 5144] JControlIDumpStackTrace: dump stacktrace for server0
[Thr 5144] *** ERROR => Can't send command for stack dump (rc=-3) [jcntrxxi.c   1403]
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:19, argument:1 from pid:0
[Thr 5144] JControlITraceIncrement: increment trace level for server0
[Thr 5144] *** ERROR => Can't send command for trace level increment (rc=-3) [jcntrxxi.c   1434]
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:4, argument:1 from pid:0
[Thr 5144] JControlIEnableProcess: enable process server0
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = -debugMode=yes
-> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:3556)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:3556) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (5)
[Thr 4512] JControlICheckProcessList: running flight recorder:
     C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856490 -bz D:\usr\sap\NW2\SYS\global
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:4, argument:1 from pid:0
[Thr 5144] JControlIEnableProcess: enable process server0
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = -debugMode=yes
-> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:2872)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:2872) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (6)
[Thr 4512] JControlICheckProcessList: running flight recorder:
     C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189858000 -bz D:\usr\sap\NW2\SYS\global
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:10, argument:1 from pid:0
[Thr 5144] JControlIDumpStackTrace: dump stacktrace for server0
[Thr 5144] *** ERROR => Can't send command for stack dump (rc=-3) [jcntrxxi.c   1403]
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:4, argument:1 from pid:0
[Thr 5144] JControlIEnableProcess: enable process server0
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:4836)
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
[Thr 5144] JControlIProcessSoftKill: soft kill of process server0 (pid:4836)
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:4836) died (STOPPING)
[Thr 4512] JControlIResetProcess: reset process server0
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:5428)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:5428) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (7)
[Thr 4512] JControlICheckProcessList: running flight recorder:
     C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189860005 -bz D:\usr\sap\NW2\SYS\global
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:4, argument:1 from pid:0
[Thr 5144] JControlIEnableProcess: enable process server0
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:5196)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:5196) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (8)
[Thr 4512] JControlICheckProcessList: running flight recorder:
     C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189860117 -bz D:\usr\sap\NW2\SYS\global
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
Thanks,
Vivek

Hi Vivek,
FYI :
JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
The above message can be ignored. You will see that message often in perfectly up/running systems as well.
Also, the dev_jcontrol file shows that the server process was terminating !
You need to check std_server0.out file for the errors/exceptions as to why server0 was terminating abruptly. The reason should be apparent from dev_server0 and std_server0 most of the times unless its a startup framework bug where the error messages are not written to the log files.
So, whenever the server process or dispatcher process fails to start, you should check the corresponding dev_server<n> or dev_dispatcher and std_server<n> / std_dispatcher  files. Also, usually, there will be some exception (if its application related) in the defaultrace file as well under server<n>\log or dispatcher\log depending on which one is failing to start.
e.g. if server0 is failing to start due to some UME issues, you will see the mention of it in std_server0.out (definitely) and more ellaborate info/exceptions in deafultrace under server0\log as well.
Hope the above helps.

Similar Messages

  • Server Process  is not running

    Hi,
    This is the defaulttrace file content, can any one give me idea how to solve.This server contain only WAS JAVA.
    Server0 log file
    #1.5#02004C4F4F500065000000E000000BE800043A7C9D203457#1190206793437#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#Administrator#9783####35db644066b011dcce2002004c4f4f50#SAPEngine_Application_Thread[impl:3]_25##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.masthead on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.masthead#library:com.sap.portal.common#
    #1.5#02004C4F4F500058000000FE00000BE800043A7C9D4D3E17#1190206796390#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9767##mmsr17_NW2_28653750#abb#372b8af066b011dcad7802004c4f4f50#SAPEngine_Application_Thread[impl:3]_1##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F50005D000000E900000BE800043A7C9F17D3A1#1190206826328#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.deployment#Administrator#9787####49b1ab5066b011dcced602004c4f4f50#SAPEngine_Application_Thread[impl:3]_19##0#0#Info#1#com.sap.portal.prt.runtime.deployment#Plain###Deploying application: com.sap.portal.navigation.masthead#
    #1.5#02004C4F4F50005D000000EA00000BE800043A7C9F1D63A7#1190206826703#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.loader#Administrator#9787####49b1ab5066b011dcced602004c4f4f50#SAPEngine_Application_Thread[impl:3]_19##0#0#Info#1#com.sap.portal.prt.runtime.loader#Plain###Loading application: com.sap.portal.navigation.masthead#
    #1.5#02004C4F4F50005D000000EB00000BE800043A7C9F1D6546#1190206826703#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#Administrator#9787####49b1ab5066b011dcced602004c4f4f50#SAPEngine_Application_Thread[impl:3]_19##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.masthead on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.masthead#library:com.sap.portal.common#
    #1.5#02004C4F4F500069000000CD00000BE800043A7C9F4D251D#1190206829828#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9767##mmsr17_NW2_28653750#abb#4b1755d066b011dcc24b02004c4f4f50#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F5000580000010200000BE800043A7CB4AFA08D#1190207188609#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.deployment#Administrator#9825####21b496c066b111dcc3dd02004c4f4f50#SAPEngine_Application_Thread[impl:3]_1##0#0#Info#1#com.sap.portal.prt.runtime.deployment#Plain###Deploying application: com.sap.portal.navigation.masthead#
    #1.5#02004C4F4F5000580000010300000BE800043A7CB4B5ECD8#1190207189031#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.loader#Administrator#9825####21b496c066b111dcc3dd02004c4f4f50#SAPEngine_Application_Thread[impl:3]_1##0#0#Info#1#com.sap.portal.prt.runtime.loader#Plain###Loading application: com.sap.portal.navigation.masthead#
    #1.5#02004C4F4F5000580000010400000BE800043A7CB4B5EE77#1190207189031#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#Administrator#9825####21b496c066b111dcc3dd02004c4f4f50#SAPEngine_Application_Thread[impl:3]_1##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.masthead on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.masthead#library:com.sap.portal.common#
    #1.5#02004C4F4F5000580000010500000BE800043A7CB51B942F#1190207195687#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9767##mmsr17_NW2_28653750#abb#2545acc066b111dcca2802004c4f4f50#SAPEngine_Application_Thread[impl:3]_1##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F500057000000AA00000BE800043A7CB70647BD#1190207227843#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9830##mmsr17_NW2_28653750#abb#397425f066b111dca5ca02004c4f4f50#SAPEngine_Application_Thread[impl:3]_16##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F50006B0000010000000BE800043A7CB9735CC9#1190207268546#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.deployment#Administrator#9835####515ebcc066b111dcc33602004c4f4f50#SAPEngine_Application_Thread[impl:3]_31##0#0#Info#1#com.sap.portal.prt.runtime.deployment#Plain###Deploying application: com.sap.portal.navigation.masthead#
    #1.5#02004C4F4F50006B0000010100000BE800043A7CB97BC4A7#1190207269109#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.loader#Administrator#9835####515ebcc066b111dcc33602004c4f4f50#SAPEngine_Application_Thread[impl:3]_31##0#0#Info#1#com.sap.portal.prt.runtime.loader#Plain###Loading application: com.sap.portal.navigation.masthead#
    #1.5#02004C4F4F50006B0000010200000BE800043A7CB97BC643#1190207269109#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#Administrator#9835####515ebcc066b111dcc33602004c4f4f50#SAPEngine_Application_Thread[impl:3]_31##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.masthead on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.masthead#library:com.sap.portal.common#
    #1.5#02004C4F4F50006B0000010300000BE800043A7CB9D88E77#1190207275187#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9830##mmsr17_NW2_28653750#abb#547fd2e066b111dcb02f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_31##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F500053000004FF00000BE800043A7CC3F90739#1190207445093#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.deployment#Administrator#9853####ba97620066b111dccdff02004c4f4f50#SAPEngine_Application_Thread[impl:3]_14##0#0#Info#1#com.sap.portal.prt.runtime.deployment#Plain###Deploying application: com.sap.portal.navigation.masthead#
    #1.5#02004C4F4F5000530000050000000BE800043A7CC3FE8D9F#1190207445453#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.loader#Administrator#9853####ba97620066b111dccdff02004c4f4f50#SAPEngine_Application_Thread[impl:3]_14##0#0#Info#1#com.sap.portal.prt.runtime.loader#Plain###Loading application: com.sap.portal.navigation.masthead#
    #1.5#02004C4F4F5000530000050100000BE800043A7CC3FE8F40#1190207445453#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#Administrator#9853####ba97620066b111dccdff02004c4f4f50#SAPEngine_Application_Thread[impl:3]_14##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.masthead on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.masthead#library:com.sap.portal.common#
    #1.5#02004C4F4F500069000000CF00000BE800043A7CC4D09825#1190207459218#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9830##mmsr17_NW2_28653750#abb#c24af89066b111dc852902004c4f4f50#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F500068000000F400000BE800043A7CC5D47C31#1190207476250#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.deployment#Administrator#9857####cd2bb33066b111dcc51302004c4f4f50#SAPEngine_Application_Thread[impl:3]_9##0#0#Info#1#com.sap.portal.prt.runtime.deployment#Plain###Deploying application: com.sap.portal.navigation.masthead#
    #1.5#02004C4F4F500068000000F500000BE800043A7CC5DA1A13#1190207476625#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.loader#Administrator#9857####cd2bb33066b111dcc51302004c4f4f50#SAPEngine_Application_Thread[impl:3]_9##0#0#Info#1#com.sap.portal.prt.runtime.loader#Plain###Loading application: com.sap.portal.navigation.masthead#
    #1.5#02004C4F4F500068000000F600000BE800043A7CC5DA1BC3#1190207476625#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#Administrator#9857####cd2bb33066b111dcc51302004c4f4f50#SAPEngine_Application_Thread[impl:3]_9##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.masthead on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.masthead#library:com.sap.portal.common#
    #1.5#02004C4F4F5000740000010E00000BE800043A7CC6163559#1190207480562#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9830##mmsr17_NW2_28653750#abb#cef7e7b066b111dc8cff02004c4f4f50#SAPEngine_Application_Thread[impl:3]_12##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F50006C0000013E00000BE800043A7CD65676A6#1190207753218#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.deployment#Administrator#9886####721bab2066b211dc8da302004c4f4f50#SAPEngine_Application_Thread[impl:3]_35##0#0#Info#1#com.sap.portal.prt.runtime.deployment#Plain###Deploying application: com.sap.portal.navigation.masthead#
    #1.5#02004C4F4F50006C0000013F00000BE800043A7CD65C1612#1190207753578#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.loader#Administrator#9886####721bab2066b211dc8da302004c4f4f50#SAPEngine_Application_Thread[impl:3]_35##0#0#Info#1#com.sap.portal.prt.runtime.loader#Plain###Loading application: com.sap.portal.navigation.masthead#
    #1.5#02004C4F4F50006C0000014000000BE800043A7CD65C17B6#1190207753578#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#Administrator#9886####721bab2066b211dc8da302004c4f4f50#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.masthead on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.masthead#library:com.sap.portal.common#
    #1.5#02004C4F4F500060000000E500000BE800043A7CD6B7B4BB#1190207759578#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9830##mmsr17_NW2_28653750#abb#755bbaf066b211dc844002004c4f4f50#SAPEngine_Application_Thread[impl:3]_8##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F5000670000010600000BE800043A7CDCB8F09B#1190207860328#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9830##mmsr17_NW2_28653750#abb#755bbaf066b211dc844002004c4f4f50#SAPEngine_Application_Thread[impl:3]_13##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F50006E000000FA00000BE800043A7CDCE31A93#1190207863093#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9830##mmsr17_NW2_28653750#abb#755bbaf066b211dc844002004c4f4f50#SAPEngine_Application_Thread[impl:3]_39##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F500060000000E700000BE800043A7CE24B0CA4#1190207953796#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9907##mmsr17_NW2_28653750#abb#e9abe24066b211dc8fd102004c4f4f50#SAPEngine_Application_Thread[impl:3]_8##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F50006D000000F600000BE800043A7CE51C9D48#1190208001093#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9907##mmsr17_NW2_28653750#abb#e9abe24066b211dc8fd102004c4f4f50#SAPEngine_Application_Thread[impl:3]_37##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F50005E000000BB00000BE800043A7CF8F9C059#1190208334359#/System/Server##com.sap.portal.activityreport#Guest#0####cd49627066b311dca3aa02004c4f4f50#SAPEngine_Application_Thread[impl:3]_15##0#0#Info#1#com.sap.portal.activityreport#Java###*--Flush data begin--*##
    #1.5#02004C4F4F50005E000000BC00000BE800043A7CF8FA31D2#1190208334390#/System/Server##com.sap.portal.activityreport#Guest#0####cd49627066b311dca3aa02004c4f4f50#SAPEngine_Application_Thread[impl:3]_15##0#0#Info#1#com.sap.portal.activityreport#Java###2 user ids saved##
    #1.5#02004C4F4F50005E000000BD00000BE800043A7CF8FA6CDF#1190208334406#/System/Server##com.sap.portal.activityreport#Guest#0####cd49627066b311dca3aa02004c4f4f50#SAPEngine_Application_Thread[impl:3]_15##0#0#Info#1#com.sap.portal.activityreport#Java###5 pages saved##
    #1.5#02004C4F4F50005E000000BE00000BE800043A7CF8FAAFCF#1190208334421#/System/Server##com.sap.portal.activityreport#Guest#0####cd49627066b311dca3aa02004c4f4f50#SAPEngine_Application_Thread[impl:3]_15##0#0#Info#1#com.sap.portal.activityreport#Java###4 iViews saved##
    #1.5#02004C4F4F50005E000000BF00000BE800043A7CF8FAB048#1190208334421#/System/Server##com.sap.portal.activityreport#Guest#0####cd49627066b311dca3aa02004c4f4f50#SAPEngine_Application_Thread[impl:3]_15##0#0#Info#1#com.sap.portal.activityreport#Java###*--Flush data end--*##
    #1.5#02004C4F4F50005E000000C000000BE800043A7CF8FAB09F#1190208334421#/System/Server##com.sap.portal.activityreport#Guest#0####cd49627066b311dca3aa02004c4f4f50#SAPEngine_Application_Thread[impl:3]_15##0#0#Info#1#com.sap.portal.activityreport#Java###Duration: 62 millis##
    #1.5#02004C4F4F50006F0000019800000BE800043A7D08467C02#1190208591046#/System/Server##com.sap.engine.services.deploy#Administrator#9974####6630e8a266b411dcbbbd02004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.engine.services.deploy#Plain###Operation stopApp on application local/LeaveRequestApproval finished for 15 ms.#
    #1.5#02004C4F4F50006F0000019900000BE800043A7D08467C8F#1190208591046#/System/Server##com.sap.engine.services.deploy#Administrator#9974####6630e8a266b411dcbbbd02004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application local/LeaveRequestApproval finished successfully on server 28653750#
    #1.5#02004C4F4F50006F0000019D00000BE800043A7D0848F897#1190208591218#/System/Server##com.sap.engine.services.deploy#Administrator#9974####6630e8a266b411dcbbbd02004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.engine.services.deploy#Plain###Operation startApp on application local/LeaveRequestApproval finished for 15 ms.#
    #1.5#02004C4F4F50006F0000019E00000BE800043A7D0848F917#1190208591218#/System/Server##com.sap.engine.services.deploy#Administrator#9974####6630e8a266b411dcbbbd02004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application local/LeaveRequestApproval finished successfully on server 28653750#
    #1.5#02004C4F4F50006F0000019F00000BE800043A7D0849117E#1190208591218#/System/Server##com.sap.engine.services.deploy#Administrator#9974####6630e8a266b411dcbbbd02004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation update over application local/LeaveRequestApproval finished successfully on server 28653750#
    #1.5#02004C4F4F50006F000001A000000BE800043A7D084911F9#1190208591218#/System/Server##com.sap.engine.services.deploy#Administrator#9974####6630e8a266b411dcbbbd02004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation update on application local/LeaveRequestApproval finished in whole cluster for 0 ms.#
    #1.5#02004C4F4F50006F000001A100000BE800043A7D0ADC615A#1190208634421#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###Aggregator Started...##
    #1.5#02004C4F4F50006F000001A200000BE800043A7D0ADCAFD3#1190208634453#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###Current Database Time: 24 Mar 2008 13:30:34 GMT##
    #1.5#02004C4F4F50006F000001A300000BE800043A7D0ADCB048#1190208634453#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java#####
    #1.5#02004C4F4F50006F000001A400000BE800043A7D0ADCB09F#1190208634453#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###*********** Aggregating data from 1 Jan 2007 00:00:34 GMT to 24 Mar 2008 13:30:34 GMT ***********##
    #1.5#02004C4F4F50006F000001A500000BE800043A7D0ADCB147#1190208634453#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###query = SELECT MAX(TIMESTAMPHOUR) FROM WCR_AGGINFO WHERE AGGREGATIONLEVEL = 'h'##
    #1.5#02004C4F4F50006F000001A600000BE800043A7D0ADCE534#1190208634468#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###First run at 3 Mar 2008 11:00:00 GMT##
    #1.5#02004C4F4F50006F000001A700000BE800043A7D0ADCE5B0#1190208634468#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###Aggregation not possible at least partailly done##
    #1.5#02004C4F4F50006F000001A800000BE800043A7D0ADD1519#1190208634468#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###SQL DELETE: DELETE FROM WCR_USERNODESTAT WHERE TIMESTAMPHOUR <= 1190208634450##
    #1.5#02004C4F4F50006F000001A900000BE800043A7D0ADD19BB#1190208634468#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###SQL DELETE: DELETE FROM WCR_WEBCNODESTAT WHERE TIMESTAMPHOUR <= 1190208634450##
    #1.5#02004C4F4F50006F000001AA00000BE800043A7D0ADD1D7E#1190208634468#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###SQL DELETE: DELETE FROM WCR_USERNODELOGON WHERE TIMESTAMPHOUR <= 1190208634450##
    #1.5#02004C4F4F50006F000001AB00000BE800043A7D0ADD20BF#1190208634484#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###SQL DELETE: DELETE FROM WCR_USERSTAT WHERE AGGREGATIONLEVEL = 'h' AND  TIMESTAMPHOUR <= 1187616634450##
    #1.5#02004C4F4F50006F000001AC00000BE800043A7D0ADD241D#1190208634484#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###SQL DELETE: DELETE FROM WCR_WEBCONTENTSTAT WHERE AGGREGATIONLEVEL = 'h' AND  TIMESTAMPHOUR <= 1187616634450##
    #1.5#02004C4F4F50006F000001AD00000BE800043A7D0ADD27D8#1190208634484#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###SQL DELETE: DELETE FROM WCR_AGGINFO WHERE AGGREGATIONLEVEL = 'h' AND  TIMESTAMPHOUR <= 1187616634450##
    #1.5#02004C4F4F50006F000001AE00000BE800043A7D0ADD2C60#1190208634484#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###Commit done##
    #1.5#02004C4F4F50006F000001AF00000BE800043A7D0ADD2E59#1190208634484#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###Aggregation took 47 millis##
    #1.5#02004C4F4F50005B000000DA00000BE800043A7D0F813F5D#1190208712343#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_27##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F50005F000000E800000BE800043A7D0FADB729#1190208715265#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_11##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F500066000000E000000BE800043A7D10F2BC5F#1190208736562#/System/Server#sap.com/irj#com.sap.portal.transport#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_17##0#0#Warning#1#com.sap.portal.transport#Plain###attributeToOptionValue: deprecated transport mode 'all' set in attribute, converting to new value 'data'.#
    #1.5#02004C4F4F500069000000D100000BE800043A7D15B9792B#1190208816687#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#eca3175066b411dc99de02004c4f4f50#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F50006A0000010100000BE800043A7D16093270#1190208821921#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#eca3175066b411dc99de02004c4f4f50#SAPEngine_Application_Thread[impl:3]_33##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F500057000000AC00000BE800043A7D1652F937#1190208826750#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#eca3175066b411dc99de02004c4f4f50#SAPEngine_Application_Thread[impl:3]_16##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F50005B000000DC00000BE800043A7D1664AD52#1190208827921#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#eca3175066b411dc99de02004c4f4f50#SAPEngine_Application_Thread[impl:3]_27##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F5000770000002400000BE800043A7D174BD7B4#1190208843062#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#Thread[PRT-Async 0,5,PRT-Async]##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F50005E000000C100000BE800043A7D174FCACE#1190208843328#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_15##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F500060000000E900000BE800043A7D1756E330#1190208843781#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_8##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F50005D000000F000000BE800043A7D17DC4673#1190208852531#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_19##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F5000760000000F00000BE800043A7D182CB14E#1190208857796#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#Thread[PRT-Async 1,5,PRT-Async]##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F50006A0000010300000BE800043A7D18302082#1190208858031#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_33##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F5000580000010900000BE800043A7D1836CF3D#1190208858468#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_1##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F500057000000AE00000BE800043A7D18738CEA#1190208862437#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_16##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F50005A0000010D00000BE800043A7D1B4FBFCB#1190208910437#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_23##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F50005D000000F200000BE800043A7D1BCA6E1F#1190208918468#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_19##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F5000530000050200000BE800043A7D1C2428C4#1190208924359#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_14##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F5000670000010800000BE800043A7D1C4174C7#1190208926265#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_13##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F50006E000000FC00000BE800043A7D1C5B3935#1190208927968#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_39##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F5000560000013E00000BE800043A7D1CCBA9CB#1190208935328#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_5##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F50006F000001B000000BE800043A7D1E1AD259#1190208957296#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002####4093bd1066b511dc848002004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F5000590000010700000BE800043A7D1E63EE6C#1190208962093#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#4093bd1066b511dc848002004c4f4f50#SAPEngine_Application_Thread[impl:3]_6##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F500065000000E300000BE800043A7D1ED83B46#1190208969703#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#4093bd1066b511dc848002004c4f4f50#SAPEngine_Application_Thread[impl:3]_25##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F5000670000010A00000BE800043A7D1EF0DAC4#1190208971328#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#4093bd1066b511dc848002004c4f4f50#SAPEngine_Application_Thread[impl:3]_13##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F50005F000000EA00000BE800043A7D1FF3A223#1190208988281#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#4093bd1066b511dc848002004c4f4f50#SAPEngine_Application_Thread[impl:3]_11##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F50006F000001B200000BE800043A7D217D9D64#1190209014109#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990####62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F50006E000000FE00000BE800043A7D21CF6D5E#1190209019468#/System/Server#sap.com/irj#com.sap.portal.transport#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_39##0#0#Warning#1#com.sap.portal.transport#Plain###attributeToOptionValue: deprecated transport mode 'all' set in attribute, converting to new value 'data'.#
    #1.5#02004C4F4F5000770000002600000BE800043A7D22933859#1190209032296#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#Thread[PRT-Async 0,5,PRT-Async]##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F5000610000014100000BE800043A7D22972C3A#1190209032562#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_3##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F5000620000010200000BE800043A7D22A03409#1190209033140#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_26##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F50006D000000FA00000BE800043A7D24030209#1190209056406#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_37##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F500068000000F700000BE800043A7D2542795E#1190209077343#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_9##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F500069000000D300000BE800043A7D25560CD2#1190209078625#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_29##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F500065000000E500000BE800043A7D259497E1#1190209082718#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_25##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F500065000000E700000BE800043A7D25AE33C8#1190209084406#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#8c16a40066b511dc816302004c4f4f50#SAPEngine_Application_Thread[impl:3]_25##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F500068000000FA00000BE800043A7D25F4DC7D#1190209089031#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_9##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F50005C0000018900000BE800043A7D26CCFBDB#1190209103187#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_21##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F5000610000014400000BE800043A7D27782A46#1190209114406#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_3##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F500060000000EB00000BE800043A7D281E236F#1190209125296#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_8##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F50005B000000E000000BE800043A7D286921AD#1190209130203#/System/Server#sap.com/irj#com.sap.portal.transport#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_27##0#0#Warning#1#com.sap.portal.transport#Plain###attributeToOptionValue: deprecated transport mode 'all' set in attribute, converting to new value 'data'.#
    #1.5#02004C4F4F5000770000002800000BE800043A7D2B3A9FE6#1190209177484#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#Thread[PRT-Async 0,5,PRT-Async]##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F5000720000013200000BE800043A7D2B3E90B6#1190209177750#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_2##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F500068000000FC00000BE800043A7D2B485A1B#1190209178390#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_9##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F5000530000050400000BE800043A7D2BB72C5E#1190209185656#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_14##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F5000580000010B00000BE800043A7D2BF23F09#1190209189531#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_1##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F500065000000E900000BE800043A7D2C13D341#1190209191718#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_25##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F500057000000B000000BE800043A7D2CC288CF#1190209203171#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_16##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F500063000000EE00000BE800043A7D2CD6EAC9#1190209204515#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_38##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F50006E000000FF00000BE800043A7D2D18DDC7#1190209208828#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_39##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F50005E000000C300000BE800043A7D2EEEEB90#1190209239640#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_15##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F50006C0000014100000BE800043A7D2FBF6A71#1190209253296#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#f0c617a066b511dcb83802004c4f4f50#SAPEngine_Application_Thread[impl:3]_35##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F50006C0000014300000BE800043A7D2FF14676#1190209256578#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#abb#10002##mmsr17_NW2_28653750#abb#f0c617a066b511dcb83802004c4f4f50#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.httpconnectivity.urliviews on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.httpconnectivity.urliviews#library:com.sap.portal.common#
    #1.5#02004C4F4F50008D0000000000000BE800043A7D30545B8A#1190209263062#/System/Server##com.sap.engine.services.deploy####mmsr17_NW2_28653750#Guest#27b45fa166ad11dcafed02004c4f4f50#SAPEngine_System_Thread[impl:5]_70##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/cafeugpuirt~comp finished successfully on server 28653750#
    #1.5#02004C4F4F50008D0000000100000BE800043A7D30545BF9#1190209263062#/System/Server##com.sap.engine.services.deploy####mmsr17_NW2_28653750#Guest#27b45fa166ad11dcafed02004c4f4f50#SAPEngine_System_Thread[impl:5]_70##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/cafeugpuirt~comp finished on current cluster node for 47 ms.#
    #1.5#02004C4F4F5000730000000600000BE800043A7D3083A0B8#1190209266156#/System/Server##com.sap.engine.services.deploy####mmsr17_NW2_28653750#Guest#a7c92c31669d11dcb80f02004c4f4f50#SAPEngine_System_Thread[impl:5]_86##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application com.test/csreq_cr finished successfully on server 28653750#
    #1.5#02004C4F4F5000730000000700000BE800043A7D3083A125#1190209266156#/System/Server##com.sap.engine.services.deploy####mmsr17_NW2_28653750#Guest#a7c92c31669d11dcb80f02004c4f4f50#SAPEngine_System_Thread[impl:5]_86##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application com.test/csreq_cr finished on current cluster node for 94 ms.#
    #1.5#02004C4F4F50005F000000EC00000BE800043A7D3181F8EB#1190209282828#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#01a16e3066b611dc954c02004c4f4f50#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F50006B0000010700000BE800043A7D31B78BF5#1190209286343#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#01a16e3066b611dc954c02004c4f4f50#SAPEngine_Application_Thread[impl:3]_31##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F5000610000014600000BE800043A7D31EB1162#1190209289718#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#01a16e3066b611dc954c02004c4f4f50#SAPEngine_Application_Thread[impl:3]_3##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F50005A0000010F00000BE800043A7D322FF621#1190209294234#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#01a16e3066b611dc954c02004c4f4f50#SAPEngine_Application_Thread[impl:3]_23##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
    #1.5#02004C4F4F50005A0000011100000BE800043A7D327E4387#1190209299359#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#0c35dd9066b611dcacd902004c4f4f50#SAPEngine_Application_Thread[impl:3]_23##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
    #1.5#02004C4F4F50002C0000000700000BE800043A7D391C52A4#1190209410390#/System/Server##com.sap.engine.services.deploy####mmsr17_NW2_28653750#Guest#329208a1668f11dca53302004c4f4f50#SAPEngine_System_Thread[impl:5]_22##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application com.test/csblock finished successfully on server 28653750#
    #1.5#02004C4F4F50002C0000000800000BE800043A7D391C5310#1190209410390#/System/Server##com.sap.engine.services.deploy####mmsr17_NW2_28653750#Guest#329208a1668f11dca53302004c4f4f50#SAPEngine_System_Thread[impl:5]_22##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application com.test/csblock finished on current cluster node for 125 ms.#
    #1.5#02004C4F4F50008E0000000100000BE800043A7D3AA688E4#1190209436234#/System/Server##com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Plain###A runtime exception ocurred: null#
    #1.5#02004C4F4F50008F0000000100000BE800043A7D3AA7F5D5#1190209436328#/System/Server##com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Plain###A runtime exception ocurred: null#
    #1.5#02004C4F4F50008F0000000300000BE800043A7D3AA841A2#1190209436343#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Plain###Process stopped#
    #1.5#02004C4F4F50008F0000000500000BE800043A7D3AA842A3#1190209436343#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
    #1.5#02004C4F4F50008F0000000700000BE800043A7D3AA8440E#1190209436343#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
    #1.5#02004C4F4F50008E0000000300000BE800043A7D3AAD14A6#1190209436656#/System/Server##com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Plain###A runtime exception ocurred: null#
    #1.5#02004C4F4F50008E0000000500000BE800043A7D3AAD16F9#1190209436656#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Plain###Process stopped#
    #1.5#02004C4F4F50008E0000000700000BE800043A7D3AAD17A3#1190209436656#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
    #1.5#02004C4F4F50008E0000000900000BE800043A7D3AAD189B#1190209436656#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
    #1.5#02004C4F4F50008F0000000900000BE800043A7D3AB1E837#1190209436968#/System/Server##com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Plain###A runtime exception ocurred: null#
    #1.5#02004C4F4F50008F0000000B00000BE800043A7D3AB1EA83#1190209436968#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Plain###Process stopped#
    #1.5#02004C4F4F50008F0000000D00000BE800043A7D3AB1EB2E#1190209436968#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
    #1.5#02004C4F4F50008F0000000F00000BE800043A7D3AB1EC1A#1190209436968#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
    #1.5#02004C4F4F50008E0000000B00000BE800043A7D3AB6BCCC#1190209437296#/System/Server##com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Plain###A runtime exception ocurred: null#
    #1.5#02004C4F4F50008E0000000D00000BE800043A7D3AB6BF2B#1190209437296#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Plain###Process stopped#
    #1.5#02004C4F4F50008E0000000F00000BE800043A7D3AB6BFE8#1190209437296#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
    #1.5#02004C4F4F50008E0000001100000BE800043A7D3AB6C0D3#1190209437296#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
    #1.5#02004C4F4F50008F0000001100000BE800043A7D3ABB91E2#1190209437609#/System/Server##com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Plain###A runtime exception ocurred: null#
    #1.5#02004C4F4F50008F0000001300000BE800043A7D3ABB94EC#1190209437609#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Plain###Process stopped#
    #1.5#02004C4F4F50008F0000001500000BE800043A7D3ABB959E#1190209437609#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
    #1.5#02004C4F4F50008F0000001700000BE800043A7D3ABB9695#1190209437609#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
    #1.5#02004C4F4F50008F0000001900000BE800043A7D3AC067E1#1190209437921#/System/Server##com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Plain###A runtime exception ocurred: null#
    #1.5#02004C4F4F50008F0000001B00000BE800043A7D3AC06A2F#1190209437921#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Plain###Process stopped#
    #1.5#02004C4F4F50008F0000001D00000BE800043A7D3AC06ADA#1190209437921#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
    #1.5#02004C4F4F50008F0000001F00000BE800043A7D3AC06C14#1190209437921#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
    #1.5#02004C4F4F50008E0000001300000BE800043A7D3AC55E9F#1190209438250#/System/Server##com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Plain###A runtime exception ocurred: null#
    #1.5#02004C4F4F50008E0000001500000BE800043A7D3AC560F5#1190209438250#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Plain###Process stopped#
    #1.5#02004C4F4F50008E0000001700000BE800043A7D3AC561A8#1190209438250#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
    #1.5#02004C4F4F50008E0000001900000BE800043A7D3AC5629E#1190209438250#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
    #1.5#02004C4F4F50008F0000002100000BE800043A7D3ACA31F2#1190209438562#/System/Server##com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Plain###A runtime exception ocurred: null#
    #1.5#02004C4F4F50008F0000002300000BE800043A7D3ACA344F#1190209438562#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Plain###Process stopped#
    #1.5#02004C4F4F50008F0000002500000BE800043A7D3ACA3502#1190209438562#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
    #1.5#02004C4F4F50008F0000002700000BE800043A7D3ACA35F2#1190209438562#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
    Thanks,
    Vivek.

    Hi,
    default trace can be very misleading. The root cause might be in the default trace it might not be. One common problem is that your license is expired. I know just a wild guess, but may be it is a hit.
    Regards,
    Jochen

  • The server process could not be started because the configured identity is incorrect

    Good morning
    I have the same problem as here, every moning i must writing pasword.
    https://social.msdn.microsoft.com/Forums/en-US/f95ee480-dda1-42fd-96af-596531e7ac2e/the-server-process-could-not-be-started-because-the-configured-identity-is-incorrect?forum=windowstransactionsprogramming
    But my configuration is the same as was answer in this post, may be you can help me with another idea?. Thanks.
    Windows 2008 R2 64Bit

    Both machines start with an automatic login so technically there is an interactive user.
    Nevertheless, it is an interesting point. i will try to configure the applications to run under a particular user and see if that changes anything.
    Thank you
    Peter

  • The Oracle BI server is not running. The repositiry had to be closed

    Hi guys,
    I have a OBI Standard Edition 10.1.3.4.1.
    I have modify the rpd and if I try to "Check In Changes", the error appears: "The Oracle BI server is not running. The repositiry had to be closed".
    In the nQServer.log this error appears:
    [nQSError: 12002] Socket communication error at call=recv: (Number=10055) An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
    Why?
    The problem persist if I restart the services.
    The problem only occurs if I make a change in the Business Model Layer. The changes in the Physical Layer do not generate errors.
    Thank you,
    Sara

    Hi Sara,
    Can you please let us know, if there are any other messages in the NQServer.out.log ? I just googled around with this code to hit at the following link : http://www.bookmark-master.com/socket-error-10055.html
    Socket error (#10055): No buffer space available.
    Analyse & Solutions:
    An operation on a socket or pipe was not performed because the system lacked sufficient buffer space or because a queue was full. This error indicates a shortage of resources on your system. It can occur if you're trying to run too many applications (of any kind) simultaneously on your machine. If this tends to occur after running certain applications for a while, it might be a symptom of an application that doesn't return system resources (like memory) properly. It may also indicate you are not closing the applications properly. If it persists, exit Windows or reboot your machine to remedy the problem.
    From the above information, I understand that this is a system resource issue. Can you please recheck if your system has got enough resources?
    Hope this helps.
    Thank you,
    Dhar

  • I was going to upgrade from 10.6.8 to mavericks 10.9.2, but the installer program notified me stating my appleworks 6 app will not run on the new set up. is there a procedure to keep or switch my documents in order to obtain the mavericks upgrade?

    i was going to upgrade from 10.6.8 to mavericks 10.9.2, but the installer program notified me stating my appleworks 6 app will not run on the new set up. is there a procedure to keep or switch my documents in order to obtain the mavericks upgrade?

    I can't say personally since I never used AW, but see if these articles help:
    http://www.macworld.com/article/1166370/open_old_docs.html
    http://www.cultofmac.com/248546/convert-system-os-9-appleworks-6-files-to-os-x-p ages-files-os-x-tips/
    I suggest that you clone your current drive with 10.6.8 to an external drive. If you have any issues after upgrading to Mavericks, you can boot back into 10.6.8.
    Both of these applications can be used to create a clone. If you need help creating your clone, let us know.
    SuperDuper! http://www.shirt-pocket.com/
    CCC http://www.bombich.com/download.html

  • The report server service is not running on Reporting Service Point server

    Hi,
    I have encountered a problem, my reporting service point has stopped working. (SCCM 2012 R2)
    In srsrp.log:
    Check state SMS_SRS_REPORTING_POINT
    12/15/2014 5:48:54 AM 3152 (0x0C50)
    Check server health. SMS_SRS_REPORTING_POINT
    12/15/2014 5:48:54 AM 3152 (0x0C50)
    Successfully created srsserver SMS_SRS_REPORTING_POINT
    12/15/2014 5:48:54 AM 3152 (0x0C50)
    Reporting Services URL from Registry [https://s-hub-sql1.domain.local/ReportServer/ReportService2005.asmx]
    SMS_SRS_REPORTING_POINT 12/15/2014 5:48:54 AM
    3152 (0x0C50)
    The request failed with HTTP status 404: Not Found.
    SMS_SRS_REPORTING_POINT 12/15/2014 5:48:54 AM
    3152 (0x0C50)
    (!) SRS not detected as running SMS_SRS_REPORTING_POINT
    12/15/2014 5:48:54 AM 3152 (0x0C50)
    Failures reported during periodic health check by the SRS Server S-HUB-SQL1.domain.local.
    SMS_SRS_REPORTING_POINT 12/15/2014 5:48:54 AM
    3152 (0x0C50)
    Registry change SMS_SRS_REPORTING_POINT
    12/15/2014 5:48:54 AM 3152 (0x0C50)
    Waiting for changes for 1 minutes SMS_SRS_REPORTING_POINT
    12/15/2014 5:48:54 AM 3152 (0x0C50)
    Timed Out... SMS_SRS_REPORTING_POINT
    12/15/2014 5:49:54 AM 3152 (0x0C50)
    Set configuration SMS_SRS_REPORTING_POINT
    12/15/2014 5:49:54 AM 3152 (0x0C50)
    In windows event log:
    On 12/15/2014 6:39:28 PM, component SMS_SRS_REPORTING_POINT on computer S-HUB-SQL1 reported:  The report server service is not running on Reporting Service Point server "S-HUB-SQL1"; start the service to enable reporting.
    In configuration manager service manager, the service sms_srs_reporting_point is running.
    In Reporting services configuration manager, the service is running.
    If I restart the reporting service, it doesn't helps.
    What is not properly?

    I've already found the reason why all stopped working - someone deleted the report manager URL HTTPS bindings (in Report services configuration manager). Added it back, than reporting started to work. Awww!

  • I lost all my unpinned 30 tabs and could not restore it, when Adobe update opened a link by firefox, which was not running in the background.

    I lost all my unpinned 30 tabs and could not restore it, when Adobe update opened a link by firefox, which was not running in the background.
    I guess what I have experienced might be a special case of 'Restore previous sessions'. The actual situation was that after I rebooted my laptop, Adobe update jumped out indicating an update being finished successfully. After I clicked on the 'close' button of the Adobe window, it automatically started firefox and linked to its website. But I did not find the 'Restore previous sessions' page this time. Then I restarted firefox, this time there was a start page with 'Restore previous sessions'. However, sadly enough, it is only restored my pinned pages plus the Adobe website. Actually, I am using 'bookmark all tabs' from time to time to secure opened tabs, but this time I did not expect such an incident. I would suggest to improve the 'Restore previous sessions' with multiple time tags and appear in all cases including my reported case here, after updating firefox, crashes etc. I like firefox in most occasions, therefore believe and hope it becomes better and more robust. Thank you very much!

    Hi,
    Please see the following support request: http://forums.mozillazine.org/viewtopic.php?f=38&t=2628065
    I think the best option would be to leave feedback here to let the relevant development team know about the problem you have had: https://input.mozilla.org/en-GB/feedback
    Also you could try the [https://addons.mozilla.org/en-US/firefox/addon/session-manager/ Session Manager] add-on which gives more control over how sessions are restored.
    I hope that helps

  • Login wizard - CF9 server - "Coldfusion not is not running on the remote site" - YES it is!

    I use Dreamweaver to upkeep sites for several friends and clients. When I use the login wizzard on a server with CF8, it works fine. If I use it on a server with CF9, I can't get past the *Coldfusion not is not running on the remote site* error. Yes it is running.  I've tried connecting using FTP, RDS, directly over the network - you name it.  Same error.
    Any suggestions?
    Thanks
    Rick

    Hi Rick
    If you are trying to RDS log in to a remote server the host may have disabled this service... Most do, and should. Allowing remote RDS is a potential security risk.  Check with your host to see if this is the case.  If it is, it is always better to duplicate your host environment locally, that is be running CF9, and the database, be that MySQL, SQL Server, Access, or whatever locally and do all you development and testing there, then just upload the files when ready.
    Hope this helps.
    Lawrence Cramer - *Adobe Community Professional*
    http://www.Cartweaver.com
    Shopping Cart for Adobe Dreamweaver
    available in PHP, ColdFusion, and ASP
    Stay updated - http://blog.cartweaver.com

  • Hierarchies Job Failing  The job process could not communicate with the dat

    Hi Experts,
    We have a group of hierarchies that run as a separate job on the DS schedules. The problem is this when we schedule the job to run during the production loads it fails but when we run immediately after it fails it runs completely fine. So it basically means that if i run it manually it runs but when its scheduled to run with the production job it fails. Now the interesting thing is If i schedule the job to run anytime after or before the production jobs are done. It works fine.
    The error i get is
    The job process could not communicate with the data flow <XXXXXX> process. For details, see previously logged
                                                               error <50406>.
    Now this XXXXX DF has only Horizontal Flatenning and it does not run as separate process because if i have it has separate process it fails with an EOF . So i removed the run as separate process and changes the DF to use in memory .
    Any Suggestion on this problem...

    Thanks Mike.. I was hoping its a memory issue but the thing i don't understand is when the job is scheduled to run with the production job it fails. when i manually run the job during the production job it runs, this kinda baffles me.
    DS 3.2 (Verison 12.2.0.0)
    OS: GNU/LINUX
    DF Cache Setting :- In Memory
    processor       : 0
    vendor_id       : GenuineIntel
    cpu family      : 6
    model           : 26
    model name      : Intel(R) Xeon(R) CPU           X5670  @ 2.93GHz
    stepping        : 4
    cpu MHz         : 2933.437
    cache size      : 12288 KB
    fpu             : yes
    fpu_exception   : yes
    cpuid level     : 11
    wp              : yes
    flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss syscall nx rdtscp lm constant_tsc ida nonstop_tsc arat pni ssse3 cx16 sse4_1 sse4_2 popcnt lahf_lm
    bogomips        : 5866.87
    clflush size    : 64
    cache_alignment : 64
    address sizes   : 40 bits physical, 48 bits virtual
    power management: [8]
    processor       : 1
    vendor_id       : GenuineIntel
    cpu family      : 6
    model           : 26
    model name      : Intel(R) Xeon(R) CPU           X5670  @ 2.93GHz
    stepping        : 4
    cpu MHz         : 2933.437
    cache size      : 12288 KB
    fpu             : yes
    fpu_exception   : yes
    cpuid level     : 11
    wp              : yes
    flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss syscall nx rdtscp lm constant_tsc ida nonstop_tsc arat pni ssse3 cx16 sse4_1 sse4_2 popcnt lahf_lm
    bogomips        : 5866.87
    clflush size    : 64
    cache_alignment : 64
    address sizes   : 40 bits physical, 48 bits virtual
    power management: [8]
    Thanks for your help

  • OID is up & running but "ldap"  process are not running

    Hi all,
    Oracle Internet Directory is up & running but LDAP processes ( Not Running ---- Process oidmon
    Not Running ---- Process oidldapd
    Not Running ---- Process oidrepld
    Not Running ---- Process odisrv) are not running.
    I am trying to configure SSO for reverse proxy server and ran the command ssocfg.sh https proxyServerName proxyServerPort
    and when i am trying to go for next step that is ldapmodify -D cn=orcladmin -w welcome1 -v -f setdasurl.ldif
    it is showing up cannot connect to LDAP server. and also when i am trying to acess SSO admin Server the redirection url is showing up with 404 page not found error.
    pls help me
    Thanks

    Do 'oidctl status' and check if the 'oidldapd' is up and running. If not, start 'oidmon' by executing the command 'oidmon start'.
    To start 'oidldapd', use 'oidctl' command.
    Eg: oidctl connect=<sid_name> server=oidldapd instance=<instance_num> start
    Sometimes, when you start 'oidmon', the 'oidldapd' process is also started. So, its a good idea to do 'oidctl status' after 'oidmon start'

  • Apache Web Server Listener is not running

    Hi,
    when starting E_BUSINESS issuing this
    adstrtal.sh apps/apps
    , I have this error message :
    Apache Web Server Listener is not running.
    Starting Apache Web Server Listener (dedicated HTTP) ...
    Apache Web Server Listener (PLSQL) is not running.
    Starting Apache Web Server Listener (dedicated PLSQL) ...
    What might be the problem ? How can I launch Apache Web Server Listener to see why it can not start and where to see it's log file ?
    Many thanks

    hsawwan,
    I stopped all services, and killed process that were using port 8103. Then restarted all. In jserv.log we have
    [09/11/2007 15:36:27:798 CET] Host os02ebsx.ourdomain.net not found and not allowed to connect
    [09/11/2007 15:37:29:146 CET] Repository /Data/oracle/d03/prdacomn/java/apps.zip doesn't exist!
    [09/11/2007 15:37:29:178 CET] oracle.apps.icx.common.InitSystemProperties: init
    [09/11/2007 15:37:29:233 CET] oracle.apps.fnd.tcf.SocketServer: init
    [09/11/2007 15:37:29:247 CET] weboamLocal/oracle.apps.fnd.oam.servlet.ui.OAMServlet: init
    [09/11/2007 15:37:30:005 CET] weboamLocal/oracle.apps.fnd.oam.servlet.ui.OAMServlet: Sucessfully initialize oaosu.OAMServlet
    [09/11/2007 15:37:30:156 CET] oracle.apps.mwa.wap.engine.WapServlet: init
    [09/11/2007 15:37:30:156 CET] oracle.apps.mwa = /Data/oracle/d03/prdaappl/mwa/11.5.0
    [09/11/2007 15:37:33:271 CET] Fatal error in parsing device registration file. See system log file for de-tails.
    but in Context.xml file we do not have os02ebsx.ourdomain.net. Where does java server pick up this host ?
    Thanks and regards.

  • This process will not run on a client version of lookout?

    I get the following error message when I try to upload my process for web
    access: "This process will not run on a client version of lookout?"
    Why am I getting this?
    Regards,
    Tommy Scharmann

    Hello Tommy,
    You're probably trying to upload a process which has a Driver object in it
    (like Modbus, AB, etc.) As you are aware, Lookout Clients (and Web CLients)
    do not have Driver Objects and that's the reason you're getting the message.
    You will normally upload your Client process -- a process which doesn't have
    driver objects but talks to a Server Process in turn.
    Regards,
    Khalid
    "Thomas Scharmann" wrote:
    I get the following error message when I try to upload my process for web>access:
    "This process will not run on a client version of lookout?"
    Why am I getting this?
    Regards,
    Tommy Scharmann

  • Applet not running in the broweser.

    Hello everyone I have a problem that is bugging me.
    in my pc at home i have operating system window xp i have oracle9i installed and also java and j2ee and version of internet explorer is 6.0
    .there is no proble running html pages but the problem is the applet are not running in the broweser even the java demo from sun is not running
    .when i try to run the applet a dialog box appears and shows this
    " jvm not find Download now" i do not have internet connection.
    and one more thing i want to down load or save file in webserver
    i donot know whether my pc is having default webserver but when i type this "http://localhost" a page of oracle is display listing jserver ,appache server and so many thing.
    do i have a webserver that can be used by me for java program(adv java) or i have to get one .as i told you there is java1.3 and j2ee1_2_3
    something like this i donot remember is there no default webserver along with them .how can i use them for my java programe .
    let me remind you the applet not getting downloaded in the browser is a bigger problem for me.
    i appreciate your concern please help me out
    have a nice day bye.

    1} The applet is not getting loaded in my internet
    browser.Error messages? Are you sure your setup is correct? Search. "Applet not working" usually has only a small range of reasons, all well-covered here.
    2}why the oracle page is displayed when i type
    "http://localhost".
    Maybe because you have some Oracle webserver?
    3} Do i have any default webbrowser in my system.Yes. The one that opens when you double-click on an HTML page.
    >
    thanks.

  • ITunes in Processes but not running

    My iTunes is running the the processes, but is not running in the applications. I have removed and uninstalled iTunes and Quicktime and reinstalled the most recent version. Quicktime opens and there are no error messages in the Quicktime Prefs. Any ideas? Thanks

    If you see the exe but itunes never fully opens, polydorus' post here might help -
    http://discussions.apple.com/thread.jspa?threadID=1875404&tstart=0

  • Unable to Deploy Applications:  "process is not defined in the descriptor"

    All
    I'm having a fairly serious issue here trying to take an LCA from one environment and get it in another environment.  Both the source and destination environments are LCES 2.5 (LCES 2 with SP2).  I have roughly 6 applications and there are some far dependencies (one application referencing an asset of another application) therein.  I've taken an LCA of all these applicaitons from the source environment and the LCA imports just fine in the destination environment but I am unable to deploy any of the applications that have far dependencies.  The error I consistently get when I attempt to deploy any application that has a far dependency is:
    [Some process name].process is not defined in the descriptor.
    I have tried all of the following:
    1) Taking 1 LCA of all applications together
    2) Taking multiple LCAs where each LCA contains only one application
    3) Taking multiple LCAs where each LCA includes an application as well as all far dependencies for that application
    Regardless of what I try, they won't deploy.  I can import the LCA and I can get the applications in Workbench and play around with them but they simply won't deploy.  I've also attempted to manually fix all depencies within the processes themselves but that doesn't work either.
    Any help would be appreciated.

    Just wanted to follow up on the solution to my issue.
    It appears the issue centers around circular far dependencies.  In general, it seems LiveCycle chokes when two applications each reference one another.  Note that I'm not talkinng about true circular referencing here wherein one process within application A references a process in application B while that same process refers back to the original process in application A.  In fact, although I haven't tested recently, I believe LiveCycle may actually catch this kind of issue.  The circular far dependencies I'm talking about is simply where a process in application A (call it a1) references a process in application B (call it b1) while a process in application B (call it b2) references a process in applicatoin A (call it a2).  Apparently this kind of circular referencing causes the deployment of said applications to choke.
    The fix was tedious as I had to manually delete all of the far dependencies from both application, deploy those two applications to get them into the runtime, and then implement those dependencies again.
    Going forward it seems like a best practice to only ever have 1 direction for dependencies for any application.

Maybe you are looking for

  • Wifi not working in iOS 6

    Have tried all the suggestions for fix, still no wifi on my iPhone 4

  • External monitor not being detected

    I recently sent my macBook away for repairs, it was only software problems, the engineers it seemed simply uninstalled and reinstalled the software. Since I have had it back, I cannot get it to detect my Dell 2209WA. It was fine before. I am using a

  • Send As permissions are being deleted, possible Protected Group problem

    I have a SBS 2008 server with a number of shared mailboxes that I need to assign Send As permissions to. However, I am getting bouncebacks when trying to use the Send As and have noticed that the settings I am applying are deleted after a short time.

  • Nulware incompatibility

    After receiving a 4Gb Nano for Xmas and installing iTunes and Quicktime, successfully, and being able to synchronise the Nano, etc, I get the following dialogue box in XP, on boot-up of the PC; '16-Bit MS-DOS Subsystem C:\WINDOWS\System32\Nulware The

  • 9.0 now can't complete purchase--error (no#) re time & cookies

    Updated to iTunes 9.0, tried to purchase couple of apps for ipod touch. Get error cannot complete, that I should make sure date on computer is accurate (it IS) and cookies enabled for iTunes, and refers me for more info to a webpage about accounts on