Skip to main content
Microsoft Idea

Power BI

Needs Votes

Support SSAS connection using HTTP data pump (msmdpump.dll)

Vote (119) Share
Tony Valentine's profile image

Tony Valentine on 20 Mar 2015 03:50:23

I know its a bit strange that we would want to configure the Power BI SSAS connector to point to an HTTP msmdpump, but it allows us to do something we can't do when going directly to the server. However, when I get to the last phase where it creates the connection in Power BI, it returns a strange "The remote server return an error: (404) Not Found....." that I do not get when going directly to the server. Could you validate my results and perhaps fix?

Comments (28)
Tony Valentine's profile image Profile Picture

Jimmy Jauhal on 06 Jul 2020 00:16:04

RE: Support SSAS connection using HTTP data pump (msmdpump.dll)

Just wanted to follow up, the live connection to a msmdpump.dll is still seems like it is NOT supported from PBI Desktop I can only do an Import. Excel and Tableau support this, so the question is: is the Power BI team working on this issue?

Tony Valentine's profile image Profile Picture

Pär Adeen on 06 Jul 2020 00:11:46

RE: Support SSAS connection using HTTP data pump (msmdpump.dll)

We are also trying to connect to a foreign ISS towards a SSAS database. We are using the SSAS connector and it "works fine" from Power BI Desktop. The authentication we use is a Basic authentication, but the user identity looks like a domain account as domain\user

AnalysisServices.Databases("https://report.site.com/msmdpump.dll", [TypedMeasureColumns=true, Implementation="2.0"])

Our problem seams to be that the SSAS connector enforces the usage of the Power BI Gateway, and it's in the Power BI Gateway we experiences the problems. This since the account provided are are told to not be in our domain or a trusted domain. To solve this I have asked the data source supplier to setup a proxy in-front of the IIS to re-write the credentials so that we no longer need to use a domain\user user identity and instead use a pure basic user identity

Are my problem definition correct? If so, I guess that it would also be possible to allow a none GW connection and instead connect directly to the ISS. If the AnalysisServices.Databases connector was open-source I the connector could easily be re-written by someone having the skills to also allow none GW connections.

If this is true, couldn't we use some other native odata connector instead?

Tony Valentine's profile image Profile Picture

Jakub Marsik on 06 Jul 2020 00:04:46

RE: Support SSAS connection using HTTP data pump (msmdpump.dll)

Hello guys, if you are ok with MDX and would like to get data from SSAS instance that is outside of AD domain and published with MSMDPUMP HTTP interface into Power BI Service with scheduled refresh capability, check out my little helper proxy application:

https://github.com/jmarsik/SSASQueryProxy

It simply gets parameters from URL and/or request body, executes MDX query (connection to SSAS can be direct with AS protocol or through MSMDPUMP) and returns back results in JSON format. You can use it from Power BI with Web.Contents M function.

Tony Valentine's profile image Profile Picture

pato lobos on 05 Jul 2020 23:58:06

RE: Support SSAS connection using HTTP data pump (msmdpump.dll)

As stated in one of the comments below this is supported since day one :
You need to add an entry in Credential Manager under 'Windows Credentials'.
Just go to :

Control Panel\All Control Panel Items\Credential Manager

And "Add a Windows Credential"
Internet or network address:
User name:
Password:
Persistante: Enterprise

Tony Valentine's profile image Profile Picture

Alvin Lau on 05 Jul 2020 23:00:22

RE: Support SSAS connection using HTTP data pump (msmdpump.dll)

Is Live Connection from PBI report server to msmdpump.dll supported as of today?

Tony Valentine's profile image Profile Picture

Alex on 05 Jul 2020 22:55:08

RE: Support SSAS connection using HTTP data pump (msmdpump.dll)

As of July 2017, the live connection to a msmdpump.dll is NOT supported.

Excel and Tableau support this, so the question is: is the Power BI team working on this issue?

Tony Valentine's profile image Profile Picture

Sylvain Driancourt on 05 Jul 2020 22:43:49

RE: Support SSAS connection using HTTP data pump (msmdpump.dll)

'Hi Everyone,
In order to avoid opening port with fixed IPs we are also trying to connect Power BI Desktop in live connection to SSAS 2016 Multidim through http://..../msmdpump.dll

It globally works, but we have frequent errors (Can't display visual) with the message: "The http server returned the following error: Service unavaible".
-->This is strange, because this seems to be randomed. When we click on Refresh we can get the visual to work.
Has anyone experienced this?

Tony Valentine's profile image Profile Picture

Greg Galloway on 05 Jul 2020 22:41:18

RE: Support SSAS connection using HTTP data pump (msmdpump.dll)

I agree that Power BI Desktop in live connection mode should support connecting to SSAS via msmdpump.dll. (It appears it works if you connect in import mode not live mode.) Also the gateway should support this.

Tony Valentine's profile image Profile Picture

Wouter Zijlstra on 05 Jul 2020 22:36:30

RE: Support SSAS connection using HTTP data pump (msmdpump.dll)

Hi all,

i didn't see a comment where someone got a working connection with a datapump (msmdpump.dll). Well, it can be done!!

First you need an entry in de Credential Manager under 'Windows Credentials'. You can add one with the connection string, username and password.

In Power BI Desktop you can make a connection with SSAS by using the datapump connection string as server and make a live connection with your model. Start building your report!!

In PowerBI.com you can make a gateway on the same connection string and datamodel and it will work in Power BI service too!

Good luck!

Tony Valentine's profile image Profile Picture

Scott Miller on 05 Jul 2020 22:34:30

RE: Support SSAS connection using HTTP data pump (msmdpump.dll)

Our organization does not allow us to use SSAS directly due to security concerns.