Forum Discussion

S-Driancourt's avatar
S-Driancourt
Frequent Visitor
9 years ago
Solved

Using HTTP data pump (msmdpump.dll) leads to (can't display visual) errors

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...
Dashboards
Gateways
  • S-Driancourt's avatar
    S-Driancourt
    9 years ago

    Thank you very much Qiuyun Yu for your feedback.

    We just found the solution to our issue and you were right, the issue was coming  from the IIS Server, or mor precisely from the configuration of the msmdpump.

    We read the following article:

    http://amolpandey.com/2016/08/26/ssas-msmdpump-dll-failing-occasionally-under-high-user-loads/

     

    And we added the following 3 lines in the msmdpump.ini file

    <MinThreadPoolSize>0</MinThreadPoolSize>
    <MaxThreadPoolSize>0</MaxThreadPoolSize>
    <MaxThreadsPerClient>20</MaxThreadsPerClient>
     
    Now we do not have the issue anymore, in Power BI Desktop or in Power BI Services
    Best regards,
    Sylvain
tannera's avatar
tannera
Advocate II
9 years ago

Thanks Sylvain for your answer. 

 

Did you ever encounter the impossibility to live connect to the pump using that method? From day one, we're not able to connect this way. In Excel or Tableau we have no problems. 

 

 

Microsoft even say the live connection is not supported in this recent thread I made: https://community.powerbi.com/t5/Desktop/Any-timeline-on-when-a-live-connection-to-a-msmdpump-dll-SSAS/m-p/231183

 

So I'm actually surprised you managed to live connect to your msmdpump.dll 

 

What steps did you take for it to authentify you correctly? 

 

Thanks

ChrisCoates's avatar
ChrisCoates
New Member
4 years ago

Hi - so I've been having the same issue but I *think* I just resolved it for us. I think it boils down to the fact the PowerBI SASS live connector doesn't support anything other than Windows Authentication. 

 

Our msmdpump.dll component sits on an an IIS server in a different domain. Generally we access it though a browser that prompts for defferent domain credentials. For a number of reasons, we had to change the IIS server to use Basic Authenticationm though with credentials still stored in the AD.

 

We managed to resolve some of those background issues, and I changed this particular application under the site (i.e. the OLAP directory) back to use Windows authentication and the Live connection started working. My application pool is using a single identity since we don't have Kerberos configured, which has "least permission" on the cubes themselves. this means that I can't configure any fine-grained access on this particular connector, which is OK for the time being whilst we transition these services into our main domain.

 

Hope this helps anyone else hunting aroud these articles for a solution like me!