March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
Hi everyone!
I have four datasets in Power BI which connects to Big Query. They connect to same tables, but some of them have more tables, some less, due to manage access rights.
And for one of them sometimes, have noticed that usually it happens on Tuesdays, I receive error:
DataSource.Error: <pii>ODBC: ERROR [HY000] [Microsoft][BigQuery] (100) Error interacting with REST API: Timeout was reached</pii>. DataSourceKind = <pii>GoogleBigQuery</pii>. DataSourcePath = <pii>GoogleBigQuery</pii>. OdbcErrors = <pii>#table({"SQLState", "NativeError", "Message"}, {})</pii>. ;ODBC: ERROR [HY000] [Microsoft][BigQuery] (100) Error interacting with REST API: Timeout was reached. The exception was raised by the IDbCommand interface.
Or this one:
DataSource.Error: <pii>ODBC: ERROR [HY000] [Microsoft][DriverOAuthSupport] (8701) Error interacting with REST API: Timeout was reached ERROR [HY000] [Microsoft][DriverOAuthSupport] (8701) Error interacting with REST API: Timeout was reached</pii>. DataSourceKind = <pii>GoogleBigQuery</pii>. DataSourcePath = <pii>GoogleBigQuery</pii>. OdbcErrors = <pii>#table({"SQLState", "NativeError", "Message"}, {})</pii>. ;ODBC: ERROR [HY000] [Microsoft][DriverOAuthSupport] (8701) Error interacting with REST API: Timeout was reached ERROR [HY000] [Microsoft][DriverOAuthSupport] (8701) Error interacting with REST API: Timeout was reached. The exception was raised by the IDbCommand interface.
I have reserve refresh and mostly the second one refreshes successfully. But on Tuesday it takes four time or even more to refresh the dataset. I cannot understand why this happens and what can I do, as other three refreshes with no errors, completely.
All connection strings look like:
Source = GoogleBigQuery.Database([BillingProject="project_name", UseStorageApi=false, ConnectionTimeout=#duration(0,0,180,0), CommandTimeout=#duration(0,0,180,0)]),
#"project_name" = Source{[Name="project_name"]}[Data],
schema_name_Schema = #"project_name"{[Name="schema_name",Kind="Schema"]}[Data],
view_name_View = schema_name_Schema{[Name="view_name",Kind="View"]}[Data]
I'm stack and don't know what to do. Maybe someone had this issue and can help.
Many thanks in advance.
Solved! Go to Solution.
Hi @Anonymous
For this type of error, you can refer to the solution in last post, see
https://community.powerbi.com/t5/Service/REST-api-to-google-big-query-crashes/m-p/800366
if you still have problem, please let me know.
Best Regards,
Community Support Team _ Tang
If this post helps, please consider Accept it as the solution✔️ to help the other members find it more quickly.
Hi @Anonymous
For this type of error, you can refer to the solution in last post, see
https://community.powerbi.com/t5/Service/REST-api-to-google-big-query-crashes/m-p/800366
if you still have problem, please let me know.
Best Regards,
Community Support Team _ Tang
If this post helps, please consider Accept it as the solution✔️ to help the other members find it more quickly.
Hi! Thank you for the answer.
There is no refresh parallelism, as I made refreshes that way, so each has it own time.
About plans timeout, I'm not sure about plan we have (admin team should upgrade to P2, but it's a big problem to communicate with them). But even when we had P1, dataset could be refreshing up to 6 hours.
And now, as I couldn't refresh dataset, I made it manually in desktop and republished, however now I have bigger problem. It timeout in 20 minutes. Last several times it took approximately 2 hours, to make full refresh. Could be something changed? Timeout limit?
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
22 | |
19 | |
11 | |
11 | |
7 |
User | Count |
---|---|
45 | |
36 | |
24 | |
10 | |
10 |