TechNote (Archived)

ColdFusion MX 6.1: Entry point error when running Web Server Configuration tool

Issue

When launching the Web Server Configuration utility, wsconfig, in GUI mode, a pop-up alert containing an error message appears and wsconfig fails.

On Windows, the Web Server Configuration utility, found atcf_root\runtime\bin\wsconfig.exe, may fail when run as a GUI. When this occurs, the following pop-up error message appears:

 The procedure entry point JVM_GetClassAccessFlags@8 could not be located in the dynamic link library jvm.dll

The caption bar for the pop-up alert will contain the message:

 wsconfig.exe - Entry Point Not Found

This issue is due to a defect in the ZeroG installer used by ColdFusion MX which mistakenly installs a "hotspot" directory containing a Sun JVM 1.3.1 jvm.dll into the ColdFusion 1.4.2 JRE directory cf_root\runtime\jre\. When launching wsconfig.exe in GUI mode by double-clicking on it, the installer finds the inappropriate JVM atcf_root\runtime\jre\hotspot\jvm.dll (1.3.1 JVM) instead of the intended JVM at cf_root\runtime\jre\bin\server\jvm.dll or cf_root\runtime\jre\bin\client\jvm.dll, both of which are JRE version 1.4.2. When the installer executes code developed for the 1.4.2 JVM but run with the 1.3.1 JVM, an internal conflict arises and wsconfig.exe fails.

This problem is logged as Macromedia issue 53401. This issue has been resolved in ColdFusion MX 7.

Solution

Search for the directorycf_root\runtime\jre\hotspot\.
If the hotspot directory is present, rename it. If it isnot present, skip to step 4.
Run wsconfig.exe. If successful, skip the remaining steps; if the error occurs, continue with step 4.
Search the system for any jvm.dll files to determine if there was another JRE outside cf_root\runtime\jre\ that was detected by wsconfig.exe.
If you find any versions of jvm.dll outside of thecf_root directory, rename those files temporarily, making note of the original names. If no other versions are found, skip to step 7.
Run wsconfig.exe. If successful, rename the jvm.dll files found in step 5 back to their original names.
If neither of the situations above resolve the problem, wsconfig.jar must be run manually using the command-line interface or the configuration batch files found incf_root\bin\connectors\. If you use the command line interface, the command should start with the full path to the coldfusion 1.4.2 java executable,cf_root\runtime\jre\bin\java; for example, c:\cfusionmx\runtime\jre\bin\java -jar c:\cfusionmx\runtime\lib\wsconfig.jar. If the configuration batch files are used instead, then the java executable will already be correctly configured in the batch file. See the documentation on Web server configuration for details.