What causes HRESULT: 0x8007007E?

Java Runtime Environment (JRE) is not installed on the Self-hosted Integration Runtime node machine. The installed JRE bitness (32-bit vs 64-bit) does not match the bitness of the Self-hosted Integration Runtime installation. The JAVA_HOME environment variable is not set or points to an incorrect JRE installation path. The JRE installation is corrupted or the jvm.dll file is missing from the expected path within the JRE directory

How do I fix HRESULT: 0x8007007E?

Step 1: Determine the bitness of your Self-hosted Integration Runtime (32-bit or 64-bit) and download the matching JRE version from https://go.microsoft.com/fwlink/?LinkId=808605 or the official Java distribution.. Step 2: Install the JRE on the Self-hosted IR node machine, ensuring it is a supported version (JRE 8 or later is typically required for ORC/Parquet processing in ADF).. Step 3: Set the JAVA_HOME system environment variable to the root directory of the installed JRE (e.g., C:\Program Files\Java\jre1.8.0_XXX) and add %JAVA_HOME%\bin to the system PATH.. Step 4: Restart the Self-hosted Integration Runtime service (and the machine if needed) so the new environment variables and DLL paths are loaded.. Step 5: Re-run the failing ADF activity to confirm the jvm.dll is now found; if the error persists, verify the exact path of jvm.dll and check for conflicting JRE installations.

High severityconfigurationAzure Data Factory →

Power BI Refresh Error:
HRESULT: 0x8007007E

What does this error mean?

HRESULT 0x8007007E (Unable to load DLL 'jvm.dll') occurs on a Self-hosted Integration Runtime node when Java Runtime Environment (JRE) is missing or not properly configured, preventing ADF from processing Java-dependent file formats such as ORC or Parquet.

Common causes

1Java Runtime Environment (JRE) is not installed on the Self-hosted Integration Runtime node machine
2The installed JRE bitness (32-bit vs 64-bit) does not match the bitness of the Self-hosted Integration Runtime installation
3The JAVA_HOME environment variable is not set or points to an incorrect JRE installation path
4The JRE installation is corrupted or the jvm.dll file is missing from the expected path within the JRE directory

How to fix it

1Step 1: Determine the bitness of your Self-hosted Integration Runtime (32-bit or 64-bit) and download the matching JRE version from https://go.microsoft.com/fwlink/?LinkId=808605 or the official Java distribution.
2Step 2: Install the JRE on the Self-hosted IR node machine, ensuring it is a supported version (JRE 8 or later is typically required for ORC/Parquet processing in ADF).
3Step 3: Set the JAVA_HOME system environment variable to the root directory of the installed JRE (e.g., C:\Program Files\Java\jre1.8.0_XXX) and add %JAVA_HOME%\bin to the system PATH.
4Step 4: Restart the Self-hosted Integration Runtime service (and the machine if needed) so the new environment variables and DLL paths are loaded.
5Step 5: Re-run the failing ADF activity to confirm the jvm.dll is now found; if the error persists, verify the exact path of jvm.dll and check for conflicting JRE installations.

Frequently asked questions

Which Java version should I install for ADF Self-hosted IR to support Parquet and ORC?

Microsoft recommends JRE 8 (64-bit) for 64-bit Self-hosted IR installations; ensure you install a JDK or JRE distribution from Oracle, Amazon Corretto, or Eclipse Temurin — the bitness must exactly match the IR.

Can multiple JRE versions cause this error even if one is installed?

Yes — if multiple JRE versions are installed and JAVA_HOME points to the wrong one, or if the PATH resolves to a mismatched version, ADF may still fail to load jvm.dll; remove conflicting installations and ensure JAVA_HOME points explicitly to the correct version.