Forum Discussion
power bi dataflows connected to google bigquery suddenly stop working
I've been using datalfows (gen 1) in PBI service using the Google BigQuery connector successfully for just over a year now, and it's be running very smoothly until this week; when my daily refreshes started failing and giving me this message:
"ERROR [HY000] [Microsoft][BigQuery] (131) Unable to authenticate with Google BigQuery Storage API. Check your account permissions"
My permissions within google seem correct in accordance with various posts i've seen about having the read sessions permissions, so i don't actually thing the message is shedding light on the issue (for info my flows have also always had useStorageApi = false).
When testing for solutions I have noticed that dataflows work for smaller tables load (e.g a 500 row table) but up to some limit they fail. I limited one of table to 100,000 rows and it failed, not exactly sure what the threshold is.
This issue is strictly just for dataflows, I have a semantic model connected to google and it loads a 2 million row table just fine on it's scheduled refresh.
When I look in google big query console I see the jobs running as normal (i.e the usual power bi dataflow related jobs), it's just not successful refreshes on the PBI side. It's very frustating because it was running so well before and nothing about the data has changed other.
Please let me know if anyone has come up against this issue and have managed to fix!
Cheers
Setting these parameters has seemed to have fixed the issue:
GoogleBigQuery.Database([BillingProject = null, UseStorageApi = null, ConnectionTimeout = null, CommandTimeout = null, ProjectId = null])
I think it was related to timing out. Perhaps there has been a dataflow gen 1 update and it has caused this new behaviour
3 Replies
- PagnumBIFrequent Visitor
Setting these parameters has seemed to have fixed the issue:
GoogleBigQuery.Database([BillingProject = null, UseStorageApi = null, ConnectionTimeout = null, CommandTimeout = null, ProjectId = null])
I think it was related to timing out. Perhaps there has been a dataflow gen 1 update and it has caused this new behaviour
- AnonymousNot applicable
- PagnumBIFrequent Visitor
hi Wearsky, thanks for your suggestion. I've just been trying this but unfortunately the dataflows still fail.