MetricSign
EN|NLRequest Access
High severitydata source

Power BI Refresh Error:
ParquetJavaInvocationException

What does this error mean?

ADF failed to invoke the Java runtime for Parquet file processing. ADF uses Java-based libraries for Parquet read/write — a JRE failure or memory issue causes this error.

Common causes

  • 1The Java Runtime Environment on the integration runtime is out of date or missing
  • 2The integration runtime does not have enough memory to process the Parquet file
  • 3A transient error occurred in the JVM during Parquet processing

How to fix it

  1. 1Upgrade the self-hosted integration runtime to the latest version, which includes an updated Java runtime.
  2. 2Ensure the integration runtime machine has at least 8 GB of RAM for Parquet processing.
  3. 3Limit concurrent copy activities on the IR to reduce memory pressure.
  4. 4Retry the activity — some JVM errors are transient and resolve on retry.

Frequently asked questions

Does this error affect all pipeline runs or just the current one?

Depends on the root cause. A persistent misconfiguration fails every run; a transient issue may resolve on retry. Check the run history.

Can this error appear in Azure Data Factory and Microsoft Fabric pipelines?

Yes — the same connector errors appear in both ADF and Fabric Data Factory pipelines.

How do I see the full error detail for an ADF pipeline failure?

In ADF Monitor, click the failed run, then the failed activity. The detail pane shows the error code, message, and sub-error codes.

Will downstream Power BI datasets be affected when an ADF pipeline fails?

Yes — a dataset refreshing after the pipeline will use stale data or fail if the target table was cleared. The Power BI refresh may succeed while serving wrong data.

Official documentation: https://learn.microsoft.com/en-us/azure/data-factory/connector-troubleshoot-parquet

Other data source errors