I have created a virtual machine on Azure using Image SQL Server Data Center for SQL Server 2014, and created some SSAS cubes on that machine. I am able to access cubes from management studio. I want to access those cubes from Power Bi. I have installed Power Bi gateway on that machine, and connected cubes using live connect method. I further installed Power Bi Enterprise gateway to enable refresh of my cubes to Power BI cloud. Now when I am trying to connect to SSAS on Azure machine using PBI Gateway I am not able to connect, it gives me error "There are currently no logon servers available to service the logon request." On the other hand when I am trying to connect to SQL Server database engine on the same machine from PBE gateway, I am able to connect without any problem. The azure machine is not part of a domain yet, is this may be a reason why I am getting error connecting to SSAS instance from Power BI gateway.
I made this machine an active directory domain controller, and so this machine is now part of an active directory. Now I am able to connect SSAS instance on this machine to PBI Enterprise gateway, but my problem did not end here, I am still not able to refresh my dataset which I have sourced from the SSAS cube on the same machine. I am getting error "Data source access error. Please contact gateway administrator"
Further I added a new user to Active directory, with same name as I was having an account in Power BI. I further changed UPN of that user in Active directory to that of my Power BI User. Let say name of my domain was domain, and upn was domain.local, and new user I created in AD was NDubey#domain.local, I chnaged the UPN to NDubey#ABC.com, as this was my login name in Power BI. After that I was able to see data in my datasets populated from SSAS cubes.
Verify that the Network Interface for the VM is using the expected Network Security Group, and the Network Security Group has the correct Inbound and Outbound Security Rules for the ports used by the PBI Gateway.
Related
Our new data source for Power BI reports is Azure Synapse. Do we still need a gateway to be set up in this case? . I think this is the reason that we can’t refresh the data in Power BI.
Thanks!
I see after clicking on ‘edit credentials’. I tried both OAuth2 and username/password authentication and received the same error message. I think the gateway is missing to enable private endpoint as per error message .
Can you please share the error message.
Everything depends on the network configuration of synapse server.
In case if the server is not configured within any vnet, you can access synapse via power bi without any gateway as both are hosted on cloud.
In case if synapse is within vnet, you need to set up a gateway within a server hosted within the vnet
For my Pro Power BI Project, I need to consume external API calls through set of automated endpoint calls.
However these set of APIs are accessible only over Private VPN Network and require OpenVPN to access them.
Below is error snapshot in Power BI:
Would Data Dateway resolve above issue or would another alternative - middleware script be required?
First that screenshot you provided looks like it is from Power BI Desktop. The on-premises data gateway is unrelated to Power BI Desktop refreshes. So make sure your laptop is connected to OpenVPN when you refresh in Power BI Desktop.
Once you are happy with the report you have built and want to publish it to the Power BI Service you will need to setup an on-premises data gateway so that the scheduled refreshes will be able to talk to your source APIs over OpenVPN. Typically you install the “standard mode” (see the link above for more details) and put it on a Virtual Machine or server which is always running (rather than a laptop which can be shut down at night during the scheduled refresh). But if you don’t need scheduled refresh during hours when your laptop is off, I suppose you could use “personal mode”. Personal mode isn’t recommended generally.
Make sure OpenVPN is connected on the server where the on-premises data gateway software is installed. If this VPN connection disconnects after a few hours then ask your IT team for a better way to get a Virtual Machine which is on the same network as the source API or on a network which has a site-to-site “always connected” type VPN connection.
You will need to install and configure the gateway software, create a data source with credentials for your source API, ensure your user account is a “User” on that gateway data source, then republish the report from Power BI Desktop so it will bind to the gateway data source and use it during refresh.
So I have this Azure Analysis Service where the data source of the cube points to an external (on prem) SQL Server database. For some reason it won't connect to it even when I have the proper firewall changes in place.
When processing the cube it complains that I need to install the on-premises data gateway.
So my question is: Is the on-premises data gateway mandatory for connecting to other sources outside Azure?
Per docs, all non-Azure data sources require the on-premises data gateway:
https://learn.microsoft.com/en-us/azure/analysis-services/analysis-services-datasource
As to why, it's unusual and not recommended that you would expose your on-premises SQL Server for direct connection from the internet.
I have a customer who intends to host SSAS VM in Azure. How will they best be able to authenticate against it without connecting to their own corporate AD?
Can one setup AD for them in the Cloud only for this Authentication?. SSAS requires Windows Authentication. Client doesn't want to setup any on Prem configurations due to security reasons.
I am trying to establish a connection to an azure SQL database from Power BI Desktop. I enter the server and database names as per the following screenshot:
I keep getting the following error:
Additionally, I am able to connect form the same Power BI Desktop to another azure SQL database on the same azure SQL server.
I checked for typos, for the azure firewall settings including my client IP and for "Allow access to Azure services" set to ON. The fact that one of the databases in the same server is connecting correctly make me consider if there is a limitation on Power BI desktop to one only database per azure SQL server.
I was finally able to establish the connection with the azure SQL server by replacing Server field above with: tcp:myServerName.database.windows.net,1433 and leaving the Database field empty.
This allowed me to connect to both databases in the server and didn't request credentials.
Somehow power pi desktop was not letting me create a new connection to another database under the same server. This has not been made clear in Power BI desktop documentation and examples.