2. Check
the JControl Developer Trace File
If the J2EE Engine was started, analyze the following trace file:
<DIR_INSTANCE>/work/dev_jcontrol
The following problems may have been logged:
● Instance properties files are missing or empty:
*** ERROR => JStartupReadArgumentsEx: can't enumerate nodes [<DIR_INSTANCE>\j2ee\cluster\instance.properties; <DIR_INSTANCE>\SDM\program\config\sdm_jstartup.properties] (rc=-1)
In this case, check the installation log files for previous error messages and retry the installation.
· Connecting to the Message Server fails:
*** ERROR => Can't attach to message server (<hostname>/<port>) [rc=-100]-> terminate
Check that the SCS instance (the SAP Central Services instance containing the Message Server and the Enqueue Server for the J2EE Engine) on host <hostname> is running and that the Message Server port is correct.
· Detecting the Java Development Kit fails:
*** ERROR => invalid
vm detection, please have a look the files
- java command ["C:\j2sdk1.4.2_02\jre\bin\java.exe" -cp . JdkDetection_<pid> >
./JdkDetection_<pid>.txt 2>&1]
- output file
[./JdkDetection_<pid>.txt]
- java file
[./JdkDetection_<pid>.java]
- class file
[JdkDetection_<pid>]
- used vm type [-server]
- used vm type []
*** ERROR => can't get JDK information (rc=-1)
Verify that the bootstrap.JavaPath property in the <DIR_INSTANCE>/j2ee/cluster/instance.properties file points to a full version of the Java Development Kit (and not to an installation of the Java Runtime Environment).
Retry the command in the <DIR_INSTANCE>/work directory from a command interpreter.
· The instance bootstrap fails:
*** ERROR => invalid return code of process [bootstrap] (exitcode=-1)
Check the bootstrap log files. See 4. Check the Instance Bootstrap Log File from the Java VM.
· The instance bootstrap does not terminate.
In this case, the last block in the dev_jcontrol file is:
***************************************************************
JStartupStartJLaunch: program = <DIR_INSTANCE>/j2ee/os_libs/jlaunch
-> arg[00] = <DIR_INSTANCE>/j2ee/os_libs/jlaunch
-> arg[01] =
pf=<DIR_SYSTEM>/SYS/profile/<SYSTEM>_<INSTANCE>_<host>
-> arg[02] =
-file=<DIR_INSTANCE>/j2ee/cluster/instance.properties
-> arg[03] = -syncSem=JSTARTUP_WAIT_ON_<pid>
-> arg[04] = -nodeName=bootstrap
-> arg[05] = -nodeId=-1
-> arg[06] = -jvmOutFile=<DIR_INSTANCE>/work/jvm_bootstrap.out
-> arg[07] = -stdOutFile=<DIR_INSTANCE>/work/std_bootstrap.out
-> arg[08] = -locOutFile=<DIR_INSTANCE>/work/dev_bootstrap
-> arg[09] = -mode=BOOTSTRAP
-> arg[10] =
pf=<DIR_SYSTEM>/SYS/profile/<SYSTEM>_<INSTANCE>_<host>
-> lib path = <...>
-> exe path = <...>
****************************************************************
Check the bootstrap log files. See 6. Check whether the instance bootstrap terminates.
If you cannot find any problems in the JControl developer trace file, create a customer message for the BC-JAS-COR component, create an archive containing the installation log files and all files from the <DIR_INSTANCE>/work directory, and send the archive as an attachment to the customer message.