Forum Discussion
DataSource.Error: ADBC: Dataset XXX was not found in location US
- 11 months ago
Hi Anonymous,
According to google's docs:To address this issue, specify the location of the dataset in the query or confirm that the dataset is available in the same location.
You might be able to explicitly specify the location of the dataset in the connection.
There's also been other community posts about similar errors indicating some regression in the service: https://community.fabric.microsoft.com/t5/Service/Power-BI-Service-BigQuery-connector-failing-with/td-p/4815200
There is an active known issue for Google BigQuery right now: https://support.fabric.microsoft.com/known-issues/?product=Power%2520BI&active=true&fixed=true&sort=published&issueId=1563
Can you try reverting to the old implementation of the connector and see if that works?
In Power BI Desktop go to File -> Options and settings -> Options -> Preview features and turn off “Use new Google BigQuery connector implementation,” then restart Desktop and reconnect. If your M query shows GoogleBigQuery.Database([Implementation="2.0"]), remove that flag. https://learn.microsoft.com/en-us/power-query/connectors/google-bigquery
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
- Anonymous11 months ago
Hi tayloramy ,
I manage to solve this by:
- Following your suggestion to reverting to old implementation (File -> Options and settings -> Options -> Preview features and turn off “Use new Google BigQuery connector implementation,” then restart Desktop and reconnect. If your M query shows GoogleBigQuery.Database([Implementation="2.0"]), remove that flag)
- Setting the Billing Project Name. To get the billing project name, I go to https://console.cloud.google.com/iam-admin/settings , and take the Project ID specified there
Thanks!
Hi Anonymous,
See this similar post: https://community.fabric.microsoft.com/t5/Power-Query/DataSource-Error-ADBC-UnknownError-while-running-a-query-with/m-p/4806424
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, please mark this as the solution.
Hi tayloramy ,
I have went through the post, and see one of the step mentioned by one of the replier:
When connecting, set the Billing Project ID and verify that your datasets are in the same region (US/EU).
But my dataset is in region asia-southeast1. Is that the cause (and again, it work last week)
All my datasets are in region asia-southeast1. Can that be the reason? But it work before ...