Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.

Reply
stefanjt
Frequent Visitor

Snowflake Connector - An existing connection was forcibly closed by the remote host

Hi, community. I need your help with something that I've been struggling with for a few weeks now.

 

When we try to load data from Snowflake (26 million rows) into PBI by using the Snowflake connector, we are getting an error, "An existing connection was forcibly closed by the remote host". Attached is the error message. error.png

We already tried various things to load that data from Snowflake (including deleting cache, installing the latest driver from Snowflake, increasing timeout times, using the legacy SF driver, etc.) to no avail. The error message appears consistently around after 5-6 million rows have been loaded. The queries in Snowflake appear as having succeeded, which most probably means that there is some communication issue between Snowflake and PBI. 

 

We reached out to Snowflake's support and they told us looking at the logs, it appears that the issue comes from the ADBC driver implementation that the September release of PBI is using. Using the legacy Snowlfake driver

stefanjt_0-1760338232151.png

 

still produces an error indicating that it's using ADBC.

 

1 ACCEPTED SOLUTION

Hi, community. I found the fix.
 
When you go to Options - Preview features - select Use legacy Snowflake connector implementation - restart PBI, this changes the connector for data sources that you add after this point.
stefanjt_0-1760365918252.png

 

To switch to the legacy connector for already added data sources, you need to go to Power Query and change the Implementation from 2.0 to 1.0 in the very first step:
stefanjt_2-1760366042029.png

This then uses the ODBC driver, which manages to load vast amounts of data (unlike ADBC).


 

View solution in original post

3 REPLIES 3
rajendraongole1
Super User
Super User

Hi  @stefanjt  -  can you try with downgrade the version,Revert to a version prior to the ADBC switch — for example:

Power BI Desktop August 2024 or July 2024 . You can download older builds from:

https://learn.microsoft.com/power-bi/fundamentals/desktop-latest-update-archive

This ensures the legacy ODBC Snowflake driver is used natively.

ODBC Driver | Snowflake Documentation

Power BI SSO to Snowflake | Snowflake Documentation

 

Hope this helps. 

@stefanjt





Did I answer your question? Mark my post as a solution!

Proud to be a Super User!





Hi, community. I found the fix.
 
When you go to Options - Preview features - select Use legacy Snowflake connector implementation - restart PBI, this changes the connector for data sources that you add after this point.
stefanjt_0-1760365918252.png

 

To switch to the legacy connector for already added data sources, you need to go to Power Query and change the Implementation from 2.0 to 1.0 in the very first step:
stefanjt_2-1760366042029.png

This then uses the ODBC driver, which manages to load vast amounts of data (unlike ADBC).


 

Thanks for the suggestion! I'm using PBI from Microsoft Store and exe installations are generally restricted as I'm using a company PC. Is it possible to resolve it some other way? I thought using the legacy driver (from Preview features) would be ODBC?

Helpful resources

Announcements
FabCon Global Hackathon Carousel

FabCon Global Hackathon

Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!

September Power BI Update Carousel

Power BI Monthly Update - September 2025

Check out the September 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors
Top Kudoed Authors