none
Through IIS manager not able to connect to Analysis Services in 2017 version RRS feed

  • Question

  • Through IIS manager not able to connect to Analysis Services in 2017 version

    http://server_name/olap/msmdpump.dll is not working while connecting to SSAS 2017 version, till 2016 version it's working fine
    Wednesday, November 1, 2017 6:54 PM

Answers

  • Hi,

    Instead of using 2017 version of msmdpump.dll  file please use the 2016 version of msmdpump.dll

    it will work

    - Srini


    Sunday, November 12, 2017 6:13 PM

All replies

  • Hi Srini kokerla,

    Thanks for your question.

    Would you mind elaborating more on this issue ? Such as the detailed error messages, the steps how you configure it.

    It is pretty hard to answer this without useful information. Thanks for your understanding. you may also consider opening a support case . Visit this link to see the various support options that are available to better meet your needs:  http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone.


    Best Regards
    Willson Yuan
    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Thursday, November 2, 2017 5:55 AM
    Moderator
  • We are trying to configure http access to connect to a SSAS Tabular OLAP cube on SQL Server Analysis Services 2017. We went through the following link  

    https://docs.microsoft.com/en-us/sql/analysis-services/instances/configure-http-access-to-analysis-services-on-iis-8-0

    and followed each step meticulously. After completing all steps when we tried connecting to it withwe are not able http://<server_name>/olap/msmdpump.dll  to. Get this exception – “Internal server error (500)”.

    We tried the same with a SQL Server Analysis Services 2016 and it works perfectly. The exact same steps followed. Tried searching for similar issues or cases but was not able to find any.  Details below..

    SQL Server 2017 build version – 14.0.1.439

    IIS version - 8.5.9600.16384



    Thursday, November 2, 2017 8:37 AM
  • Hi Srini kokerla,

    Thanks for your response.

    According to your description, you have set up the http access for your SSAS Tabular OLAP cube on SQL Server Analysis Services 2017. Now you can not connect to it , and get this exception – “Internal server error (500)”, right?

    In this scenario, you may try to connect to it with the server IP address instead of server name, you can try something like http://serverIPAddress/olap/msmdpump.dll  , see if it works for you.

    For error “Internal server error (500)”,  you can also refer to below blog:

    https://www.lifewire.com/500-internal-server-error-explained-2622938


    Best Regards
    Willson Yuan
    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Friday, November 3, 2017 1:11 AM
    Moderator
  • Thanks Willson Yuan

    it's not working. we are approaching MSDN SUpport Team.

    Thanks

    Srini

    Friday, November 3, 2017 1:34 PM
  • Hi Srini kokerla,

    Thanks for your response.

    Please post back the solution here. This can be beneficial to other community members who are facing similar issues, thank for your contribution.


    Best Regards
    Willson Yuan
    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Monday, November 6, 2017 1:09 AM
    Moderator
  • Hi,

    Instead of using 2017 version of msmdpump.dll  file please use the 2016 version of msmdpump.dll

    it will work

    - Srini


    Sunday, November 12, 2017 6:13 PM
  • Hi Srini kokerla,

    Thanks for your contribution.


    Best Regards
    Willson Yuan
    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Monday, November 13, 2017 8:18 AM
    Moderator
  • This problem still exists a year later. Hours of wasted effort until I stumbled across this thread. We've also opened a case w/ MS.

    Has there been a hot fix or other update to fix this bug?

    <rant>I’m just astonished that MS can release a product without any documentation of changes between msmdpump versions and no troubleshooting tips. I tried for hours to get this to work and they’re just too lazy to document or fix it?</rant>

    Monday, November 26, 2018 4:07 PM
  • Latest cumulative update fixes this problem please use SQL Server 2017 CU16 (Latest). I was also facing the same issue but when i update to latest CU16 .

    Thanks, Shishupal

    Tuesday, August 6, 2019 4:27 PM
  • We are on 2017 CU16 and having same issue. I am trying to set up these first time.
    Thursday, November 21, 2019 11:46 PM