Note 997510 - Troubleshooting J2EE Engine 6.40/7.

0 Bootstrap Issues

Note Language: English Version: 3 Validity: Valid from 27.02.2007

Summary

Symptom
The j2ee engine does not start because bootstrap fails to synchronize the
files from the database and exits with non-zero return code.

More Terms
bootstrap, invalid return code of process [bootstrap] ,
JControlExecuteBootstrap: error executing bootstrap

Cause and Prerequisites

J2EE Engine startup fails and in the dev_jcontrol file located in the
instance work folder one can see an error similar to:
[Thr 1] *** ERROR => invalid return code of process [bootstrap]
(exitcode=66) [jstartxx_mt. 1452]
[Thr 1] JControlExecuteBootstrap: error executing bootstrap node
[bootstrap] (rc=66)

The Bootstrap module can fail to synchronize the engine's files because
of:

o Not started database

o Corrupted database

o Not enough or missing file system permissions

o Wrong installation type (32 bit binaries on 64 bit machine)

o Errors in the bootstrap.properties file

o Errors in the bootstrap logic

Solution
Bootstrap log files location

The bootstrap log files can be found in /usr/sap/<SID>/JC<XX>/work/

folder. The log files there are as follows:

o dev_bootstrap* - logs from the Startup Framework that shows the

parameters with which the bootstrap was started

o log_bootstrap* - logs from the execution of the bootstrap. Shows

the execution flow from the last session and the possible errors

o jvm_bootstrap* - logs from the JVM output for the bootstrap

process. Shows possible JVM problems during the bootstrap
execution.

Troubleshooting problems related to the database and the jdbc driver

If in bootstrap log files one sees the error:

SynchronizationException: Database initialization failed!Check database
properties!
scroll down to the last caused by statement, to identify the real reason

15.09.2008 Page 1 of 3
 Note 997510 - Troubleshooting J2EE Engine 6.40/7.0 Bootstrap Issues

for the error. It will usually fall in one of the following categories:

o Database not started. Make sure the database is started and

accessible. To test whether this is the case, try to connect with
Config Tool, and an external db vendor provided tool.

o User or password for connection to the database are either

incorrect or the password has expired. Make sure the connection
details in Secure Store are the correct ones, if necessary change
the jdbc/pool/<SID>/Password and jdbc/pool/<SID>/User via Config
Tool.

o If java.lang.ClassNotFoundException is present as a cause for the

bootstrap error, most likely the driver class specified in Secure
Store is incorrect, or the driver jar file cannot be found. In
this case check whether the path to the driver jar files is
configured correctly in SecureStore.

o "java.sql.SQLException: No suitable driver" exceptions may indicate

an incorrect URL: The driver class configured in the secure store
could be loaded with the driver path specified but it could not be
assigned to the JDBC URL.Check the entries in the secure
store(/usr/sap/<SID>/SYS/global/security/data/SecStore.properties).

If in bootstrap log files one sees the error:

com.sap.engine.bootstrap.SynchronizationException: os.bit.length
property not set correctly [XX] ! Check database consistency! JVM
reported [YY] where XX and YY are 32 and 64 respectively, apply note 771132
to resolve the issue.

If in the bootstrap log files one sees the following error:

Can't load main class [com.sap.engine.offline.OfflineToolStart] or
Exception occurred:com.sap.engine.bootstrap.SynchronizationException: Error
reading local folder [C:\usr\sap\J2E\JC00\j2ee\cluster\bootstrap]! Check
permitions!
or some other IO error stating other botstrap class or file cannot be read
check the permissions on the ../j2ee/cluster/bootstrap folder and make sure
the <sid>adm has the right to read , write and execute those files.

If in bootstrap log files one sees an error pointing out that secure store
properties files cannot be read or cannot be found, or that some iaik class
cannot be found, check the following:

o Whether the file ../j2ee/cluster/bootstrap/bootstrap.properties

contains correct entries. Make sure there are no extra spaces at
the end of the lines.

o If the folder SYS\global\security\lib\engine contains the iaik jar

files.

o If the file SYS\global\security\data\SecStore.properties exists and

has the correct permissions.

If none of the above suggestions help, gather the following log files:

o all std_bootstrap* files from the instance work folder

15.09.2008 Page 2 of 3
 Note 997510 - Troubleshooting J2EE Engine 6.40/7.0 Bootstrap Issues

o all jvm_bootstrap* files from the instance work folder

o all dev_bootstrap* files from the instance work folder

o system.log from \j2ee\cluster\bootstrap folder

and open a support ticket attaching them to it.

Header Data
Release Status: Released for Customer
Released on: 27.02.2007 09:22:52
Priority: Recommendations/additional info
Category: Help for error analysis

Main Component BC-JAS-COR Enterprise Runtime, Core J2EE Framework

Valid Releases
Software Component Release From To Release and Following
Release
SAP-JEE 60 6.40 6.40
SAP-JEE 7.00 7.00 7.00

15.09.2008 Page 3 of 3