Forum Discussion
Error when loading DirectQuery PBIX file: Datasource has no credentials, unable to Patch the gateway
At the moment I post, it shall work. It seems a period outage and right now it works. I get the positive reponse from the ones who had the same error in this link.
Hi Eric_Zhang,
Thanks for your response! I tried this but instead of a NotFound exception I received a BadRequest.
However I'm able to update my credentials with:
await client.Datasets.SetAllConnectionsAsync(workspaceCollectionName, workspaceId, datasetId, connectionParameters);
Here is a screenshot of the output
Finally found the issue! When I used PowerBI-CLI the problem became a bit clearer. Apparently I needed to "Allow access to Azure services" in the relevant SQL database. After that I could finally Patch the Gateway and now I can see data in my report.
We definitely need more/the same feedback in the PowerBI API SDK!
This was my error (the IP Address is an Azure IP Address):
[ powerbi ] {"error":{"code":"DM_GWPipeline_Gateway_DataSourceAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_DataSourceAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2146232060"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Cannot open server 'engiep-dev-weeu-sql' requested by the login. Client with IP address 'xx.xx.xx.213' is not allowed to access the server. To enable access, use the Windows Azure Management Portal or run sp_set_firewall_rule on the master database to create a firewall rule for this IP address or address range. It may take up to five minutes for this change to take effect."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2146232060"}},{"code":"DM_ErrorDetailNameCode_UnderlyingNativeErrorCode","detail":{"type":1,"value":"40615"}}]}}}
How do you find the up address of PowerBI Embedded in order to whitelist the up address? Is it guaranteed not to change? I was under the impression that azure to azure calls didn't need it address whitelisting.
You mean IP address right? The IP address is an Azure IP Address, apparently you can switch on "Allow access to Azure services" on the Azure SQL Database. Then all Azure Services will have access to the database, including the Gateway. This way you don't need to add the Gateway's IP Address to the list of allowed IP addresses
