Power BI desktop Snowflake ODBC driver connection problem

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.