Power BI desktop Snowflake ODBC driver connection problem

[BBouwman0820]

Hi,

We have been troubleshooting the connection between Power BI desktop and Snowflake for a while.
We use a proxy and are able to connect to Snowflake using the native connector with the Power BI desktop versions from march & may.
When we update Power BI desktop to the June, July or August version we are unable to connect with the error below:

After a long search we suspected the Simba Snowflake ODBC Driver to cause the error. 
We tried replacing the whole folder /Simba Snowflake ODBC Driver and Simba Snowflake ODBC Driver.ini file with the identical files from the the March version of Power BI desktop. After entering the credentials, the connection is established: the connector works.
I do not know if this file is the culprit but,
Version of SnowflakeODBC_sb64.dll 3.2.2.1005 does not work 
Version of SnowflakeODBC_sb64.dll 2.24.6.1017 does work

However, it is not a feasible solution to distribute Power BI Desktop like this in our organisation. 
I would kindly request for a fix 

[misterm_secure]

We have the same Problems with the november 2024 Version. Is there an explanation why this still occurs?

Is this some Proxy Configuration Problem?

[Anonymous]

Thanks for the reply from rajendraongole1.

Hi @BBouwman0820 , 

May I ask if you have gotten this issue resolved? If it is solved, please mark the helpful reply or share your solution and accept it as solution, it will be helpful for other members of the community who have similar problems as yours to solve it faster . Thank you very much for your kind cooperation!

Best Regards,
Zhu

[nickgcraw]

Had this same issue last year when I updated to the June 24 version but got solved with the October 24 version.

Now I am having the same issue after updating to the August 25 version!! Such a pain. Can microsoft please correct this?

[BBouwman0820]

I don't think you are having the same issue as it has been patched.
what i would advise is to check the new version of the ADBC connector which is known to cause issues.
you can either add a no_proxy rule to your environment variables depending on your datasource
OR use the old odbc connector by removing the implementation=2.0 part in the advanced editor in your data transformation tab. 

[jmweekes]

I feel your pain, nickgcraw.

Thank you for this information, BBouwman0820.  You can also uncheck "Use new Snowflake connector implementation" in the Preview features in order to use the old ODBC connector.  We discovered that this was necessary in order to see database views when selecting "tables" in Power Query/Transform.

Do you have any more information on the specifics of the no_proxy rule?

[BBouwman0820]

hi @jmweekes,

Make sure you have updated to the last version of Power BI desktop, unchecking the preview feature is not in the last version anymore. If you do have an older version it might be a suitable option to uncheck it.

if you are using a newer version the 'views' problem should be fixed.
however, because you can not just disable the preview feature, you will have to delete the piece of text that determines if you are using the ODBC or ADBC version. this can be doen in the advanced editor in power query editor. 

if you still experience a problem then, you can add a new line to your environment variables but that could cause other issues. 
name; NO_PROXY
value; .amazonaws.com,.azure.com,.gcs.com,localhost,127.0.0.

[rajendraongole1]

Hi @BBouwman0820 -If the latest driver doesn't work, continue using the version 2.24.6.1017 temporarily as you troubleshoot.

Make sure you have set up the ODBC DSN correctly (Data Source Name) and that there are no conflicting environment variables that might interfere with Power BI's connection to Snowflake.You can review Snowflake's ODBC documentation to check if the latest drivers need specific setup changes for different Power BI versions

Ref documents:

Downloading the ODBC Driver | Snowflake Documentation

ODBC - Snowflake Developers

Revert to an older Power BI version: If you need to ensure stable connections, continue using the March or May versions of Power BI Desktop, where the connection works.

Previous monthly updates to Power BI Desktop and the Power BI service - Power BI | Microsoft Learn

Use Power BI’s feedback forum or Snowflake’s support to request a fix. There might be specific compatibility changes in newer versions that affect proxy configurations.

Hope the above information helps.

[jmweekes]

12/02/2024 update:  We worked with Microsoft to resolve this issue.  They provided a correctd version of the September 2024 version of Power BI Desktop that resolved the issue.  Sorry for the late update!

‎09-24-2024 03:54 PM

We are experiencing what I suspect is the same issue.  We also must use a proxy server when connecting to Snowflake from Power BI Desktop for queries over a relatively low size limit. 

•  March, April and May versions work without issue. 
•  Something changed in the June, July and August versions that is causing queries that require a proxy server to not use the proxy server.   Smaller queries, which do not require a proxy server (e.g. 50 rows), execute without issue.  Larger queries, which do require a proxy server (e.g., 700 rows), hang for about 45 minutes before returning the following error: 
  
  "[DataSource.Error] ERROR [HY000] [Microsoft][Snowflake] (25) Result download worker error: Worker error: [Microsoft][Snowflake] (25) Result download worker error: Arrow chunk download failed max retries done: Unformatted ErrorException: {Message="LocalizableDiagnostic(MessageKey="SFRestRequestFailed" ComponentID=102 Params=[***, CURLerror (curl_easy_perform() failed) - code=7 msg='Couldn't connect to server' osCode=10061 osMsg='Unknown error']".
  
  
• We confirmed that the queries are excuting successfully in Snowflake, in about 15 seconds, but the results are not returned to Power BI Desktop.
• The same reports/queries execute without error from the Power BI service.
• We worked with our network group and confirmed that after we upgraded to the June version nothing from Power BI Desktop was hitting the proxy server.  We also confirmed this with isolated tests.
• We ran diagnostics in Power BI.  Upon review, our support consultants concluded "End-of-Stream Exception (EndOfStreamException):  The log indicates that Power BI was unable to read beyond the end of a stream, causing it to terminate prematurely. This suggests that when the query result is being streamed back from Snowflake, Power BI either fails to fully download the data or receives incomplete data over the network."
• A fiddler trace indicated we started receiving 503 Service Unavailable errors the moment it tried to hit the proxy.  (NOTE: The same query in earlier versons of Power BI run successfully.)
• We are now working with Microsoft and waiting for them to analyze additonal Power BI diagnostics.  We were originally told an issue was introduced in the August version and they were working on a fix.  We never got a straight answer about June or July versions.  We were then provided a link to what we understood was an updated August version (2.135.7627.0); however, this version did not resolve the issue for us.

[BBouwman0820]

What we eventually did to solve it in september 2024:

Install the latest version of Power BI desktop (september 2024) remove the ODBC driver for Snowflake folder and replace with the complete folder from the june version of Power BI desktop. Eventually we filtered it down to the .ini file in that same folder. 
after replacing it everything worked. 
In contact with Microsoft we had confirmation that this problem would be solved in the October version. We have been updating the Power BI desktop app since without any problems.

[wht]

any news on this one? we are also going via proxy and issues from June release onwards.... I think we are getting different error..  but it seems related

[jmweekes]

I just updated my original post to indicate that we worked with Microsoft to resolve this issue.  They provided a correctd version of the September 2024 version of Power BI Desktop that resolved the issue.

We have had no problem since that time; we have not, however, upgraded past September 2024.  Have you configured the HTTP_PROXY and HTTPS_PROXY environment variables on your desktop machines?

[wht]

yes, we also configure HTTP_PROXY and HTTPS_PROXY to go via proxy