SUMJava failed in phase Start Java shadow instance

[Former Member]

Hello,

We are executing SUMjava. The process failed in phase Start Java shadow instance. Problem is with starting shadow instance JC02 during bootstrap. The errors found in log log_bootstrap.0.log is:

Exception occurred for component [internal/unkown] of type [unkown]

com.sap.engine.bootstrap.SynchronizationException: Database index contains file [/ext/com.adobe~DocumentServicesLibrary/DocumentServicesLibrary.jar] that cannot be found in [bin\runtime/ext/com.adobe~DocumentServicesLibrary/DocumentServicesLibrary.jar]

When bootstrap.properties file is modified to skip synchronization (option element.resynch = skip), following message appears:

Bootstrap properties file [/usr/sap/SMX/SUM/sdt/system/SMX/JC02/j2ee/cluster/bootstrap/bootstrap.properties] found [kernelProperties.bin] file not found; forcing [detect] mode

Please let me know if any known solution is available to this error. We are stuck for several days on this error.

Thank You

[former_member185239]

Hi Matej,

Make the parameter element.resynch = Force in bootstrap.properties file.

Rename the folder server0 and dispatcher folder inside cluster.

Take a restart of the Server, it will create the folder server0 and dispatcher once again.

After that resync the SDM with the OS level and database.

Follow the below link to https://scn.sap.com/thread/3734853

Also paste the bootstrap log files.

With Regards

Ashutosh Chaturvedi

[Former Member]

We have managed to solve the issue by replicating the kernelProperties.bin file to /bootstrap and /cluster subfolders.

However SUM cannot continue due to the error with sapcontrol. When SUM tries to check the status of JAVA, some kind of trace file is not available. When replicating issue in command line, the result is as follows:

smx:smxadm 442> sapcontrol -nr 2 -host smx -user smxadm ****** -prot NI_HTTP -function GetTraceFile

28.09.2016 10:17:31

GetTraceFile

FAIL: Cannot open file

[former_member185239]

great!!

[Former Member]

Followed note 172827 and this helped with the sapcontrol error.