Forum Discussion
Issues connecting to On-Prem Tabular Model
All,
We have the "Power BI Analysis Services" up and running to our tabular models in Dev and Prod environment.
For some reason, I have three users that are not able to see the databases on-prem, using the 'Get-Data' option.
These users in question have PowerBI Pro accounts assigned to them, they have access to the server at the SSAS level as well as they are setup as local admin on those boxes where SSAS is running.
On the other hand, I am able to see and connect to data on-prem. Another account with Domain Admin rights is also able to connect.
What could be the issue?
Thanks in advance for the help.
16 Replies
- AnonymousNot applicable
igordossantos I would first suggest you take a look at the AS in depth documentation under "Where things can go wrong" to check some of the potential issues off your list.
https://powerbi.microsoft.com/en-us/documentation/powerbi-admin-analysis-services-connector-indepth/
in that post you'll also find a link to the troubleshooting page which has additional areas you should verify are set up correctly.
Let me know if you've gone thru all this already and still have an issue, otherwise there is a wealth of information to verify in these to posts that will most likely lead to a resolution.
- igordossantosHelper I
Eno,
I'm going through the links you sent right now.
Below are the informational and error messages that both of my users are seeing when they try to connect to the data on-prem:
Informational:
Creating new MSOLAP connection to AS server. Activity ID: 05c5f73d-1d5b-45e3-969f-3d2ac4302861
Activity ID: 05c5f73d-1d5b-45e3-969f-3d2ac4302861Informational:
Do impersonation for user domain\bi-asconnector-dev. Activity ID: 05c5f73d-1d5b-45e3-969f-3d2ac4302861
Activity ID: 05c5f73d-1d5b-45e3-969f-3d2ac4302861Error:
Open MSOLAP connection failed. The connection string is Provider=MSOLAP.5;Data Source=server|dev;transport compression=None;protocol format=XML;[email protected];sspropinitappname="PowerBI - Model Creation";timeout=180. Activity ID: 05c5f73d-1d5b-45e3-969f-3d2ac4302861
Activity ID: 05c5f73d-1d5b-45e3-969f-3d2ac4302861Do they need any specific rights at the AD level in order to impersonate a the login? Because remember that I and another domain admin user can get to the on-prem data.
- BjoernContinued Contributor
"they are setup as local admin on those boxes where SSAS is running."
When you say that: Are the 2 users in questions domain-users with local admin rights?
Usually it should work the way you described it.
- igordossantosHelper I
That is correct. They are domain users with local admin rights as well as they are part of the Server Administrators Role in SSAS. With the above, I'm still getting the error messages described on my post.
- AnonymousNot applicable
igordossantos Did everything check out in the links? Are these a subset of users, and there are other users that see things as they should?
- waltheedImpactful Individual
Hi,
SSAS Tabular only accepts Windows accounts, I mean accounts that exist in your local Active Directory (AD) domain.
Between logging to Power BI and accessing the data source, smart things happen.
Your local AD has to be synchronized with the Azure AD. So if you are trying this on your non-domain joined laptop, like I was, you can stop here...
The Power BI user is converted into an effective username which should be authorized as user on the SSAS Tabular Database. You can read that here.
Read from Usernames in Power BI and further
https://powerbi.microsoft.com/en-us/documentation/powerbi-gateway-enterprise-indepth/
Here is how to add User Principal Names, if you are allowed to
https://technet.microsoft.com/en-us/library/cc756018(v=ws.10).aspx
HTH,