Forum Discussion
Gateways and SSAS connectors
As I understand it, this (https://powerbi.microsoft.com/en-us/blog/announcing-general-availability-of-power-bi-gateway-for-enterprise-deployment/) means that it is now possible to create live connection to SSAS OLAp on prem data sources.
I am a bit confused about where to istall the ssas connector and the gateway.
I have installed the gateway on my client (since I am not sure where to put it and since it it not recommended to put on the same server as the SSAS connector).
I have one server that has one SSAS olap and one SSAS tabular instance.
I have installed an SSAS connector for the SSAS tabular instance locally on that server.
I am unable to install another SSAS connector on the same server.
Can someone please guide me on how to set up gateways (I am also unsure wheter to use personal or enterprise) and ssas connectors?
I want to publish power BI reports for both tabular and olap
5 Replies
- AnonymousNot applicable
You do not have to install nothing more than the enterprise gateway on your server. Then go to https://app.powerbi.com/groups/me/gateways/, verify that your gateway is connected and configure two new datasources, one for the tabular and one for the multidimensional.
- Axdata_LarsFrequent Visitor
Hi,
you should install the Enterprise gateway on the SSAS server for better performance and for 24/7 access.
Once you have installed the gateway,- you define the different on-premise datasources in the PowerBI service.
- jockefeAdvocate IV
Ok so "General availability" means that I dont need the ssas connectors anymore?
- AnonymousNot applicable
jockefe Well, technically GA means: the point where all necessary commercialization activities have been completed and the software has been made available to the general market either via the web or physical media
It's already been announced that there will be new features added in the future.
There is no harm in installing the Enterprise Gateway alongside the SSAS connector - the EG will silently assume all the SSAS connector work, and you can remove it at a later date.
- jockefeAdvocate IV
Hi all,
thanks for the replies.
After a couple of weeks of troubleshooting I finally found a solution to the problem with the SSAS connector
It worked efter IT added the SSAS service account to the Windows Authorization Access Group
It was a matter of unsufficient access in the active directory
Seems strange to me though that I could not find anything on google regarding this.