Qlik Stitch: MySQL integration extraction error “Fatal Error Occurred YEAR“

David_Apodaca — Mon, 08 Dec 2025 09:28:03 GMT

MySQL extraction encounters the following error:

FATAL [main] tap-hp-mysql.main - Fatal Error Occurred - YEAR

Resolution

Identify columns storing date/time values.

Query for invalid years
For example:

YEAR(date_column) < 1 OR YEAR(date_column) > 9999

Correct invalid records or replace them with valid defaults.
If you cannot modify source data, deselect the problematic column in table settings in the integration.
Consider enforcing valid ranges via application-level validation or MySQL constraints.
If using MySQL zero dates (0000-00-00), adjust SQL mode or replace with valid dates.

Cause

This error occurs when the MySQL integration attempts to process a DATE, DATETIME, or TIMESTAMP field containing an invalid year value. Common examples include 0 or any year outside the supported range. The error message typically states "Fatal Error Occurred" followed by details about the invalid year or month value.

The underlying Python library used by the Stitch MySQL integration enforces strict date parsing rules. It only supports years in the range 0001–9999. If the source data contains values less than 0001 or greater than 9999, the extraction will error. This issue often arises from legacy data, zero dates (0000-00-00), or improperly validated application inserts.

Any column selected for replication that contains invalid date values will trigger this error.

article Qlik Stitch: MySQL integration extraction error “Fatal Error Occurred YEAR“ in Official Support Articles

Qlik Stitch: MySQL integration extraction error “Fatal Error Occurred YEAR“

Resolution

Cause

Environment