How to solve an ODBC/OLE-DB error in power BI? - google-bigquery

I am having trouble in power bi and bigquery data connection.
I am getting the following error:
error retured -OLE-DB or ODBC error.
unable to authenticate with bigquery storage API.
check your account permission.

Related

Power BI refreshes failing if Synapse is updated by Dynamics - is this to be expected?

We have recently implemented Azure Synapse Workspace into our reporting landscape. The purpose of this Synapse Workspace is to store Dynamics data to be reported on by Power BI. We were using the Data Export Services mechanism to move data from Dynamics to Azure SQL Server and report from there but MS have deprecated DES and we now use Synapse as the substitute.
I have found, and this happens 50% of the time during working hours, that when I amend a Power BI report and the Power Query element re-evaluates itself, the re-evaluation seeks an update from the source - which is the Azure Synapse Workspace, the re-evaluation fails. I get an 'Operating system error code 12'. The error message is below with sensitive text scrubed.
Click this to show the error message received
Having Googled the error, it tells me a read (i.e. a Power BI refresh/re-evaluation) cannot take place against the Synapse Workspace if Synapse is updated being by Dynamics during the same time.
Is this correct? I can't believe MS would devise a DES replacement that cannot be read from if it is being updated from the source. The source (Dynamics) will be updated throughout the working day and so this would mean that no one can read from Synapse during the working day.
I'm wondering if further configuration is required within Synapse to allow reads.
If you can confirm what I'm facing is correct and/or advise me on how to remedy this it will be greatly appreciated.
Thanks.
I'm stumped on what to do. I have verified that when the Power BI report fails its refresh/re-evaluation the failing entity has actually been updated in the Synapse Workspace's CSV file. So the Google explanation seems to be correct.

Unable to connect Bigquery on PowerBi Application

When I connect to my BigQuery on PowerBI Desktop and try to pull data from one of the largest projects(having over 200 datasets with 30,000 date partitioned tables) under Bigquery, I get the error below.
Used features: Odbc.DataSource/Microsoft ODBC
Driver for Google BigQuery/2.4.0.1002/BigQuery
I tried clearing the cache in powerbi application folder(C:\Users\username\AppData\Local\Microsoft\Power BI Desktop\Cache) and it doesn’t work for me.
Could you please help me with this.

BI Engine mode is partial and the reason is due to internal errror

I created a reservation for BI Engine to make the reports on Google datastudio load faster.
I create a query and save it as view. I looked at the job information and it says "unable to support input table due to an internal error". What does it mean?
One of your tables is defined as external table (references a spreadsheet). Unfortunately BI Engine only supports tables that are stored in BigQuery natively today. We will work on improving the error message in this case. Supporting external tables was not on our roadmap so far, unfortunately.
To get full BI Engine acceleration, please load the data from spreadsheet into BigQuery.
See BI Engine overview here: https://cloud.google.com/bi-engine/docs/introduction

Azure Synapse Analytics Error when using saveAsTable from a DataFrame which is loaded from a SQL source

I'm following the guide (https://learn.microsoft.com/en-us/azure/synapse-analytics/get-started) for loading data from a SQL Pool and writing the DataFrame to a table in the metastore. However I'm getting an error:
Error : org.apache.hadoop.fs.azurebfs.contracts.exceptions.AbfsRestOperationException: Operation failed: "This request is not authorized to perform this operation using this permission.", 403, PUT, https://xxx.dfs.core.windows.net/tempdata/synapse/workspaces/xxx/sparkpools/SparkPool/sparkpoolinstances/8f3ec14a-1e59-4597-8fd9-42da0db65331?action=setAccessControl&timeout=90, AuthorizationPermissionMismatch, "This request is not authorized to perform this operation using this permission. RequestId:fe61799c-e01f-0003-119e-37fdb1000000 Time:2020-05-31T22:57:55.8271281Z"
I've replaced my resource names with xxx.
Other DataFrame saveAsTable operations work fine. From what I can see, the data is being read from the SQL Pool successfully and being staged as when I browse the data lake location specified in the error I can see the data.
/tempdata/synapse/workspaces/xxx/sparkpools/SparkPool/sparkpoolinstances/8f3ec14a-1e59-4597-8fd9-42da0db65331
The Synapse workspace managed identity has storage blob data contributor permissions and my own domain account has owner access.
Has anyone else had issues?
Thanks
Andy
Please assign yourself (account with which you're trying to run the script) a role of Storage Blob Data Contributor.
Below information is now showing up during the creation of Azure Synapse workspace.
It was a big struggle to figure this out during it's private preview.
More information related to securing synapse workspace can be found here.
Let me know if this worked.
Thank you.

Problem with Google BigQuery Rest API via Power BI

I have a problem scheduling refresh in the Power Bi service for the google Big Query database.
It used to work fine and since last Friday Power Bi cannot connect to gbq anymore.
I tried Microsoft Support but they send me to you.
This is the error I receive:
ODBC: ERROR [HY000] [Microsoft][DriverOAuthSupport] (8701) Error interacting with REST API: Couldn't connect to server ERROR [HY000] [Microsoft][DriverOAuthSupport] (8701) Error interacting with REST API: Couldn't connect to server Table: CS_Scorecard.
Cluster URI: WABI-WEST-EUROPE-B-PRIMARY-redirect.analysis.windows.net
Activity ID: 07d42767-95e3-4bbc-81e8-6953be164caa
Request ID: f1b4b205-4228-4f16-8d6d-e98b28eec5c7
Time: 2019-12-10 12:43:12Z
I tried creating a new model with 1 gbq link and that worked fine. But my existing model is failing right now.
Any ideas on how to resolve this?
According with Power BI support page this issue is known.
Seems that the issue may be caused by a lack of permissions for the user attempting to establish a connection.
You will need to check that the account being used has the appropriate permissions, in particular "bigquery.tables.list" permission needs to be assigned.
Check the BigQuery roles and permissions.
I suggest confirming that there are no custom IAM roles or roles type set up on the dataset(s) you are trying to connect to.
Verify that you are using the last version of Simba drivers for BigQuery.
Finally you can look the following Public Issue Tracker, where this issue was reported.
thank you for your answer.
The Power Bi user has the Data Viewer role and we haven't any custom role on this dataset.
About the driver, we are trying to refresh a dataflow on the PBI Server, not in Desktop, so I guess the driver is updated.
Thank you.