Power BI refresh failing with ODBC "Invalid date, time or timestamp value" error on Snowflake

[nathangriffiths]

Hi,

One of our Power BI datasets often (but not always) fails to refresh from a Snowflake connection and throws an error of:

ODBC: ERROR [22007] [Microsoft][Support] (40490) Invalid date, time or timestamp value.

We thought it may be related to an issue with the Snowflake driver version Power BI is using (also discussed in this thread https://community.powerbi.com/t5/Service/ODBC-ERROR-22007-Microsoft-Support-40490-Invalid-date-time-...

However if we run SELECT CURRENT_CLIENT() in Power BI it returns version 2.24.3 for the Snowflake driver which is a newer version of the Snowflake ODBC driver than the one where the issue discussed in that thread was supposedly resolved (2.24.2) .

Can anyone suggest another reason why we would intermittently see this error when refreshing from Snowflake?

From the Snowflake ODBC driver change log:

[julsr]

This error is happening again. Is there a workaround, or what should I do?

[v-cazheng-msft · Accepted solution]

Hi @nathangriffiths ,

It’s a new known issue in our internal team and they have declared the part of the fix will be available in product environment before middle April. Currently, please retrigger the refresh as the workaround.

Issue description:

Power BI customers using Snowflake data source may see following refreshes issues intermittently. • Long refresh times and failures with an Access Violation error in the driver • ODBC: ERROR [22007] [Microsoft][Support] (40490) Invalid date, time or timestamp

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly. If I misunderstand your needs or you still have problems on it, please feel free to let me know. Thanks a lot!

Best Regards,

Community Support Team _ Caiyun

[nathangriffiths]

Hi, it's now 26th May and we have not received any update on this, was a fix deployed?

[nathangriffiths]

Hi, it's now 20th April - is there any further update on this issue? Was the fix deployed?