Power BI updated the Snowflake ODBC drive to 3.2.2. in the service & now dataflows will not refresh

[1deanchereden]

Issue happened around 6/7am GMT where all snowflake connected dataflow started to fail and have been failing all day.  The error within the error log is:

"The 'Driver' property with value '{Simba Snowflake ODBC Driver New}' doesn't correspond to an installed ODBC driver"

After connecting the Power BI support I was told it was not an issue on their end and would need to speak to Snowflake.

Snowflake came back and said:

Checking the query history, I see the ODBC driver has been upgraded from 2.24.6 to 3.2.2 in PowerBI. Please note that this error is triggered by the ODBC driver managed by Microsoft PBI; therefore, Snowflake has little to no control over it.

I checked the query history and saw the client driver changed from 2.24.6 to 3.2.2 on the next refresh at 7am.

The issue is purely when refreshing as you can connect and see data in the dataflow and save it.

I've not seen anything recent about this online and the only mention of a similar issue is on a desktop version but I cannot believe this is only an issue for us so is anyone else having any issues?

I'm currently waiting for Microsoft to fix the issue as the ticket is back with them and their engineers are looking into it.

[1deanchereden · Accepted solution]

They seem to have fixed the issue now.  UK South was affected but no confirmation of what the issue was.

[aw169--]

I've got a support case open.

Have seen that the Snowflake Connector documentation was updated on 15th Jan, and have tried adding in the Implementation="2.0" to the M code connection part, but get the below error:

Expression.Error: The Adbc.DataSource function is not available in this environment

Details

Reason = Expression.Error

This should have been communicated properly by MSFT, it's so poor.

[1deanchereden]

I tried the same so I think this is for Gen 2 because if you change to Implementation="1.0" it loads data and saves but still gives the error about the driver but does last longer while refreshing before it fails.

[1deanchereden]

I would say to anyone with this issue to raise a ticket as soon as to speed Microsoft up.

https://admin.powerplatform.microsoft.com/newsupportticket/powerbi

[aw169--]

We have exactly the same issue, I was scrambling around to find something similar.

[1deanchereden]

I had my 2nd call with Microsoft late yesterday and another one just now to collect logs and screenshots. 

The only update is that we found the connector works in Gen 2 Dataflows, so it's Gen 1 dataflows that are the issue.

We use PPU licence so we had to use the Fabric free trial to test using Gen 2 dataflows.

I did try Gen 1 connected to SF within the fabric workspace to see if that worked but I got the same error.

I know Microsoft want people to move to fabric but you'd think they would test legacy connectors with updates when most of their clients would still be using Gen 1 dataflows because anyone who moved to fabric capacity only did because premium capacity was moved to it.

They really need to sort out their support of their original offering because no one using it wants to use fabric.