Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
7 years ago

MSOLAP version for Enterprise Gateway

I've noticed the Enterprise Gateway installs MSOLAP 5 and it doesn't seem to use any other version even if I have the latest client libraries installed on the same machine. 

 

In the Gateway logs I notice entries like: 

AdoNetDBFullConnectiongString: Service Msolap progid is different with on-prem. Service:MSOLAP.5. On-Prem:MSOLAP.8.

...

Optional command property c8b522be-5cf3-11ce-ade5-00aa0044773d:BOOKMARKS is not supported by MSOLAP.8

 

 

 

My question is, is it possible to update this to the latest version and is there any benefit in doing so? I can't find much info or release notes on the differences between the versions.

5 Replies

  • v-yuta-msft's avatar
    v-yuta-msft
    Community Support

    Hi dmgdotnet,

     

    Analysis Services utilize three client libraries, also known as data providers. ADOMD.NET and Analysis Services Management Objects (AMO) are managed client libraries. The Analysis Services OLE DB Provider (MSOLAP DLL) is a native client library. Typically, all three are installed at the same time. Azure Analysis Services requires the latest versions of all three libraries.

     

    So you should download and update the three lastest client libraries for connecting to azure analysis services. Please refer to the documentation: https://docs.microsoft.com/en-us/azure/analysis-services/analysis-services-data-providers.

     

    Regards,

    Jimmy Tao

    • Anonymous's avatar
      Anonymous
      Not applicable

      Hi Jimmy Tao,

       

      Replying again as I can't see my first attempt on the thread, apologies if this gets posted twice.

       

      Thanks for the reply but I'm specifically referring to the Enterprise Gateway which seems to install and use the old version of the provider no matter what I have already available on the server at the time of installation.  

       

      The Gateway has it's own copy of the dlls in it's installation directory and there are no instructions on upgrading this or if we should.

       

      Edit: Typo

      • goflse's avatar
        goflse
        Helper I

        I have exactly the same issue. Downloaded gateay today. Runing SQLServer 2016 SP2 Enterprise.

        Help needed urgently.

         

        Kind regards Göran

  • Anonymous's avatar
    Anonymous
    Not applicable

    Not sure why this was marked as solved, it definitly wasn't me that marked as solution and this is not solved.