Forum Discussion

reubwork's avatar
reubwork
Resolver I
1 year ago
Solved

Snowflake data source refresh errors following July 2025 release

In case anyone else finds this. I started getting weird errors refreshing a report in the past few days.   Data source error: The credentials provided for the Snowflake source are invalid. (Source...
Need Help
  • reubwork's avatar
    reubwork
    1 year ago

    This turned out to be user error. 

     

    We're switching from using Snowflake sql login and password, to using Snowflake service users with Programmable Access Tokens. 

    When creating a PAT, you're required to specify an explicit single Snowflake role. Then, if you try and use any other role in the power query ingest it'll fail. 

     

    So, user error. 

     

reubwork's avatar
reubwork
Resolver I
1 year ago

hi there,

 

I've had a lot of issues with the server side refresh of snowflake queries (not locally)... up until the July release which is a big improvement. 

 

If you're using SQL Logins and passwords... you need to get off that this year as Snowflake are disabling logins without MFA. 

 

So we've switched to using Programmable Access Tokens... https://docs.snowflake.com/en/user-guide/programmatic-access-tokens

The intermittent thing is strange and suggests some kind of data handling issue to me... I've not seen any network transport issues. (Is your power bi capacity in the same region as Snowflake?) 

You can force it to use the old connector with the Implementation option. default is the new version which is 2.0

 

// declare connection
snowflake_connection = Snowflake.Databases(
"sonovate.west-europe.azure.snowflakecomputing.com",
warehouse_name,
[Role = role_name, Implementation="1.0"]
),

 

amol_mahajan's avatar
amol_mahajan
New Member
1 year ago

Using [Implementation="2.0"] solved my issue. Thanks!
I had other data sources along with snowflake and only those reports were failing. After forcing this in power query the refresh are working fine.
Thanks!