Forum Discussion
Snowflake ADBC connector error: Error: ADBC: [Snowflake] arrow/ipc:undefined
hi XCT I found this one and looks like this is a confirmed bug in the Snowflake ADBC driver, not a Power BI timeout or network config issue. Take a look and have a read.
SNOW-3449105: arrow/ipc: could not read message body · Issue #1781 · snowflakedb/gosnowflake
Good news is the fix was merged and released with gosnowflake v2.1.0 (released ~June 9, 2026). It adds a Reset() method to ArrowStreamBatch that lets the ADBC driver re-download a chunk after a mid-stream TCP failure without re-executing the entire query.
However, this fix still needs to be picked up by Microsoft to incorporate into Power BI Service/Desktop. Their target is around July release cutoff.
For workaround, You already found this which is ODBC fallback (Implementation 1.0). Note that ODBC uses a completely different data transfer mechanism that handles large result sets more reliably.
Definitely worth filing a support ticket referencing SNOW-3449105 (link above) to add more pressure so that the patched driver lands in Power BI Service quicker 🙂
Hi XCT,
Were there any changes to configuration on the snowflake side?
THe error message "An existing connection was forcibly closed by the remote host" tells me that Pwoer BI connected successfully, and then snowflake killed the connection.
Was any sort of IP whitelisting or anything of that nature configured?
Do you have other connections to snowflake that are still working?
