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 🙂
So, quick update on this. I started getting this error on a large model of mine (using just a select * query against a large Snowflake table) this morning. Never had it before today.
Was the new ADBC driver with the fix already pushed to PBI Service? Because if I route the refresh through our on-prem PBI gateway it completes successfully without triggering this new error. And I assume that the ADBC driver being used in that scenario is a bit older than whatever PBI Service uses when I route the refresh for that model through a Shared Cloud Connection instead of our gateway.
I ask because I'm worried that an update to the ADBC driver in PBI Service today is what caused this issue in the first place, whereas it was indicated in this thread that the July 2026 PBI Service update for the ADBC driver was supposed to be the fix.
Hi NSnoap,
Thank you for reaching out to Microsoft Fabric Community.
This looks like the same snowflake driver issue. The connector is still moving from ODBC to ADBC in stages, that is why the on-prem gateway refresh works but fails on the shared cloud connection.
- For now, keep this model refreshing through the on-prem gateway since it already works or force the connection back to the ODBC driver instead of ADBC.
If required, please raise a Microsoft support ticket to confirm the rollout status for your tenant.
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
Follow below documentation for reference:
Thanks and regards,
Anjan Kumar Chippa