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 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 rizalard0684,
Following my support ticket, Microsoft has confirmed that the fix will be deployed in the July 2026 release of Power BI Desktop and Power BI Service. We must be patient!
Thx for your support!
Do we know when the July 2026 release for PBI Service is supposed to go out? It's 7/24 right now, and I just started getting this error for the first time on one of our most important semantic models that needs to refresh daily.
Hi,
Since the latest PBI service Update, it works with the semantic model I've mentionned in my first message of this topic. Since August, all workspaces switched to ADBC mode by default (except if you disabled it in your tenant settings).