on 05-16-2007 11:29 PM
We just added a dialog instance on a new server, sapinst runs all the way through, but fails because it cannot start the instance.
This is the trace file for dev_Jcontrol.
I do remember this is kind of a false error, because all of the java settings are correct. Can anybody help us with this?
-
trc file: "D:\usr\sap\PP1\J00\work\dev_jcontrol", trc level: 1, release: "700"
-
node name : jcontrol
pid : 3544
system name : PP1
system nr. : 00
started at : Wed May 16 15:05:37 2007
arguments :
arg[00] : D:\usr\sap\PP1\J00\exe\jcontrol.EXE
arg[01] : pf=
bksaprtlc1\sapmnt\PP1\SYS\profile\PP1_J00_bksaprtld1
[Thr 2100] Wed May 16 15:05:37 2007
[Thr 2100] *** WARNING => INFO: Unknown property [instance.en.host=bksaprtlc1] [jstartxx.c 841]
[Thr 2100] *** WARNING => INFO: Unknown property [instance.box.number=PP1J00bksaprtld1] [jstartxx.c 841]
[Thr 2100] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c 841]
[Thr 2100] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c 841]
**********************************************************************
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\PP1\J00\j2ee\cluster\instance.properties]
-> ms host : bksaprtlc1
-> ms port : 3900
-> OS libs : D:\usr\sap\PP1\J00\j2ee\os_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
**********************************************************************
**********************************************************************
Used property files
-> files [00] : D:\usr\sap\PP1\J00\j2ee\cluster\instance.properties
**********************************************************************
**********************************************************************
Instance properties
-> ms host : bksaprtlc1
-> ms port : 3900
-> os libs : D:\usr\sap\PP1\J00\j2ee\os_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
**********************************************************************
**********************************************************************
Bootstrap nodes
-> [00] bootstrap : D:\usr\sap\PP1\J00\j2ee\cluster\instance.properties
**********************************************************************
**********************************************************************
Worker nodes
**********************************************************************
[Thr 2100] [Node: bootstrap] java home is set by profile parameter
Java Home: d:\usr\java
[Thr 2100] *** ERROR => JStartupIGetJDKInfo: Cannot find Java compiler [d:\usr\java\bin\javac.exe]. [jstartxxi.c 968]
[Thr 2100] *** ERROR => can't get JDK information (rc = -1) [jstartxxi.c 1240]
[Thr 2100] **********************************************************************
ERROR => JDK Detection failed.
Please see SAP Note 943602 , section 'JDK detection issues'
for additional information and trouble shooting.
**********************************************************************
[Thr 2100] *** ERROR => can't read bootstrap node properites (rc=-1) [jcntrxx.c 1247]
[Thr 2100] JControlCloseProgram: started (exitcode = -1)
[Thr 2100] JControlCloseProgram: good bye... (exitcode = -1)
Perry,
Is your JAVA_HOME environment variable set correctly in all locations? You should add the jre path (d:\usr\java\bin) to the system path variable.
<i>Cannot find Java compiler [d:\usr\java\bin\javac.exe].</i>
-jwise
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, believe it or not, it had nothing to do with java path, it was a permissions issue. I went back to the install docs. it said that SAPService<SID> should not be a member of domain users and its primary group should be SAP_<SID>_GlobalAdmin. I made the changes, and "VIOLA", it started....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Perry,
See if this helps :
The engine is not able to start due to problems detecting the JDK.
<b>1.</b> Check that you have installed the correct JDK version. Read the section entitled 'Confirmation of the VM in use' in Note 943498 to find the appropriate platform-specific note.
To identify the current version of the JDK, execute the following command at command line level:
java -version You must have installedthe complete JDK/JSDK (including the Java Compiler javac).
<b>2.</b> Check if there are redundant JDK versions and make sure that the SAP J2EE Engine uses the correct JDK version. Therefore, <b>verify thecorresponding parameter in the instance profile
/usr/sap/<SID>/SYS/profile/<SID>_JC<num>_<host>
jstartup/vm/home = <jdk home directory>.
This parameter has a higher priority than the environment variable JAVA_HOME. </b> - On Unixsystems, it is important to verify the user rights.
If you experience problems with the JDK, open a message under the component for the relevant JDK provider (for example, BC-OP-SUN-JSE).
Thanks,
Sai Kondapi.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.