Power BI Service – BigQuery connector failing with ReadChunkWithRetries (Desktop works)

I found a workaround that resolved the issue for me.

In the query code, look for queries having the `[Implementation="2.0"]` parameter:

`= Value.NativeQuery(GoogleBigQuery.Database([Implementation="2.0"])`

and replace them with

`= Value.NativeQuery(GoogleBigQuery.Database()`

by deleting `[Implementation="2.0"]`

It seems that `[Implementation="2.0"]` is the newer version that has recently stopped working in Service refreshes, and the older implementation is still working fine.

Even though reverting to the older implementation or using the Simba ODBC driver with an explicitly set Billing Project ID does work as a temporary fix, this shouldn’t be the long-term solution. The [Implementation="2.0"] path and ADBC driver are clearly part of Power BI’s forward-looking architecture, and it's concerning that Service refreshes are failing while Desktop continues to work.

We really need Microsoft to investigate and resolve the regression in the new connector implementation. Stability in the Power BI Service is critical, especially for enterprise workflows relying on scheduled refreshes and DirectQuery.

Hoping this gets prioritised soon — thanks to everyone who’s shared workarounds!

Hi 

I was facing the exactly same issue, and solved by removing the parameter from the source connector

[Implementation="2.0"]

After removing this part, the model refresh worked normally.

The final connector information should look like this

= GoogleBigQuery.Database()

Discovered that this was being added since I had the preview feature active to use the new BigQuery connector.

Issue: Power BI Service fails with ReadChunkWithRetries error using BigQuery connector—Desktop works fine.
Cause: Likely a bug in the ADBC driver used by the Service connector (see Apache Arrow issue #3322).

Workarounds:
- Try ODBC with Simba driver.
- Set Billing Project ID explicitly.
- Use legacy connector if possible.

Status: No official fix yet from Microsoft—worth raising via support or community forums.

Hello i have experienced a similar error with the default selection of the location of the data in BQ , all my data is in EU and PowerBI now looks for it in US ,i haven´t found a way to change this behaviour .

By the moment i have appied the solution of powerbi_user191

In the query code, look for queries having the `[Implementation="2.0"]` parameter:

`= Value.NativeQuery(GoogleBigQuery.Database([Implementation="2.0"])`

and replace them with

`= Value.NativeQuery(GoogleBigQuery.Database()`

This is the error I have in PowerQuery (  ADBC framework seems to have some busg to solve already)  

DataSource.Error: ADBC: Cannot execute <ExecuteQueryInternalAsync>b__1 after 5 tries. Last exception: The service bigquery has thrown an exception. No HttpStatusCode was specified. Job analytics-ppc-ga4/US/job_605e8141_ff66_4e72_b771_a5cc6feef7b3 contained 2 error(s). First error message: Not found: Dataset analytics-ppc-ga4:reporting_page_path_level_funnel was not found in location US Detalles:     DataSourceKind=GoogleBigQuery     DataSourcePath=GoogleBigQuery     AdbcStatus=1     SQLState=     NativeError=0

Hi Anonymous ,
Thanks for reaching out to Microsoft Fabric Community Forum .
Try these Workarounds

Based on your testing with raw tables, views, and snapshots using DATE, STRING, INT64, FLOAT64, and different UseStorageApi settings, here are some solutions to address the ADBC driver issue:

Use ODBC with Simba Driver:

Install the Simba Google BigQuery ODBC driver from Google’s SDK.

Set up an ODBC connection in Power BI Service via a data gateway, making sure to include the Billing Project ID in the connection string to prevent routing issues.

This method bypasses the ADBC driver and is considered stable for both Import and DirectQuery modes. Test with a small dataset to ensure it works for your scenario.

Export Data to Intermediate Storage:

For Import mode, export BigQuery data to CSV or Parquet in Google Cloud Storage or Azure Blob Storage. Then, connect Power BI Service to these files using a suitable connector. This method avoids the streaming issue but is less ideal for DirectQuery.

Since your snapshot table testing was successful, this approach should work well for static data refreshes.

Check Authentication and Permissions:

Make sure the service account for Power BI Service has the bigquery.jobs.create and bigquery.tables.getData roles in BigQuery. Incorrect permissions can also cause streaming errors.

Re-authenticate the BigQuery connection in Power BI Service to eliminate token-related issues.

Escalate and Monitor:

Submit a support ticket through the Power BI admin portal, referencing the ADBC driver bug and related GitHub issue. Keep an eye on the Microsoft Fabric Community for updates from Microsoft support.

Replacing the Power Query code - Removing Implementation 2.0 worked for us as well.  But Does anyone have a link to a microsoft issues that we can follow to make sure the issue gets resolved?

I've also been experiencing this issue, with this error message:

Data source errorCannot execute <ReadChunkWithRetries>b__0 after 5 tries. The exception was raised by the IDbCommand interface. Table: test_table.

Everything works fine on Desktop, as was mentioned.

I have no ability to use a gateway, nor can I submit a ticket to official support.
I hope to raise more awareness to this issue: Microsoft, please fix this!

A potentially helpful note:
When updating an M / PowerQuery query's SQL code, I noticed `Implementation 2.0` is automatically inserted as a parameter.
After updating any BigQuery SQL, it's worthwhile to check if `Implementation 2.0` was inserted again: I didn't notice that at first and had some Service refreshes fail as a result.

I finally found some official documentation on this issue:

---

A recent fix was published for this issue and should be deployed in October 2025

---

The link has other relevant information regarding the issue:
https://learn.microsoft.com/en-us/power-query/connectors/google-bigquery#unable-to-refresh-partitioned-models-with-adbc