Forum Discussion

CarlosPBIVision's avatar
CarlosPBIVision
New Member
3 years ago
Solved

Power BI Connection Error with BigQuery

Hi,

 

We have some reports that we expected to get refreshed on a daily basis on Power BI Service (all tables are connected to our data warehouse on BigQuery). But this morning, for some reason, we got this error for all of them:

ERROR [HY000] [Microsoft][BigQuery] (131) Unable to authenticate with Google BigQuery Storage API. Check your account permissions.

We already tried this thoroughly but it didn't work out: https://community.powerbi.com/t5/Service/BIgQuery-Account-Permissions/m-p/1390692

 

Does anybody know we could solve this? It seems it is happenning almost exclusively for the most heavy tables in terms of rows and size

 

Thanks

  • Hi Selina, we already solved the problem by contacting PBI Support directly.

     

    To help future users: the solution was to go to the "Source" step of every PowerQuery table that we're ingesting from BigQuery, and substituting

    Source = GoogleBigQuery.Database()

     With

    Source = GoogleBigQuery.Database([BillingProject = "Insert-Your-Project-ID-Here"])

     

    That's it. The catch is that it must be for ALL tables coming from BQ, not only the large, problematic ones.

     

    Best,

     

4 Replies

  • Hi Selina, we already solved the problem by contacting PBI Support directly.

     

    To help future users: the solution was to go to the "Source" step of every PowerQuery table that we're ingesting from BigQuery, and substituting

    Source = GoogleBigQuery.Database()

     With

    Source = GoogleBigQuery.Database([BillingProject = "Insert-Your-Project-ID-Here"])

     

    That's it. The catch is that it must be for ALL tables coming from BQ, not only the large, problematic ones.

     

    Best,

     

    • Anonymous's avatar
      Anonymous
      Not applicable

      Hi CarlosPBIVision ,

       

      I'm glad you solved the problem. You can mark the reply as a solution to better facilitate other members to find it.

       

      Best regards,

      Community Support Team Selina zhu

      If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

    • ep2's avatar
      ep2
      Regular Visitor

      This solution worked for me, (thanks!), however I am struggling to understand why this is suddenly neccessary on tables which worked fine previously? Do you have any insight on that?

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi CarlosPBIVision ,

     

    Have you had this error before? Have you tried to re-upload the report to the service for refreshing?

     

    I reviewed the document you shared and indeed, there were errors consistent with yours and many members participated in it to share their views. but there is no solution to your problem, is there?

     

    Best regards,

    Community Support Team Selina zhu

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly