Error: Could Not Open jvm.cfg While Using ZappySys JDBC Bridge Driver

ODBC PowerPack
1

When using the ZappySys JDBC Bridge Driver, you may encounter the following error:

Error: could not open jvm.cfg

This issue occurs when the Java Virtual Machine (JVM) configuration file (jvm.cfg) is missing, corrupted, or inaccessible. The JDBC driver relies on a proper Java Runtime Environment (JRE/JDK) to initialize, so if the JVM cannot start, the driver fails to load.

Root causes

One or more of these:

  1. Wrong JAVA_HOME or PATH — points to an incomplete or mismatched directory.
  2. Corrupt or partial JRE/JDK install — missing jvm.cfg file.
  3. Mixing 32-bit and 64-bit Java binaries — e.g., java.exe from System32 but jvm.cfg from Program Files (x86).
  4. Leftover symbolic link (especially from older Oracle Java path shims like C:\Program Files (x86)\Common Files\Oracle\Java\javapath).
  5. System32 shadowing — an outdated Java copy under C:\Windows\System32 hijacks execution.

Step-by-step Fix

Step 1 — Check which Java is running

Run this in Command Prompt:

where java

You’ll likely see multiple entries like:

C:\Windows\System32\java.exe C:\Program Files\Common Files\Oracle\Java\javapath\java.exe C:\Program Files\Java\jdk-17\bin\java.exe

:backhand_index_pointing_right: The first one is what Windows is actually using.

Step 2 — Test the correct one manually

Run:

"C:\Program Files\Java\jdk-17\bin\java.exe" -version

If that works fine — your install is good. The issue is with the PATH .

Step 3 — Fix your PATH

Open System Properties → Environment Variables → System Variables → Path .

  • Remove any entries like:
C:\Program Files (x86)\Common Files\Oracle\Java\javapath

or

C:\Windows\System32

(if it contains java.exe)

  • Add your valid JDK path:
C:\Program Files\Java\jdk-17\bin

Then open a new CMD window and confirm:

java -version

Step 4 — Verify jvm.cfg exists

Go to your JDK folder, e.g.:

C:\Program Files\Java\jdk-17\jre\lib\amd64\jvm.cfg

or for newer JDKs:

C:\Program Files\Java\jdk-21\conf\jvm.cfg

If it’s missing, reinstall Java — that’s not fixable manually.

Step 5 — Clean up stray copies

Optional but recommended:

where javadel "C:\Windows\System32\java.exe"del "C:\Program Files\Common Files\Oracle\Java\javapath\java.exe"

:warning: Do this only if you verified the correct one works elsewhere.

Quick Fix Summary

Problem Fix
jvm.cfg missing Reinstall JDK
Wrong PATH or JAVA_HOME Correct to real JDK path
Old Oracle shim Remove javapath entries
Multiple Java installs Keep only one active version

If you want, paste your output of:

where javaecho %JAVA_HOME%java -version

Best Practices

  • Always use a 64-bit version of Java if your application (SSIS, Power BI, etc.) is 64-bit.
  • Avoid manually copying Java folders.
  • Keep only one active Java installation when possible.
  • After upgrading Java, recheck your ZappySys JDBC Bridge Driver settings to ensure paths are still valid.

Conclusion

The error “Could not open jvm.cfg” while using ZappySys JDBC Bridge Driver typically indicates a missing or misconfigured Java installation. Verifying your Java environment variables, reinstalling Java.

References