MetricSign
EN|NLRequest Access
Medium severitydata source

Power BI Refresh Error:
OrcDateTimeExceedLimit

What does this error mean?

A datetime value in an ORC file exceeds ADF's valid ticks range. Values like 0001-01-01 00:00:00 fall outside the valid range due to differences between the Julian and Gregorian calendars.

Common causes

  • 1The ORC file contains datetime values of 0001-01-01 00:00:00, which in some calendar systems falls outside the valid ticks range
  • 2Calendar conversion differences between Julian and proleptic Gregorian calendar produce an out-of-range ticks value

How to fix it

  1. 1Check the ticks value referenced in the error message and identify the source column producing it.
  2. 2Avoid using the datetime value 0001-01-01 00:00:00 in ORC datetime columns — replace with NULL or a valid default date.
  3. 3Filter or transform out-of-range datetime values in the source before writing to ORC.

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-orc

Other data source errors