Invalid Shared Library Path (in dev_<component name>) (SAP Library

Invalid Shared Library Path (in dev_<component name>)

The VM detection builds the library path to find the JVM shared library. If this path is incorrect, you will receive the following error messages in the dev_<node name> trace file:

This graphic is explained in the accompanying text

*** ERROR => DlLoadLib: LoadLibrary(jvm.dll) Error 126

Error 126 = "The specified module could not be found."

*** ERROR => Can't load VM shared library (jvm.dll) (rc=-2)

*** ERROR => Can't load DLL for Java VM

*** ERROR => can't launch program (rc=-2)

JLaunchCloseProgram: close program (exitcode=-2)

Solution

Check the javaVMLibPathproperty in the VM property file (instance.properties.vmprop). The file is located in the cluster directory of the J2EE instance. In the example below, the incorrect property line is in bold (instead of “jre” the path contains “lall”). The <component name> can be bootstrap, dispatcher, server<n>, and so on.

Example

#test1. : ----------------------------------------

#test1. : generated VM parameters

#test1. : Tue May 06 08:26:28 2003

#test1. : ----------------------------------------

<component name>.javaVMPath=C:\jdk1.3.1_07

<component name>.javaVMVersion=1.3.1

<component name>.javaVMVendor=Java HotSpot(TM) Client VM (build 1.3.1_07-b02, mixed mode)

<component name>.javaVMType=classic

<component name>.javaVMLibPath=C:\jdk1.3.1_07\lall\bin\classic;C:\jdk1.3.1_07\jre\bin

<component name>.javaVMExePath=C:\jdk1.3.1_07\bin

<component name>.javaVMPropVers=1.0