Forum Discussion
Data connection issues with Google Big query
Hello everybody,
Currently I am having issue connecting to a data source from Google Bigquery, but it is throwing up an Error
DataSource.Error: ADBC: UnknownError [] Cannot execute <ExecuteQueryInternalAsync>b__2 after 5 tries
Details:
DataSourceKind=GoogleBigQuery
DataSourcePath=GoogleBigQuery
AdbcErrors=[Table]
Has anybody encountered this error before? I have checked that I am using the correct service account gmail and JSON credentials when authenticating.
We found that problem. We haven't found the solution to the problem while using the new ADBC connector. If ADBC is disabled it uses ODBC and works again. Can enable/disable here: To access this feature in Power BI Desktop, navigate to Options and settings (under the File tab) > Options > Preview features, and then select the checkbox to enable the Use new Google BigQuery connector implementation option. Once the option is on, all the newly created connections automatically use the new connector implementation.
9 Replies
Hi naphob , hope you are doing great. May we know if your issue is solved or if you are still experiencing difficulties. Please share the details as it will help the community, especially others with similar issues.
Hi naphob
This error often comes from setup or permission mismatches. Try these:
-
Make sure BigQuery API is enabled and your service account has BigQuery Data Viewer + Job User roles.
-
Use the correct JSON key in Power BI and set the Billing Project ID and Location (US/EU).
-
Clear cached credentials in Power BI and reconnect.
-
Test with a simple query like SELECT 1 to confirm access.
-
Update Power BI Desktop or the BigQuery driver if it’s outdated.
-
Ensure service account has BigQuery Data Viewer + Job User roles.
Update to latest Power BI Desktop (connector bug fixes).
Check region of dataset matches connection.
Verify network/firewall allows bigquery.googleapis.com.
If still failing → use Simba ODBC driver instead of native connector.
We found that problem. We haven't found the solution to the problem while using the new ADBC connector. If ADBC is disabled it uses ODBC and works again. Can enable/disable here: To access this feature in Power BI Desktop, navigate to Options and settings (under the File tab) > Options > Preview features, and then select the checkbox to enable the Use new Google BigQuery connector implementation option. Once the option is on, all the newly created connections automatically use the new connector implementation.
Hello agomez_binni Thank you for suggesting an alternative method, this method worked for me as I updated Power BI desktop version and disable this Preview Feature.
Hi naphob , thanks for the update, glad it worked. If you have any other queries, please feel free to create a new post in the community. We are always happy to help.
any solution for Dataflow? I found that I can only use existing Table/View from BigQuery but cannot use SQL Query in the new connector. Thanks!
Hi Suu , Thank you for reaching out to the Microsoft Community Forum.
In Power BI Dataflows (and Fabric Dataflows Gen2), the new Google BigQuery ADBC connector doesn’t support custom SQL queries, it only lets you pull from existing tables or views. That’s why you can’t paste a query directly like in Power BI Desktop with the older ODBC connector. The workaround is to create a view in BigQuery that contains your SQL logic, then point your Dataflow to that view. This way you get the same result while staying within the connector’s current limitations.
That is not the only issue for this solution. It is needed to enable the new connector but then you have to clean up the json file downloaded from big query. I banged my head on this problem for days. ChatGPT got me part of the way but this thread https://community.fabric.microsoft.com/t5/Service/Power-BI-Service-BigQuery-connector-failing-with/m-p/4819008 helped me wrap it up.
You have to do two things.You have to convert the json you download from Big Query into a single line as suggested in this article. That was what I was not doing yet. Then you have to remove all of the indenting space and remove the \n line break indicators in the private key.
I used Notepadd++ to do that stuff. Once I did that it finally took the darn thing! Hope that helps!
