JAVA_HOME does not point to the JDK

Hello !
I am running one project in Eclipse , but, i am getting some errors while running the project.
Error is as follows :
com.sun.tools.javac.Main is not on the classpath.
Perhaps JAVA_HOME does not point to the JDK.
It is currently set to "C:\Zicom\java\jre1.5.0_04"
If anybody is knowing the solution please tell me, i need your help badly.
Thank you very much.

Aw c'mon, that error message is self-explanatory.
What's your JDK home directory? Not something ending in jre1.5.0_04, I'll bet.
My Computer -> right-click -> Properties -> Advanced -> Environment Variables -> JAVA_HOME -> change it to the home directory of your jdk -> run Eclipse -> post back here.
db
edit Late, as usual. Anyhow, remove the \bin at the end of your JAVA_HOME and try again.
Edited by: Darryl.Burke

Similar Messages

JAVA_HOME does not point to the JDK Error.

Hello Friends,
                     I unable build my local DC due problem with JAVA_HOME Parameter.
I am using j2sdk1.4.2_08. Is this a problem. (JDK Version).
I have checked the file C:\usr\sap\J2E\JC00\work\dev_server0
I got the following error when try to build DC.
Ant build finished with ERRORS
Unable to find a javac compiler;
com.sun.tools.javac.Main is not on the classpath.
Perhaps JAVA_HOME does not point to the JDK
Error: Build stopped due to an error: Unable to find a javac compiler;
com.sun.tools.javac.Main is not on the classpath.
Perhaps JAVA_HOME does not point to the JDK
Build plugin finished at 2007-09-09 16:21:38 GMT+08:00 (SGT)
Total build plugin runtime: 5.453 seconds
Build finished with ERROR
Cheers.. Sam

Please find below is C:\usr\sap\J2E\JC00\work\dev_server0 content
trc file: "C:\usr\sap\J2E\JC00\work\dev_server0", trc level: 1, release: "640"
node name   : ID4467550
pid         : 5648
system name : J2E
system nr. : 00
started at : Tue Sep 04 10:03:42 2007
arguments   :
    arg[00] : C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    arg[01] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
    arg[02] : -DSAPINFO=J2E_00_server
    arg[03] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
[Thr 4672] Tue Sep 04 10:03:42 2007
[Thr 4672] *** ERROR => Invalid property value [box.number/J2EJC00senthil] [jstartxx.c   789]
[Thr 4672] *** ERROR => Invalid property value [en.host/PWDF3013] [jstartxx.c   789]
[Thr 4672] *** ERROR => Invalid property value [en.port/3201] [jstartxx.c   789]
[Thr 4672] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
JStartupReadInstanceProperties: read instance properties [C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties]
-> ms host    : senthil
-> ms port    : 3601
-> OS libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> Admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Used property files
-> files [00] : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
Instance properties
-> ms host    : senthil
-> ms port    : 3601
-> os libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Bootstrap nodes
-> [00] bootstrap            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID4467500 : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID4467550 : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID4467500            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [01] ID4467550            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
[Thr 4672] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 4672] JLaunchRequestQueueInit: create pipe listener thread
[Thr 2992] WaitSyncSemThread: Thread 2992 started as semaphore monitor thread.
[Thr 3280] JLaunchRequestFunc: Thread 3280 started as listener thread for np messages.
[Thr 4672] Tue Sep 04 10:03:43 2007
[Thr 4672] INFO: Invalid property value [JLaunchParameters/]
[Thr 4672] [Node: server0] java home is set by profile parameter
     Java Home: C:\j2sdk1.4.2_08
JStartupIReadSection: read node properties [ID4467550]
-> node name       : server0
-> node type       : server
-> java path       : C:\j2sdk1.4.2_08
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Dsun.io.useCanonCaches=false -verbose:gc -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=C:/usr/sap/J2E/SYS/global -Djava.awt.headless=true -XX:NewSize=85m -XX:MaxNewSize=85m -XX:MaxPermSize=192m -XX:PermSize=192m -XX:DisableExplicitGC -XX:UseParNewGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc
-> java vm version : 1.4.2_08-b03
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type    : server
-> java vm cpu     : x86
-> heap size       : 512M
-> init heap size : 512M
-> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster\server0
-> class path      : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> main class      : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters      :
-> debuggable      : yes
-> debug mode      : no
-> debug port      : 50021
-> shutdown timeout: 120000
[Thr 4672] JLaunchISetDebugMode: set debug mode [no]
[Thr 4932] JLaunchIStartFunc: Thread 4932 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack   : 262144 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: -Djava.security.policy=./java.policy
-> arg[ 3]: -Djava.security.egd=file:/dev/urandom
-> arg[ 4]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 5]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 6]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 7]: -Djco.jarm=1
-> arg[ 8]: -Dsun.io.useCanonCaches=false
-> arg[ 9]: -verbose:gc
-> arg[ 10]: -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar
-> arg[ 11]: -Dsys.global.dir=C:/usr/sap/J2E/SYS/global
-> arg[ 12]: -Djava.awt.headless=true
-> arg[ 13]: -XX:NewSize=85m
-> arg[ 14]: -XX:MaxNewSize=85m
-> arg[ 15]: -XX:MaxPermSize=192m
-> arg[ 16]: -XX:PermSize=192m
-> arg[ 17]: -XX:+DisableExplicitGC
-> arg[ 18]: -XX:+UseParNewGC
-> arg[ 19]: -XX:+PrintGCDetails
-> arg[ 20]: -XX:+PrintGCTimeStamps
-> arg[ 21]: -XX:SurvivorRatio=2
-> arg[ 22]: -XX:TargetSurvivorRatio=90
-> arg[ 23]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 24]: -verbose:gc
-> arg[ 25]: -Dsys.global.dir=C:\usr\sap\J2E\SYS\global
-> arg[ 26]: -Dapplication.home=C:\usr\sap\J2E\JC00\j2ee\os_libs
-> arg[ 27]: -Djava.class.path=C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 28]: -Djava.library.path=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI.ACE\;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;C:\usr\sap\J2E\SCS01\exe;C:\usr\sap\J2E\JC00\exe;C:\usr\sap\J2E\SYS\exe\run
-> arg[ 29]: -Dmemory.manager=512M
-> arg[ 30]: -Xmx512M
-> arg[ 31]: -Xms512M
-> arg[ 32]: -DLoadBalanceRestricted=no
-> arg[ 33]: -Djstartup.mode=JCONTROL
-> arg[ 34]: -Djstartup.ownProcessId=5648
-> arg[ 35]: -Djstartup.ownHardwareId=Z2123283434
-> arg[ 36]: -Djstartup.whoami=server
-> arg[ 37]: -Djstartup.debuggable=yes
-> arg[ 38]: -DSAPINFO=J2E_00_server
-> arg[ 39]: -DSAPSTARTUP=1
-> arg[ 40]: -DSAPSYSTEM=00
-> arg[ 41]: -DSAPSYSTEMNAME=J2E
-> arg[ 42]: -DSAPMYNAME=senthil_J2E_00
-> arg[ 43]: -DSAPDBHOST=
-> arg[ 44]: -Dj2ee.dbhost=senthil
[Thr 4932] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 5412] Tue Sep 04 10:03:50 2007
[Thr 5412] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 5412] JLaunchISetClusterId: set cluster id 4467550
[Thr 5412] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 5412] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 5184] Tue Sep 04 10:04:23 2007
[Thr 5184] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
[Thr 5184] *** ERROR => JHVM_RegisterNatives: registration for class com.sap.security.core.server.vsi.service.jni.VirusScanInterface failed. [jhvmxx.c     338]
[Thr 5412] Tue Sep 04 10:04:49 2007
[Thr 5412] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
[Thr 3120] Tue Sep 04 10:04:50 2007
[Thr 3120] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
[Thr 336] Tue Sep 04 10:09:06 2007
[Thr 336] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]
[Thr 2592] Tue Sep 04 12:34:36 2007
[Thr 2592] JLaunchIExitJava: exit hook is called (rc=-337)
[Thr 2592] JLaunchCloseProgram: good bye (exitcode=-337)
trc file: "C:\usr\sap\J2E\JC00\work\dev_server0", trc level: 1, release: "640"
node name   : ID4467550
pid         : 1432
system name : J2E
system nr. : 00
started at : Tue Sep 04 12:34:40 2007
arguments   :
    arg[00] : C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    arg[01] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
    arg[02] : -DSAPINFO=J2E_00_server
    arg[03] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
[Thr 5984] Tue Sep 04 12:34:40 2007
[Thr 5984] *** ERROR => Invalid property value [box.number/J2EJC00senthil] [jstartxx.c   789]
[Thr 5984] *** ERROR => Invalid property value [en.host/PWDF3013] [jstartxx.c   789]
[Thr 5984] *** ERROR => Invalid property value [en.port/3201] [jstartxx.c   789]
[Thr 5984] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
JStartupReadInstanceProperties: read instance properties [C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties]
-> ms host    : senthil
-> ms port    : 3601
-> OS libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> Admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Used property files
-> files [00] : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
Instance properties
-> ms host    : senthil
-> ms port    : 3601
-> os libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Bootstrap nodes
-> [00] bootstrap            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID4467500 : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID4467550 : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID4467500            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [01] ID4467550            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
[Thr 5984] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 5984] JLaunchRequestQueueInit: create pipe listener thread
[Thr 5096] JLaunchRequestFunc: Thread 5096 started as listener thread for np messages.
[Thr 1600] WaitSyncSemThread: Thread 1600 started as semaphore monitor thread.
[Thr 5984] Tue Sep 04 12:34:41 2007
[Thr 5984] INFO: Invalid property value [JLaunchParameters/]
[Thr 5984] [Node: server0] java home is set by profile parameter
     Java Home: C:\j2sdk1.4.2_08
JStartupIReadSection: read node properties [ID4467550]
-> node name       : server0
-> node type       : server
-> java path       : C:\j2sdk1.4.2_08
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Dsun.io.useCanonCaches=false -verbose:gc -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=C:/usr/sap/J2E/SYS/global -Djava.awt.headless=true -XX:NewSize=85m -XX:MaxNewSize=85m -XX:MaxPermSize=192m -XX:PermSize=192m -XX:DisableExplicitGC -XX:UseParNewGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc
-> java vm version : 1.4.2_08-b03
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type    : server
-> java vm cpu     : x86
-> heap size       : 512M
-> init heap size : 512M
-> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster\server0
-> class path      : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> main class      : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters      :
-> debuggable      : yes
-> debug mode      : no
-> debug port      : 50021
-> shutdown timeout: 120000
[Thr 5984] JLaunchISetDebugMode: set debug mode [no]
[Thr 4812] JLaunchIStartFunc: Thread 4812 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack   : 262144 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: -Djava.security.policy=./java.policy
-> arg[ 3]: -Djava.security.egd=file:/dev/urandom
-> arg[ 4]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 5]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 6]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 7]: -Djco.jarm=1
-> arg[ 8]: -Dsun.io.useCanonCaches=false
-> arg[ 9]: -verbose:gc
-> arg[ 10]: -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar
-> arg[ 11]: -Dsys.global.dir=C:/usr/sap/J2E/SYS/global
-> arg[ 12]: -Djava.awt.headless=true
-> arg[ 13]: -XX:NewSize=85m
-> arg[ 14]: -XX:MaxNewSize=85m
-> arg[ 15]: -XX:MaxPermSize=192m
-> arg[ 16]: -XX:PermSize=192m
-> arg[ 17]: -XX:+DisableExplicitGC
-> arg[ 18]: -XX:+UseParNewGC
-> arg[ 19]: -XX:+PrintGCDetails
-> arg[ 20]: -XX:+PrintGCTimeStamps
-> arg[ 21]: -XX:SurvivorRatio=2
-> arg[ 22]: -XX:TargetSurvivorRatio=90
-> arg[ 23]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 24]: -verbose:gc
-> arg[ 25]: -Dsys.global.dir=C:\usr\sap\J2E\SYS\global
-> arg[ 26]: -Dapplication.home=C:\usr\sap\J2E\JC00\j2ee\os_libs
-> arg[ 27]: -Djava.class.path=C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 28]: -Djava.library.path=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI.ACE\;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;C:\usr\sap\J2E\SCS01\exe;C:\usr\sap\J2E\JC00\exe;C:\usr\sap\J2E\SYS\exe\run
-> arg[ 29]: -Dmemory.manager=512M
-> arg[ 30]: -Xmx512M
-> arg[ 31]: -Xms512M
-> arg[ 32]: -DLoadBalanceRestricted=no
-> arg[ 33]: -Djstartup.mode=JCONTROL
-> arg[ 34]: -Djstartup.ownProcessId=1432
-> arg[ 35]: -Djstartup.ownHardwareId=Z2123283434
-> arg[ 36]: -Djstartup.whoami=server
-> arg[ 37]: -Djstartup.debuggable=yes
-> arg[ 38]: -DSAPINFO=J2E_00_server
-> arg[ 39]: -DSAPSTARTUP=1
-> arg[ 40]: -DSAPSYSTEM=00
-> arg[ 41]: -DSAPSYSTEMNAME=J2E
-> arg[ 42]: -DSAPMYNAME=senthil_J2E_00
-> arg[ 43]: -DSAPDBHOST=
-> arg[ 44]: -Dj2ee.dbhost=senthil
[Thr 4812] Tue Sep 04 12:34:42 2007
[Thr 4812] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 4216] Tue Sep 04 12:35:05 2007
[Thr 4216] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 4216] JLaunchISetClusterId: set cluster id 4467550
[Thr 4216] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 4216] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 5892] Tue Sep 04 12:35:49 2007
[Thr 5892] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
[Thr 5892] *** ERROR => JHVM_RegisterNatives: registration for class com.sap.security.core.server.vsi.service.jni.VirusScanInterface failed. [jhvmxx.c     338]
[Thr 4216] Tue Sep 04 12:36:14 2007
[Thr 4216] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
[Thr 516] Tue Sep 04 12:36:16 2007
[Thr 516] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
[Thr 332] Tue Sep 04 12:41:00 2007
[Thr 332] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]
[Thr 5096] Tue Sep 04 20:53:33 2007
[Thr 5096] JLaunchRequestFunc: receive command:17, argument:0 from pid:1152
[Thr 5096] JLaunchIShutdownInvoke: set shutdown interval (stop:1188910413/end:1188910533/TO:120)
[Thr 5096] JLaunchProcessCommand: Invoke VM Shutdown
[Thr 5096] JHVM_FrameworkShutdownDirect: invoke direct shutdown
[Thr 4196] JLaunchISetState: change state from [Running (3)] to [Waiting for stop (4)]
[Thr 4196] JLaunchISetState: change state from [Waiting for stop (4)] to [Stopping (5)]
[Thr 4196] Tue Sep 04 20:53:58 2007
[Thr 4196] JLaunchISetState: change state from [Stopping (5)] to [Stopped (6)]
[Thr 4988] Tue Sep 04 20:53:59 2007
[Thr 4988] JLaunchIExitJava: exit hook is called (rc=0)
[Thr 4988] JLaunchCloseProgram: good bye (exitcode=0)
trc file: "C:\usr\sap\J2E\JC00\work\dev_server0", trc level: 1, release: "640"
node name   : ID4467550
pid         : 272
system name : J2E
system nr. : 00
started at : Tue Sep 04 20:54:04 2007
arguments   :
    arg[00] : C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    arg[01] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
    arg[02] : -DSAPINFO=J2E_00_server
    arg[03] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
[Thr 4792] Tue Sep 04 20:54:04 2007
[Thr 4792] *** ERROR => Invalid property value [box.number/J2EJC00senthil] [jstartxx.c   789]
[Thr 4792] *** ERROR => Invalid property value [en.host/PWDF3013] [jstartxx.c   789]
[Thr 4792] *** ERROR => Invalid property value [en.port/3201] [jstartxx.c   789]
[Thr 4792] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
JStartupReadInstanceProperties: read instance properties [C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties]
-> ms host    : senthil
-> ms port    : 3601
-> OS libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> Admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Used property files
-> files [00] : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
Instance properties
-> ms host    : senthil
-> ms port    : 3601
-> os libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Bootstrap nodes
-> [00] bootstrap            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID4467500 : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID4467550 : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID4467500            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [01] ID4467550            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
[Thr 4792] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 4792] JLaunchRequestQueueInit: create pipe listener thread
[Thr 1072] JLaunchRequestFunc: Thread 1072 started as listener thread for np messages.
[Thr 3240] WaitSyncSemThread: Thread 3240 started as semaphore monitor thread.
[Thr 4792] Tue Sep 04 20:54:05 2007
[Thr 4792] INFO: Invalid property value [JLaunchParameters/]
[Thr 4792] JStartupIReadSection: debug mode is specified by program arguments
[Thr 4792] [Node: server0] java home is set by profile parameter
     Java Home: C:\j2sdk1.4.2_08
JStartupIReadSection: read node properties [ID4467550]
-> node name       : server0
-> node type       : server
-> java path       : C:\j2sdk1.4.2_08
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Dsun.io.useCanonCaches=false -verbose:gc -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=C:/usr/sap/J2E/SYS/global -Djava.awt.headless=true -XX:NewSize=85m -XX:MaxNewSize=85m -XX:MaxPermSize=192m -XX:PermSize=192m -XX:DisableExplicitGC -XX:UseParNewGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc
-> java vm version : 1.4.2_08-b03
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type    : server
-> java vm cpu     : x86
-> heap size       : 512M
-> init heap size : 512M
-> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster\server0
-> class path      : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> main class      : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters      :
-> debuggable      : yes
-> debug mode      : yes
-> debug port      : 50021
-> shutdown timeout: 120000
[Thr 4792] JLaunchISetDebugMode: set debug mode [yes]
[Thr 2100] JLaunchIStartFunc: Thread 2100 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack   : 262144 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: -Djava.security.policy=./java.policy
-> arg[ 3]: -Djava.security.egd=file:/dev/urandom
-> arg[ 4]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 5]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 6]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 7]: -Djco.jarm=1
-> arg[ 8]: -Dsun.io.useCanonCaches=false
-> arg[ 9]: -verbose:gc
-> arg[ 10]: -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar
-> arg[ 11]: -Dsys.global.dir=C:/usr/sap/J2E/SYS/global
-> arg[ 12]: -Djava.awt.headless=true
-> arg[ 13]: -XX:NewSize=85m
-> arg[ 14]: -XX:MaxNewSize=85m
-> arg[ 15]: -XX:MaxPermSize=192m
-> arg[ 16]: -XX:PermSize=192m
-> arg[ 17]: -XX:+DisableExplicitGC
-> arg[ 18]: -XX:+UseParNewGC
-> arg[ 19]: -XX:+PrintGCDetails
-> arg[ 20]: -XX:+PrintGCTimeStamps
-> arg[ 21]: -XX:SurvivorRatio=2
-> arg[ 22]: -XX:TargetSurvivorRatio=90
-> arg[ 23]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 24]: -verbose:gc
-> arg[ 25]: -Dsys.global.dir=C:\usr\sap\J2E\SYS\global
-> arg[ 26]: -Dapplication.home=C:\usr\sap\J2E\JC00\j2ee\os_libs
-> arg[ 27]: -Djava.class.path=C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 28]: -Djava.library.path=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI.ACE\;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;C:\usr\sap\J2E\SCS01\exe;C:\usr\sap\J2E\JC00\exe;C:\usr\sap\J2E\SYS\exe\run
-> arg[ 29]: -Xdebug
-> arg[ 30]: -Xnoagent
-> arg[ 31]: -Djava.compiler=NONE
-> arg[ 32]: -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=50021
-> arg[ 33]: -Dmemory.manager=512M
-> arg[ 34]: -Xmx512M
-> arg[ 35]: -Xms512M
-> arg[ 36]: -DLoadBalanceRestricted=no
-> arg[ 37]: -Djstartup.mode=JCONTROL
-> arg[ 38]: -Djstartup.ownProcessId=272
-> arg[ 39]: -Djstartup.ownHardwareId=Z2123283434
-> arg[ 40]: -Djstartup.whoami=server
-> arg[ 41]: -Djstartup.debuggable=yes
-> arg[ 42]: -DSAPINFO=J2E_00_server
-> arg[ 43]: -DSAPSTARTUP=1
-> arg[ 44]: -DSAPSYSTEM=00
-> arg[ 45]: -DSAPSYSTEMNAME=J2E
-> arg[ 46]: -DSAPMYNAME=senthil_J2E_00
-> arg[ 47]: -DSAPDBHOST=
-> arg[ 48]: -Dj2ee.dbhost=senthil
[Thr 2100] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 2588] Tue Sep 04 20:54:11 2007
[Thr 2588] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 2588] JLaunchISetClusterId: set cluster id 4467550
[Thr 2588] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 2588] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 3600] Tue Sep 04 20:54:52 2007
[Thr 3600] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
[Thr 3600] *** ERROR => JHVM_RegisterNatives: registration for class com.sap.security.core.server.vsi.service.jni.VirusScanInterface failed. [jhvmxx.c     338]
[Thr 2588] Tue Sep 04 20:55:21 2007
[Thr 2588] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
[Thr 4848] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
[Thr 5320] Tue Sep 04 21:01:07 2007
[Thr 5320] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]
trc file: "C:\usr\sap\J2E\JC00\work\dev_server0", trc level: 1, release: "640"
node name   : ID4467550
pid         : 5276
system name : J2E
system nr. : 00
started at : Tue Sep 04 22:04:45 2007
arguments   :
    arg[00] : C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    arg[01] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
    arg[02] : -DSAPINFO=J2E_00_server
    arg[03] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
[Thr 1532] Tue Sep 04 22:04:45 2007
[Thr 1532] *** ERROR => Invalid property value [box.number/J2EJC00senthil] [jstartxx.c   789]
[Thr 1532] *** ERROR => Invalid property value [en.host/PWDF3013] [jstartxx.c   789]
[Thr 1532] *** ERROR => Invalid property value [en.port/3201] [jstartxx.c   789]
[Thr 1532] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
JStartupReadInstanceProperties: read instance properties [C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties]
-> ms host    : senthil
-> ms port    : 3601
-> OS libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> Admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Used property files
-> files [00] : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
Instance properties
-> ms host    : senthil
-> ms port    : 3601
-> os libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Bootstrap nodes
-> [00] bootstrap            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID4467500 : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID4467550 : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID4467500            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [01] ID4467550            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
[Thr 1532] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 1532] JLaunchRequestQueueInit: create pipe listener thread
[Thr 1636] JLaunchRequestFunc: Thread 1636 started as listener thread for np messages.
[Thr 644] WaitSyncSemThread: Thread 644 started as semaphore monitor thread.
[Thr 1532] Tue Sep 04 22:04:46 2007
[Thr 1532] INFO: Invalid property value [JLaunchParameters/]
[Thr 1532] JStartupIReadSection: debug mode is specified by program arguments
[Thr 1532] [Node: server0] java home is set by profile parameter
     Java Home: C:\j2sdk1.4.2_08
JStartupIReadSection: read node properties [ID4467550]
-> node name       : server0
-> node type       : server
-> java path       : C:\j2sdk1.4.2_08
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Dsun.io.useCanonCaches=false -verbose:gc -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=C:/usr/sap/J2E/SYS/global -Djava.awt.headless=true -XX:NewSize=85m -XX:MaxNewSize=85m -XX:MaxPermSize=192m -XX:PermSize=192m -XX:DisableExplicitGC -XX:UseParNewGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc
-> java vm version : 1.4.2_08-b03
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type    : server
-> java vm cpu     : x86
-> heap size       : 512M
-> init heap size : 512M
-> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster\server0
-> class path      : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> main class      : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters      :
-> debuggable      : yes
-> debug mode      : yes
-> debug port      : 50021
-> shutdown timeout: 120000
[Thr 1532] JLaunchISetDebugMode: set debug mode [yes]
[Thr 5300] JLaunchIStartFunc: Thread 5300 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack   : 262144 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: -Djava.security.policy=./java.policy
-> arg[ 3]: -Djava.security.egd=file:/dev/urandom
-> arg[ 4]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 5]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 6]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 7]: -Djco.jarm=1
-> arg[ 8]: -Dsun.io.useCanonCaches=false
-> arg[ 9]: -verbose:gc
-> arg[ 10]: -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar
-> arg[ 11]: -Dsys.global.dir=C:/usr/sap/J2E/SYS/global
-> arg[ 12]: -Djava.awt.headless=true
-> arg[ 13]: -XX:NewSize=85m
-> arg[ 14]: -XX:MaxNewSize=85m
-> arg[ 15]: -XX:MaxPermSize=192m
-> arg[ 16]: -XX:PermSize=192m
-> arg[ 17]: -XX:+DisableExplicitGC
-> arg[ 18]: -XX:+UseParNewGC
-> arg[ 19]: -XX:+PrintGCDetails
-> arg[ 20]: -XX:+PrintGCTimeStamps
-> arg[ 21]: -XX:SurvivorRatio=2
-> arg[ 22]: -XX:TargetSurvivorRatio=90
-> arg[ 23]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 24]: -verbose:gc
-> arg[ 25]: -Dsys.global.dir=C:\usr\sap\J2E\SYS\global
-> arg[ 26]: -Dapplication.home=C:\usr\sap\J2E\JC00\j2ee\os_libs
-> arg[ 27]: -Djava.class.path=C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 28]: -Djava.library.path=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI.ACE\;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;C:\usr\sap\J2E\SCS01\exe;C:\usr\sap\J2E\JC00\exe;C:\usr\sap\J2E\SYS\exe\run
-> arg[ 29]: -Xdebug
-> arg[ 30]: -Xnoagent
-> arg[ 31]: -Djava.compiler=NONE
-> arg[ 32]: -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=50021
-> arg[ 33]: -Dmemory.manager=512M
-> arg[ 34]: -Xmx512M
-> arg[ 35]: -Xms512M
-> arg[ 36]: -DLoadBalanceRestricted=no
-> arg[ 37]: -Djstartup.mode=JCONTROL
-> arg[ 38]: -Djstartup.ownProcessId=5276
-> arg[ 39]: -Djstartup.ownHardwareId=Z2123283434
-> arg[ 40]: -Djstartup.whoami=server
-> arg[ 41]: -Djstartup.debuggable=yes
-> arg[ 42]: -DSAPINFO=J2E_00_server
-> arg[ 43]: -DSAPSTARTUP=1
-> arg[ 44]: -DSAPSYSTEM=00
-> arg[ 45]: -DSAPSYSTEMNAME=J2E
-> arg[ 46]: -DSAPMYNAME=senthil_J2E_00
-> arg[ 47]: -DSAPDBHOST=
-> arg[ 48]: -Dj2ee.dbhost=senthil
[Thr 5300] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 2320] Tue Sep 04 22:04:55 2007
[Thr 2320] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 2320] JLaunchISetClusterId: set cluster id 4467550
[Thr 2320] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 2320] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 4712] Tue Sep 04 22:05:41 2007
[Thr 4712] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
[Thr 4712] *** ERROR => JHVM_RegisterNatives: registration for class com.sap.security.core.server.vsi.service.jni.VirusScanInterface failed. [jhvmxx.c     338]
[Thr 2320] Tue Sep 04 22:06:47 2007
[Thr 2320] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
[Thr 6132] Tue Sep 04 22:06:48 2007
[Thr 6132] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
[Thr 2128] Tue Sep 04 22:13:14 2007
[Thr 2128] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]
[Thr 5860] Wed Sep 05 21:49:01 2007
[Thr 5860] JLaunchIExitJava: exit hook is called (rc=-335)
[Thr 5860] JLaunchCloseProgram: good bye (exitcode=-335)
trc file: "C:\usr\sap\J2E\JC00\work\dev_server0", trc level: 1, release: "640"
node name   : ID4467550
pid         : 5224
system name : J2E
system nr. : 00
started at : Wed Sep 05 21:49:06 2007
arguments   :
    arg[00] : C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    arg[01] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
    arg[02] : -DSAPINFO=J2E_00_server
    arg[03] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
[Thr 5568] Wed Sep 05 21:49:06 2007
[Thr 5568] *** ERROR => Invalid property value [box.number/J2EJC00senthil] [jstartxx.c   789]
[Thr 5568] *** ERROR => Invalid property value [en.host/PWDF3013] [jstartxx.c   789]
[Thr 5568] *** ERROR => Invalid property value [en.port/3201] [jstartxx.c   789]
[Thr 5568] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
JStartupReadInstanceProperties: read instance properties [C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties]
-> ms host    : senthil
-> ms port    : 3601
-> OS libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> Admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Used property files
-> files [00] : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
Instance properties
-> ms host    : senthil
-> ms port    : 3601
-> os libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Bootstrap nodes
-> [00] bootstrap            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID4467500 : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID4467550 : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID4467500            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [01] ID4467550            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
[Thr 5568] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 5568] JLaunchRequestQueueInit: create pipe listener thread
[Thr 1716] JLaunchRequestFunc: Thread 1716 started as listener thread for np messages.
[Thr 1928] WaitSyncSemThread: Thread 1928 started as semaphore monitor thread.
[Thr 5568] INFO: Invalid property value [JLaunchParameters/]
[Thr 5568] JStartupIReadSection: debug mode is specified by program arguments
[Thr 5568] [Node: server0] java home is set by profile parameter
     Java Home: C:\j2sdk1.4.2_08
JStartupIReadSection: read node properties [ID4467550]
-> node name       : server0
-> node type       : server
-> java path       : C:\j2sdk1.4.2_08
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Dsun.io.useCanonCaches=false -verbose:gc -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=C:/usr/sap/J2E/SYS/global -Djava.awt.headless=true -XX:NewSize=85m -XX:MaxNewSize=85m -XX:MaxPermSize=192m -XX:PermSize=192m -XX:DisableExplicitGC -XX:UseParNewGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc
-> java vm version : 1.4.2_08-b03
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type    : server
-> java vm cpu     : x86
-> heap size       : 512M
-> init heap size : 512M
-> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster\server0
-> class path      : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> main class      : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters      :
-> debuggable      : yes
-> debug mode      : yes
-> debug port      : 50021
-> shutdown timeout: 120000
[Thr 5568] JLaunchISetDebugMode: set debug mode [yes]
[Thr 2500] JLaunchIStartFunc: Thread 2500 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack   : 262144 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: -Djava.security.policy=./java.policy
-> arg[ 3]: -Djava.security.egd=file:/dev/urandom
-> arg[ 4]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 5]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 6]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 7]: -Djco.jarm=1
-> arg[ 8]: -Dsun.io.useCanonCaches=false
-> arg[ 9]: -verbose:gc
-> arg[ 10]: -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar
-> arg[ 11]: -Dsys.global.dir=C:/usr/sap/J2E/SYS/global
-> arg[ 12]: -Djava.awt.headless=true
-> arg[ 13]: -XX:NewSize=85m
-> arg[ 14]: -XX:MaxNewSize=85m
-> arg[ 15]: -XX:MaxPermSize=192m
-> arg[ 16]: -XX:PermSize=192m
-> arg[ 17]: -XX:+DisableExplicitGC
-> arg[ 18]: -XX:+UseParNewGC
-> arg[ 19]: -XX:+PrintGCDetails
-> arg[ 20]: -XX:+PrintGCTimeStamps
-> arg[ 21]: -XX:SurvivorRatio=2
-> arg[ 22]: -XX:TargetSurvivorRatio=90
-> arg[ 23]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 24]: -verbose:gc
-> arg[ 25]: -Dsys.global.dir=C:\usr\sap\J2E\SYS\global
-> arg[ 26]: -Dapplication.home=C:\usr\sap\J2E\JC00\j2ee\os_libs
-> arg[ 27]: -Djava.class.path=C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 28]: -Djava.library.path=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI.ACE\;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;C:\usr\sap\J2E\SCS01\exe;C:\usr\sap\J2E\JC00\exe;C:\usr\sap\J2E\SYS\exe\run
-> arg[ 29]: -Xdebug
-> arg[ 30]: -Xnoagent
-> arg[ 31]: -Djava.compiler=NONE
-> arg[ 32]: -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=50021
-> arg[ 33]: -Dmemory.manager=512M
-> arg[ 34]: -Xmx512M
-> arg[ 35]: -Xms512M
-> arg[ 36]: -DLoadBalanceRestricted=no
-> arg[ 37]: -Djstartup.mode=JCONTROL
-> arg[ 38]: -Djstartup.ownProcessId=5224
-> arg[ 39]: -Djstartup.ownHardwareId=Z2123283434
-> arg[ 40]: -Djstartup.whoami=server
-> arg[ 41]: -Djstartup.debuggable=yes
-> arg[ 42]: -DSAPINFO=J2E_00_server
-> arg[ 43]: -DSAPSTARTUP=1
-> arg[ 44]: -DSAPSYSTEM=00
-> arg[ 45]: -DSAPSYSTEMNAME=J2E
-> arg[ 46]: -DSAPMYNAME=senthil_J2E_00
-> arg[ 47]: -DSAPDBHOST=
-> arg[ 48]: -Dj2ee.dbhost=senthil
[Thr 2500] Wed Sep 05 21:49:07 2007
[Thr 2500] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 1148] Wed Sep 05 21:49:15 2007
[Thr 1148] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 1148] JLaunchISetClusterId: set cluster id 4467550
[Thr 1148] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 1148] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 6136] Wed Sep 05 21:50:06 2007
[Thr 6136] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
[Thr 6136] *** ERROR => JHVM_RegisterNatives: registration for class com.sap.security.core.server.vsi.service.jni.VirusScanInterface failed. [jhvmxx.c     338]
[Thr 1148] Wed Sep 05 21:50:33 2007
[Thr 1148] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
[Thr 3344] Wed Sep 05 21:50:34 2007
[Thr 3344] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
[Thr 2620] Wed Sep 05 21:56:35 2007
[Thr 2620] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]
[Thr 5688] Thu Sep 06 10:29:06 2007
[Thr 5688] JLaunchIExitJava: exit hook is called (rc=-337)
[Thr 5688] JLaunchCloseProgram: good bye (exitcode=-337)
trc file: "C:\usr\sap\J2E\JC00\work\dev_server0", trc level: 1, release: "640"
node name   : ID4467550
pid         : 3688
system name : J2E
system nr. : 00
started at : Thu Sep 06 10:29:08 2007
arguments   :
    arg[00] : C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    arg[01] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
    arg[02] : -DSAPINFO=J2E_00_server
    arg[03] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_senthil
[Thr 3348] Thu Sep 06 10:29:08 2007
[Thr 3348] *** ERROR => Invalid property value [box.number/J2EJC00senthil] [jstartxx.c   789]
[Thr 3348] *** ERROR => Invalid property value [en.host/PWDF3013] [jstartxx.c   789]
[Thr 3348] *** ERROR => Invalid property value [en.port/3201] [jstartxx.c   789]
[Thr 3348] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
JStartupReadInstanceProperties: read instance properties [C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties]
-> ms host    : senthil
-> ms port    : 3601
-> OS libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> Admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Used property files
-> files [00] : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
Instance properties
-> ms host    : senthil
-> ms port    : 3601
-> os libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Bootstrap nodes
-> [00] bootstrap            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [01] bootstrap_

Activation error - Perhaps JAVA_HOME does not point to the JDK

Hi all,
After compiling and building my application locally I checked in the activity but activation failed with the following log:
Perhaps JAVA_HOME does not point to the JDK
     at org.apache.tools.ant.taskdefs.compilers.CompilerAdapterFactory.getCompiler(CompilerAdapterFactory.java:105)
     at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:929)
     at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:758)
     at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
     at org.apache.tools.ant.Task.perform(Task.java:364)
     at org.apache.tools.ant.Target.execute(Target.java:341)
     at org.apache.tools.ant.Target.performTasks(Target.java:369)
     at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
     at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:112)
     at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:61)
     at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:218)
     at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:195)
     at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)
     at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:347)
     at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:99)
     at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:73)
     at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:58)
     at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1723)
     at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1495)
     at com.sap.tc.buildcontroller.CBSBuildController.build(CBSBuildController.java:727)
     at com.sap.tc.buildcontroller.CBSBuildController.execCommand(CBSBuildController.java:503)
     at com.sap.tc.buildcontroller.CBSBuildController.evalCmdLine(CBSBuildController.java:442)
     at com.sap.tc.buildcontroller.CBSBuildController.run(CBSBuildController.java:314)
     at com.sap.tc.buildcontroller.CBSBuildController.exec(CBSBuildController.java:252)
     at com.sap.tc.buildcontroller.CBSBuildController.mainLoop(CBSBuildController.java:207)
     at com.sap.tc.buildcontroller.CBSBuildController.main(CBSBuildController.java:168)
This happen suddenly since build was successfull till last friday, so we're sure that something changed in server configuration but we don't know what... now we need to make the server works again!
thanks for any help.
Stefano

Hi ,
Check the jdk versions in SDM and your machine.
Make sure the JAVA_HOME environment variable is set to correct jdk version which is used by sdm.
Where to check the JDK version in sdm:
You can check which jdk is being used from the following file: /usr/sap/<SID>/<INSTANCE>/SDM/program/config/sdm_jstartup.properties
    under value of property "sdm.JavaPath"
Go to your system desktop and select mycomputer->rightclick and select properties ->
Advanced ->environment variables ->System Variables check the variable JAVA_HOME=c:\jdk1.6
Both jdk versions should be same.Then only sdm will deploy the appl properly.
Regards,
Lavanya.G

The test package does not point to the correct logical system

Hello,
I have defined SMSY logical componant, I have copied project1 to project2.
I have changed within the system landscape of project2, the logical componant.
I have also defined a project plan, and the test packages.
Hence, the test packages still do not point to the logical component that is defined in the landscape...
I must have missed something !
Can you help ?
Thanks a lot

hi
try following
1 check in smsy the logical component is correctly defined with clients dev qa and prd
2 same logical component is assigned to solar_project_admin
3 Project IMG is generated in the respective system
4 in solar01 check the logical component is shown correctly
5 Re- Generate the test plan once
hope above steps will resolve issue
regards
prakhar

EmCCR reports JAVA_HOME does not contain a valid JDK/JRE

Greetings,
I am seeing occasional emails from several OEM monitored targets reporting this issue. I have found a couple of support notes, 976112.1 & 832949.1 and understand the problem but am still unclear on a couple of things and hoping someone can assist me.
1) how to set the $JAVA_HOME variable. jdk is installed in both the $ORACLE_HOME and $AGENT_HOME directories. Does it matter which jdk I use?
2) The ccr directory is a subdirectory of the $ORACLE_HOME directory and the emCCR.jar file is also there. I assume that is the required jar file and so my $PATH must include that. Does that also mean the $JAVA_HOME variable should point there rather than at the $AGENT_HOME/jdk?
3) Note 976112.1 suggests setting the $JAVA_HOME variable in then running setupCCR. I do not find a setupCCR but I do find a configCCR. I am not sure which is the correct executable to use. emCCR status shows I have 12.0.0.0.1 installed -
iamdev1:product/11.2.0.2/dbhome_1/ccr/bin->./emCCR status
Oracle Configuration Manager - Release: 12.0.0.0.1 - Production
Copyright (c) 2005, 2013, Oracle and/or its affiliates. All rights reserved.
Start Date               04-Jan-2014 12:08:55
Last Collection Time     21-Jan-2014 12:07:00
Next Collection Time     22-Jan-2014 12:07:00
Collection Frequency     Daily at 12:07
Collection Status        idle
Log Directory            /usr/local/oracle/product/11.2.0.2/dbhome_1/ccr/hosts/devon/log
Registered At            12-Jun-2011 12:07:47
Automatic Update         On
Collector Mode           Connected
4) I am also unclear as to which documentation I should follow.
Any help or suggestions are greatly appreciated. Thank you.
Bill Wagman

Hi Solomon,
Please cross check your settings with the following post about "configuring WLS (10.3.2) on Mac".
http://forums.oracle.com/forums/thread.jspa?messageID=4008200&#4008200
- Ram

[CS3/4] activeBook does not point to "active Book"

Is it me misunderstanding something, or is the "activeBook" property broken?
Found out the hard way today that "app.activeBook" does *not* point to the, erm, 'active' book. Or maybe I don't understand what makes it the active one ... Remember, Books come in a palette, and while you can have one in the front and another in the back (which, I *think*, ought to make the visible one the 'active' book), you can also drag one book file out of it and put it elsewhere on your desktop. Now which one is active? Is the answer a simple "The one ID tells you is active, through the Application's 'activeBook' property"? Nope. That doesn't work at all.
In InDesign CS3 (Windows -- in case it makes a difference), app.activeBook always reports the alphabetically first one, of all your opened books. Didn't think of checking on CS4/Windows at work, but my home CS4/Mac does it exactly the opposite way: it always reports the alphabetically last one!
Steps to recreate:
1. Write a Javascript that simply reports the active book's name:
alert (app.activeBook.name)
2. Create a new book file "Book A". It will open a Books panel, and 'Book A' is the only item in there. Running the who-am-i script tells you "Book A.indb".
3. Now create a second book file "Book B". It will appear in the Books panel and be active -- the visible book. Sure enough, the who-am-i tells you now "Book B.indb".
4. So it works? No. Select "Book A" in the panel. The script still thinks "Book B" is active.
5. Drag one of the books out of its palette onto your workspace -- now you cannot see which one *is* active. The script ensures you it's still "Book B", and no amount of clicking, selecting, or otherwise manipulating either palette will make it change its mind.
I think 'activeBook' is a rather bad thought-out function -- after all, if you have two panels, and both have the Add document buttons and a menu, which one can be considered "active"?
On the other hand, the only time you -- yes you! John Q. User! -- would be sure to be able to tell which one is active, is when they are both in the same palette, one in front and the other in the back. But the script proves that wrong.
Maybe Adobe uses some other definition of the word 'active', for Books only? As far as I can tell, it works as expected for the two other properties activeDocument and activeWindow ...

What you are describing ia not a scripting bug, but rather a bug in the InDesign application, that I think I filed a couple of month's back. The issue cropped up in a C++ plug-in where it became obvious that InDesign can't figure out which book is active.
The bug is, that clicking on the little tab-like piece of a book panel doesn't trigger the kSetCurrentActiveBookCmdBoss Command notifying InDesign that the book has changed. In order to trigger command it is necesary to click on the main panel or it's flyout menu.
Since clicking on flyout menu makes front book active this bug rarely shows itself, except of course when writing a script.
File a bug report and maybe they'll fix this among many other book bugs.

Pointer does not move to the default button in the dialog box

example: when cleaning out trash the pointer does not go to the default button in the dialog box, you have to manually go there.
This happens all the time.

Hi Abhishek,
In SAP this job shows completed till the 3rd step. and no error in the job log. but it does not execute the 4th and the 5th steps. And in Redwood, it shows completed for 1st and 2nd steps, 3rd step is in Error but has no error log. The 4th and 5th steps are in chained status. I have not amended the job chain after import. I have just scheduled it as it was running in the SAP system.
Let me know if you need some further information on this.
Regards
madhu

When I enter time machine (on Time Capsule) i see the stack of screen shots and the time line. However, when I roll over the mouse pointer, the time line does not activate. The cancel button does not get me out of the app: have to alt cmd esc. Ideas?

When I enter time machine (on Time Capsule) i see the stack of screen shots and the time line. However, when I roll over the mouse pointer, the time line does not activate. The cancel button does not get me out of the app: have to alt+cmd+esc. Ideas?

I have never seen it but then I run SL which is much more reliable than Lion..
See
http://pondini.org/TM/E4.html
Check the master guru of all TM problems.

The name '' does not exist in the current context

I have a recurring problem where all of a sudden I can no longer see the values of my variables when I debug my unit tests. I cannot find a pattern as to when this happens but I experience this across one of every 20 tests that I write. Occasionally this
has also happened during normal debbuging of running code on my machine.
I have included 2 screen shots. The first is when it is working. I have a break point set at the declaration of list of types. At this point all my variables are still reporting their values back to the debugger. Once I step over this to the next line (screen
shot 2) I get the error message 'The name '[variable name]' does not exist in the current context'
This problem is annoying me to no end. If anyone has any insight as to why this might be happening I would be very much appreciative.
My Settings/Configuration
Using Visual Studio 2013 Premium (Version 12.0.31101.00 Update 4)
Projects are all set to Target Framework = .NET 4.5.1
Resharper 9.1 is installed
My active configuration is debug mode, Any CPU
My PC is 64bit and so is the O/S windows 8.1
All of my projects are also compiled and built in debug mode
For all my projects configuration debug has the Optimize Code check box unchecked
I am unit testing code in an outside project referenced by the unit testing project (standard unit test project setup)
I make use of the latest version of NSubstitute in my tests although I do not think that would have any bearing on this issue
I omitted the code following the error because it is not relevant. I had cut it out and replaced it with a Task.Delay(4) which resulted in the same issue.
What I have tried so far
I have tried debugging the unit test from Visual Studio Test Explorer instead of from Resharper with the same result.
If I remove 2 items at the end of the array it starts to work again (so 6 items initialized instead of 8)
I clean solution with rebuild has no effect
Removing properties of the array also seems to work, example remove all initialization of property Value
Mark as answer or vote as helpful if you find it useful | Igor

Hi IWolbers,
>>I have a recurring problem where all of a sudden I can no longer see the values of my variables when I debug my unit tests. I cannot find a pattern as to when this happens but I experience this across one of every 20 tests that I write. Occasionally
this has also happened during normal debbuging of running code on my machine.
So you mean that it worked well before, am I right?
If you debug the same app in other VS machine, does it work well? So we could make sure that whether it is related to the VS IDE.
Please disable all add-ins in your VS IDE, and then reset your VS settings, debug it again.
https://msdn.microsoft.com/en-us/library/ms247075(v=vs.100).aspx
Or you could run your VS in safe mode, debug it again, at least, we could know that whether it is the add-in's issue.
https://msdn.microsoft.com/en-us/library/ms241278.aspx
To make sure that it is not the project files' issue, create a new blank solution, copy the project files to the new solution, clean and rebuild the solution, check the result.
>>Once I step over this to the next line (screen shot 2) I get the error message 'The name '[variable name]' does not exist in the current context'
How about debugging it with "Step Into" instead of "Step Over"? Or you could add breakpoints between 234 line to 241 line, after the breakpoint is hit, check the watch window again. How about the result?
In addition, do you check other debugger window like local or others?
Best Regards,
Jack
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

The Web template does not exist in the master system

We are using a Web Template (ZPORTAL) as an access point to other web templates and to 0ANALYZER. We recieve an abort when the use logs on for the first time and is presented with the password change window. When they change the password and click ok, the following message is recieved: The Web template "ZPORTAL=" does not exist in the master system. After the abort, they go back to the ZPORTAL again in which case no abort occurs and they are able to navigate the web template. This only happens when they have to change their password. Has anyone else seen this?

Make sure the template exists in the system which is configured in the iView property.
There should be a one to one mapping between BI and EP systems.
You cannot connect 2 BI system to one EP system and configure BI JAVA

The name "Pi" does not exist in the namespace "clr-namespace:PressureVessels".

Pi is the name of a class.
I made some major modification to the program in VS 2013, then after transferring the program to another PC with VS 2012 running, I am getting many errors that says:
The name "ClassName" does not exist in the namespace "clr-namespace:PressureVessels".

Cleaning removes all the stuff out your bin.
If all this stuff is in the one solution then that's equivalent to manually deleting it.
If your app is composed from separate dll then I maybe some versioning issue.
If not and you can't reproduce the issue on your dev machine...
Tricky.
You would have mentioned it if you were putting stuff in the GAC.
Could be a sln or csproj issue.
They occasionally corrupt.
What else.
How did you get your code onto the other pc?
Is it contained within one folder with no external references beyond .net framework ones?
If you did something a bit dodgy with your references a dll might be coming from somewhere which is on your pc and not on this other one.
The only other advice I can think of is to step away for a bit and do something else.
It's all too easy to get into a flat spin when something drastic happens and one has no idea wtf is going on.
I used to be a points hound.
But I'm alright nooooooooooooooooooooooooooooOOOOOWWWW !

Field BSEG-HKTID does not exist in the additional data Screen

Hi
We are facing a problem while posting the parked document. Field BSEG-HKTID does not exist in the screen SAPLF040 0331.
As we want to avoid entering the field-data at the time of payment proposal run using T.code F110, we prefer to enter at the time of posting a parked document or at the time of parking.
We had checked the field status (of Posting key and GL) and its not available.
We refered note 953374 House bank details: Account ID in the document. It asks to activate the RE-FX component. However, we are not in the real estate business hence not logical to do so. How do we need to proceed?
PP

To do the same change with the transaccion FB02 y FB03, create an enhancemente point in the program: SAPMF05L dynpro: 1301, module: DYNPRO_MODIFIKATION, at the of perform open_fi_dynpro_mod and write:
LOOP AT SCREEN.
IF sy-tcode = 'FB02'.
    IF screen-name = 'BSEG-HKTID'.
      screen-input = 1.
      screen-invisible = 0.
      screen-active = 1.
      screen-output = 1.
      screen-group4 = ' '.
      MODIFY SCREEN.
      EXIT.
    ENDIF.
elseif sy-tcode = 'FB03'.
      IF screen-name = 'BSEG-HKTID'.
      screen-input = 0.
      screen-invisible = 0.
      screen-active = 1.
      screen-output = 1.
      screen-group4 = ' '.
      MODIFY SCREEN.
      EXIT.
    ENDIF.
endif.
ENDLOOP.
and, all ready.

Business system does not exist in the SLD

hi,
I am trying to export the ID objects into QA, when i get the error saying that "Business system D01 does not exist in the SLD".
I have created the Transport target for the D01 business system in the SLD to point to the QA system T01.
When i try to export the objects and reimport them into QA i get the above error.
Any ideas what could be missing?
Thanks,
Tirumal

hi,
Prashant -
I did refresh the cache but no luck. I still see only the QA Business system but not able to see the Dev SLD Business systems at all.
Stefan -
They are pointing to the same sld. If i do an sldcheck from QA XI Server it directs me to the dev SLD. So this is good.
I am using only 1 SLD. Is there a way that i can tell QA to look for DEV SLD instead of QA SLD?
Thanks,
Tirumal

Yahoo e-mail page is distorted and hard to read (once in a while its OK) - box does not extend to the right side making e-mail info hard to read. Info displayed in the reading panel is OK.

When I open the Yahoo email page, the box does not extend across the screen and the script is distorted making it hard to read the source, subject etc. The reading panel info reads OK. All other pages of Yahoo are not distorted.

Many of your points are totally legitimate.
This one, however, is not:
…To put it another way, the design of the site seems to be geared much more towards its regular users than those the site is supposedly trying to "help"…
The design and management of the forums for more than five years have driven literally dozens of the most valuable contributors and "regulars" away from the forums—permanently.
The only conclusion a prudent, reasonable person can draw from this state of affairs is that Adobe consciously and deliberately want to kill these forums by attrition—without a the PR hit they would otherwise take if they suddenly just shut them down.

DDNTF_CONV_UC~" does not exist in the ABAP Dictionary

Hello Experts ,
We are migrating our ECC system from Oracle to HANA DB using DMO - during Post Processing phase we are getting the following error :
(screenshot attached)
4 ETG003 Table "DDNTF_CONV_UC~" does not exist in the ABAP Dictionary
4 ETG003 Table "DDNTF~" does not exist in the ABAP Dictionary
4 ETG003 Table "DDNTT_CONV_UC~" does not exist in the ABAP Dictionary
4 ETG003 Table "DDNTT~" does not exist in the ABAP Dictionary\
1. Am not sure why Shadow tables are considered in this phase ?
2. What steps i can follow to fix this error ?[I tried activating those using se14 but activation button is disabled].
3. I have a option to ignore and move forward but am not sure about the side affects ?
Source ECC6 Ehp5 702 on Oracle.
Target ECC6 Ehp7 740 on HANA.
SUM SP12 PL02
Thanks
Dev

Hi Avinash,
two comments on this:
This is not an issue, as this text is NOT an error message.
(An error message lists the "E" as second character,
but the screenshot above shows a space as second character.)
The log handling for this phase will be adapted in SUM SP13, so that non-errors are not listed at this point, to avoid this confusion.
SUM 1.0 SP12 PL 1 to PL 3 must not be used any longer, see SAP Note 2122247.
Regards, Boris

JAVA_HOME does not point to the JDK

Similar Messages

Maybe you are looking for