The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Has anyone seen this error before, it has been preventing all new and existing reports from connecting to the data since 3/25? DataSource.Error: ODBC: ERROR [HY000] [Microsoft][BigQuery] (100) HTTP Error 404: notFound (Request couldn't be served.).
Details:
DataSourceKind=GoogleBigQuery
DataSourcePath=GoogleBigQuery
OdbcErrors=[Table]
We confirmed nothing has changed with our service account access and we can still access Google BigQuery and successfully complete queries in the Google interface but can't connect via Power BI.
Solved! Go to Solution.
Hi @kristenlooser ,
Please refer to the steps in this document.
Google BigQuery connector - Power Query | Microsoft Learn
Please note:
This error occurs when you refer to a resource (a dataset, a table, or a job) that doesn't exist, or when the location in the request does not match the location of the resource (for example, the location in which a job is running). This can also occur when using table decorators to refer to deleted tables that have recently been streamed to.
Try:
Fix the resource names, correctly specify the location, or wait at least 6 hours after streaming before querying a deleted table
Hope this helps!
Thank you @v-priyankata, adding the Billing Project ID to the advanced options of the queries seems to have resolved the issue. Not sure why something changed on 3/25 but at least we can move forward now.
Hi @kristenlooser ,
Please refer to the steps in this document.
Google BigQuery connector - Power Query | Microsoft Learn
Please note:
This error occurs when you refer to a resource (a dataset, a table, or a job) that doesn't exist, or when the location in the request does not match the location of the resource (for example, the location in which a job is running). This can also occur when using table decorators to refer to deleted tables that have recently been streamed to.
Try:
Fix the resource names, correctly specify the location, or wait at least 6 hours after streaming before querying a deleted table
Hope this helps!