Forum Discussion
PowerBI Desktop using HTTP endpoint to connect an OLAP Cube... Why "Connect Live" isn't allowed?
- 9 years ago
Hi All,
After several hours following the HTTP configuration steps, reading the community posts and trying all the proposed solutions without success, creating, configuring and deleting several Azure VMs… I tried another approach to eliminating any Azure missing configuration. I created a VM locally running SQL SERVER 2016 SP1 dev edition and IIS 10, where I installed the HTTP data pump and Finally worked… I was able to connect Power BI Desktop to the Cube, getting all the metadata using the HTTP endpoint…
I believe the main issue was that our cube is running on SQL Server 2012.... and when using the Azure VMs with SQL Server 2016 SP1 to do my tests using the public IP address Power BI returned always the error shown in the previous post, maybe I miss some Azure configurations... (note if I'm in the Azure Machine and use the internal IP address the HTTP endpoint works)
Before you start using the Power BI Desktop connection live with the HTTP endpoint you need to add a Windows credential with the user and password required by the HTTP end point….
Please got to Control Panel > User Accounts > Credential Manager, and click “Add a Windows Credential”,
After I have the HTTP data pump working and create the first Report using Power BI Desktop Edition I tried to Publish it to the Power BI Service, but once is an Analysis Services on- premises... I needed to install the Power BI on-Premisses Gateway... to do that I added to the VM the AD Role... after promoting the VM to a domain controller and set the gateway configuration, everything worked fine... :)
the following image depicts all components together,
Now, the Power BI on-premisses Gateway working with the HTTP endpoint:
Finally, the dataset using the gateway always up to date,
Hope this information helps others with the same issue I had ;)
Cheers, Luis
Hi Again,
few more tests...
I created two Azure VMs with SQL Server 2016 SP1 Dev Edition and with Power BI Desktop on both, (let's call them 2016SP1Server and 2016SP1Client), one of them I configured the HTTP Data Pump and restored an OLAP cube.
> I'm able to connect the cube from both machines using the HTTP Data pump and the import option...
> When I'm in the 2016SP1Server I can connect the cube using the HTTP data pump and the Connect live :) .. the URL used :
When I'm in the 2016SP1Client I can't connect the cube using the HTTP data pump and the Connect live :(.. with the same error I got before:
Any suggestion?
Cheers, Luis
Hi All,
After several hours following the HTTP configuration steps, reading the community posts and trying all the proposed solutions without success, creating, configuring and deleting several Azure VMs… I tried another approach to eliminating any Azure missing configuration. I created a VM locally running SQL SERVER 2016 SP1 dev edition and IIS 10, where I installed the HTTP data pump and Finally worked… I was able to connect Power BI Desktop to the Cube, getting all the metadata using the HTTP endpoint…
I believe the main issue was that our cube is running on SQL Server 2012.... and when using the Azure VMs with SQL Server 2016 SP1 to do my tests using the public IP address Power BI returned always the error shown in the previous post, maybe I miss some Azure configurations... (note if I'm in the Azure Machine and use the internal IP address the HTTP endpoint works)
Before you start using the Power BI Desktop connection live with the HTTP endpoint you need to add a Windows credential with the user and password required by the HTTP end point….
Please got to Control Panel > User Accounts > Credential Manager, and click “Add a Windows Credential”,
After I have the HTTP data pump working and create the first Report using Power BI Desktop Edition I tried to Publish it to the Power BI Service, but once is an Analysis Services on- premises... I needed to install the Power BI on-Premisses Gateway... to do that I added to the VM the AD Role... after promoting the VM to a domain controller and set the gateway configuration, everything worked fine... :)
the following image depicts all components together,
Now, the Power BI on-premisses Gateway working with the HTTP endpoint:
Finally, the dataset using the gateway always up to date,
Hope this information helps others with the same issue I had ;)
Cheers, Luis
- EricBoubert9 years agoNew Member
Hello Luis,
We are trying to use PowerBi with the datapump.
We want to use basic authentication but it doesn't work with the live connection.
Do you see and solve this issue ?
- tannera9 years agoAdvocate II
Same issue here.
- LuisQuedas9 years agoAdvocate I
Hi tannera
Are you connecting directly Power BI desktop to your source using the HTTP datapump? are you tyring to publish your reports on the Power BI Cloud Service?, would you like to provide me more information about what you are trying to do and your setup?
I need to know more details ;)
Thanks, Luis
- LuisQuedas9 years agoAdvocate I
Hi Eric, sorry only reply this post now...
Are you connecting directly Power BI desktop to your source using the HTTP datapump? are you tyring to publish your reports on the Power BI Cloud Service?, would you like to provide me more information about what you are trying to do and your setup?
Thanks, Luis