I tried to publish my report on dashboard. and I get this error
This data source cannot be accessed by data gateway.
I used direct query from my sql server. I downloaded and installed on-premise data gateway.
When I go to Manage Gateway in Power BI service. It says you do not have any gateways.
Not really sure as to what to do.
Please someone guide me.
When using Direct Query, you must configure the gateway's data sources under manage gateways
If you cannot see any gateways under manage gateways, then one of four scenarios has occurred.
You have not finished the install process for the On-Premise Data Gateway
You have not Signed into the OpDG ( locally where it was installed )
You used a different accounts when publishing the report and signing in to the OpDG
( Very outlandish ) You installed the OpDG somewhere that it just cannot see an outside network. Perhaps a bad region? This can be changed in the local config page for the OpDG
To Fix this:
Re-Install the OpDG
Sign-in locally to the OpDG using the same account you published with
Try changing the region. I don't think it's this.
Next:
Under manage gateways, once you can see the gateway, you need to add a source. The Source must Suit two conditions. It must have the FQDN of the server.database AND it must be the exact same connection string used in the local PBIx File you published.
Ex. If you Direct-Queried to MyDomain.ServerOne.ProductionDatabase, but in PowerBI Desktop, you just said Localhost:ProdData, you'll have an issue. Make sure both the PBIx and the DataSource under your gateway online both have the FQDN.
Then You should be able to assign a gateway under the dataset settings ( Dataset -> Schedule refresh -> Choose Data Gateway )
Good Luck!
Related
When using the Google Cloud SQL instance, SSL can be enabled using the Server Certificate server-ca.pem downloaded from the Google Cloud SQL instance's Connections section. The Server Certificate seems to be only for a single instance. If I have multiple instances I will need to download and use multiple Server Certificates.
Is there a way to upload or customize the Server Certificate of the Google Cloud SQL instances that I am using? My goal is to use a single Root CA Certificate that can connect to all the Google Cloud SQL instances that I have. I read through the Google documentation and still not able to clearly understand whether it is possible. Appreciate any input from the community.
Example, for Amazon RDS, it supports a root certificate that works for all AWS Regions. I would like to understand whether there is something similar Google Cloud SQL is using.
Currently this is not possible. You can only manage client certificates as you mentioned. I found this Feature Request(FR) in the Public Issue Tracker. I would recommend you to "star" it to ensure that you receive updates about it. You can also adjust notification settings by clicking the gear icon in the top right corner and selecting settings.
The FR are evaluated by the number of users being affected by that. The more stars it have, the more possibilities to be developed it has.
In the end I don't think that having all the Instances with the same Certificate should be the best path to follow. I understand that this could help to reduce the amount of sensitive data managed, but in the end you "would never put all its eggs into one basket". This could be risky.
I get automated reports from aws server to my mail via a link. the aws link is similar to this (http://s3.ap-southeast-1.amazonaws.com/analytics/Company/Stock/MS_2020-08-03T02:43-9ebb780c.xlsx) - data might be deleted now.
Is there a way where i can automatically load the excel file from this report on to google sheet
Also, i dont have access to S3 server. its maintained by a different firm and we get only auto reports.
Context
I need to start sharing Power BI reports with other users (all users are Power BI Pro licenses).
Reports will be in live connection with an Analysis Services and my original data source are on-premise, therefore, I need to install a gateway to transfer data into the cloud.
Question
We already have a capable server for installing the gateway, therefore, my questions are:
Is it wise to install a Gateway VM on that server even though the server is used for other applications?
I don't have access to Power BI Admin Portal and it is tricky to get access to it since we are a very big company all over the world. Can I use an on premises data gateway without a Power BI Admin account? (While installing gateway just adding my account as admin)
I have a Power BI workbook that I have created in Desktop. It sources from a SQL Server database. I can access this database with account x. My Azure tenant admin has created a data source for this database in our gateway (within the Power BI service), and I have access to this gateway. The admin supplied account y in connecting to this data source. How does this work when I go to refresh the dataset that this workbook creates when I publish it to the service? That is, when I schedule a refresh on the dataset, will it dial into the SQL Server database using account y provided in the data source definition (virtually ignoring / dropping account x's credentials)?
Yep. That's exactly how it works. The automated refresh will use account 'Y.'
Data sources that have been deployed to some hosted location will almost always disregard the credentials used to create the dataset and instead use credentials that are specifically supplied for the refresh. These 'service' accounts will typically have different rules about password resets, have the lowest appropriate levels of access, and be under the prevue of system administrators rather than report authors. Its a very standard practice. It protects against misuse, error, loss of accounts, and segregates actual user activity from automated behaviors in the logs.
However, it is a little odd to me that your admin 'created the datasource' -- is that correct? Or did the admin just wire up the gateway to the datasource that was deployed when you published?
If you want to use a datasource that is already published, then you need to connect to that datasource from PowerBI desktop. Otherwise you'll be pushing out something new that has nothing to do with the resources that your admin created.
I have a PowerBI instance and a Postgres database on Heroku. In my search the PostgreSQL connectors for PowerBI all seem to be for desktop:
https://powerbi.microsoft.com/en-us/integrations/postgresql/
https://powerbi.microsoft.com/en-us/documentation/powerbi-desktop-data-sources/
Has anyone found a connector for the cloud PowerBI solution?
Thanks!
The data source "connectors" for Desktop and the service "connectors" for the cloud are different things.
If you build a report in Power BI Desktop that connects to a PostgreSQL database data source, you can publish that report to PowerBI.com (the cloud) and configure a gateway to allow scheduled refreshes directly from the cloud (i.e. once configured, you can pull data from your PostgreSQL database via the gateway into the report in the cloud on a schedule). It sounds like this is what you were looking to do.
More information about the on-premises gateway, including the list that shows that PostgreSQL can be used via the gateway for a scheduled refresh: https://powerbi.microsoft.com/en-us/documentation/powerbi-gateway-onprem/#list-of-available-data-source-types
You cannot, however, start building a blank report in the cloud and connect to an on-premises PostgreSQL database. When you start out from the cloud, you can only connect to a more limited set of cloud-based data sources (Azure and SSAS). In general, you almost always want to start building your Power BI report in Power BI Desktop and then publish it to the cloud.
The service connectors in Power BI are something entirely different. They provide a quick way to connect to other cloud-based services you may subscribe to and bring in your personal data for reporting. E.g. if you use Salesforce, the Power BI connector will connect directly to Salesforce for you. This is different to connecting to your own database directly. It's not your database you're connecting to, but your data that belongs to a 3rd party service that's already in the cloud. More information here: https://powerbi.microsoft.com/en-us/documentation/powerbi-content-packs-services/
I hope this helps clarify things.