Forum Discussion

XCT's avatar
XCT
Icon for Resolver I rankResolver I
2 months ago
Solved

Snowflake ADBC connector error: Error: ADBC: [Snowflake] arrow/ipc:undefined

Hi everyone,   For 2 days, I've receive this error message with a daily refresh in Power BI Service for a semantic model:   DataSource.Error: ADBC: [Snowflake] arrow/ipc: could not read message b...
Need Help
  • rizalard0684's avatar
    rizalard0684
    2 months ago

    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 🙂

rizalard0684's avatar
rizalard0684
Icon for Resolver III rankResolver III
2 months ago

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 🙂

  • XCT's avatar
    XCT
    Icon for Resolver I rankResolver I
    2 months ago

     

    I'm glad to hear that this issue is known and not related to a network configuration problem.

     

    It looks like this is an issue with the "new ADBC" driver. Replacing ODBC with ADBC may introduce some problems.

     

    Based on your input, I have opened a support ticket referencing the link you mentioned. Let's wait and see how it progresses.

     

  • XCT's avatar
    XCT
    Icon for Resolver I rankResolver I
    2 months ago

    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!

    • NSnoap's avatar
      NSnoap
      Frequent Visitor
      1 month ago

      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.

      • XCT's avatar
        XCT
        Icon for Resolver I rankResolver I
        27 days ago

        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).

  • NSnoap's avatar
    NSnoap
    Frequent Visitor
    1 month ago

    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.