Forum Discussion
Can't connect to SQL Server 2016 SSAS Tabular Model on local network server from Power BI Desktop
Hello,
I've got a SQL Server 2016 SSAS Tabular Model instance up and running on a customer's local network server. I VPN into the customers network to access their network and the server with the SSAS instance.
I'm trying to connect to that SSAS Model from my local desktop PC (Windows 10) using Power BI Desktop (just downloaded the most recent version). I have not been successful so far.
(Note that I can successfully connect to this Tabular Model from Excel, from this same PC, using Power Pivot.)
If I try to connect to the server using Get Data/Analysis Services, enter the server name and select "Connect Live" and click OK, I get the message "We could not connect to the Analysis Services server because the connection times out or the server name is incorrect."
If I try to connect using the Import Option and enter my Windows Credentials (AD credentials for the customer's network - same as when connecting via Excel) I receive the message "The user was not authorized".
I've seen a number of requests about this issue, but no clear answers. If this can be done and someone has a clear step-by-step procedure on how to do this, I'd sure like to see it.
Thanks for any help anyone can provide!
DWA
Have you tried typing in the Database (cube) name? The field shows as optional, but I have one instance where, if I leave it blank, it won't find any cubes, but if I fill it in, it works just fine.
Thank you leonardmurphy! That did the trick for me.
So in summary here are the two things I needed to do.
1. Run PowerBI Desktop from the command line under the context of the remote user.
2. Enter the database (cube) name (even though it says it's optional)
Thanks to all who helped with this!
Douga
12 Replies
Hi Douga,
I cannot reproduce you issue when connecting to remote SQL Server 2016 SSAS Tabular Model from the latest version of Power BI Desktop which is installed on my local desktop PC(Windows 10). In my scenario, the machine running SQL Server 2016 and the PC running Power BI Desktop are in same domain.
In your scenario, it seems that SQL Server 2016 and Power BI Desktop don’t exist in a same domain, in this case, I suspect that SQL Server 2016 cannot recognize your Windows Credentials. You can start SQL Server Profiler of SQL Server 2016 SSAS Tabular, then connect to SSAS from Power BI Desktop and capture details about the login process.
Besides, use runas /netonly command as follows to connect to SSAS from Power BI Desktop and check if it is successful.
1. Open command prompt and run the following command, enter the password of domain user when prompted.runas /netonly /user: Domain\username "C:\Program Files\Microsoft Power BI Desktop\bin\PBIDesktop.exe"
2. Create a saved windows credential for the SQL Server you want to connect to.
For more details, please check the following similar blogs.
Connect to SQL Servers in another domain using Windows Authentication
Pretend You’re On The Domain With Runas /NetOnly
Thanks,
Lydia ZhangThank you for the advice! There was one small change I had to make to your command line, but I'm now able to connect, but with the new issue below. The command line I used was:
runas /netonly /user:userdomain\username "C:\Program Files\Microsoft Power BI Desktop\bin\PBIDesktop.exe"However... I now have a different issue that I don't see when running to a SQL Server 2016 instance running locally on my PC.
It only successfully connects now when I choose the "Import" option. When I choose the "Connect Live" option I receive the following error message:
"Sorry the server you are trying to connect to doesn't have any models."
Any idea why it won't see the models?
Just to try and troubleshoot, I installed Power BI Desktop directly on the SSAS server, and I see this same behavior. Any idea why this is the behavior on the server (Windows Server 2012)"
Again, thanks for all your help!Doug A.
Hi Douga,
In Power BI Desktop, go to File -> Options and Settings -> Data Source Settings -> Global permissions-> find your SSAS data source->Clear permissions, then connect to SSAS using live option and check if it is successful.
Thanks,
Lydia Zhang
Hello,
I've got a SQL Server 2016 SSAS Tabular Model instance up and running on a customer's local network server. I VPN into the customers network to access their network and the SQL server with the SSAS instance.
I'm trying to connect to that SSAS Model from my local desktop PC (Windows 10) using Power BI Desktop (just downloaded the most recent version). I have not been successful so far.
(Note that I can successfully connect to this Tabular Model from Excel, from this same PC, using Power Pivot.)
If I try to connect to the server using Get Data/Analysis Services, enter the server name and select "Connect Live" and click OK, I get the message "We could not connect to the Analysis Services server because the connection times out or the server name is incorrect."
If I try to connect using the Import Option and enter my Windows Credentials (AD credentials for the customer's network - same as when connecting via Excel) I receive the message "The user was not authorized".
I've seen a number of requests about this issue, but no clear answers. If this can be done and someone has a clear step-by-step procedure or reference on how to do this, I'd sure like to see it.
Thanks for any help anyone can provide!
Hi all,
Seeking urgent help!
I am facing simillar problem but in my case, I am trying to connect Power BI desktop(on my laptop) to SSAS tabular(On -premise server) within my office network. I am getting follwing error
Details: "AnalysisServices: A connection cannot be made. Ensure that the server is running."
Whereas, I can connect to SQL Database on same server using SSMS. Can you Please advice
Q1, Can I connect Power BI desktop(my laptop) to SSAS tabular server(On-Premise server) using my office network?
Q2, As SSAS uses windows authentication, do I need to create any hybrid authentication method ?
Please advice
mazharmh,
Your Windows Authentication username has to have the appropriate security access to the SSAS instance.
I've found that you need to enter the SSAS database name even though it says on the dialog that the name is optional.
