Forum Discussion

lopezd's avatar
lopezd
Regular Visitor
10 years ago
Solved

GatewayPipelineErrorCode=DM_GWPipeline_UnknownError

Hi,   I´m traing to connect my AS database to Power BI pro but i´m getting this log error from my gateway log:   GatewayPipelineErrorCode=DM_GWPipeline_UnknownError InnerType=AdomdErrorResponseE...
  • Anonymous's avatar
    Anonymous
    10 years ago

    Hi lopezd,

    Please check the edition, version and patchlevel of your SSAS instance from the following registry. Make sure your SSAS instance meets requirement and you don't mix it with SQL Server Database engine.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS11.InstanceName \Setup Keys: Edition ,PatchLevel , Version.



    Thanks,
    Lydia Zhang

Anonymous's avatar
Anonymous
Not applicable
10 years ago

Hi lopezd,

In Power BI Desktop, you can go to File>Help>About to check its version. The latest version of Power BI Desktop is 2.37.4464.602, which can be downloaded is this link.


Thanks,
Lydia Zhang

lopezd's avatar
lopezd
Regular Visitor
10 years ago

Hi Lydia,

 

Thanks for the response we have the new version now. We can not get live connection jet. SQL Server Analysis Services Tabular model databases as well as multidimensional models? or should be one or the other?

 

Thanks

 

 

  • Anonymous's avatar
    Anonymous
    Not applicable
    10 years ago

    Hi lopezd,

    Please check the edition, version and patchlevel of your SSAS instance from the following registry. Make sure your SSAS instance meets requirement and you don't mix it with SQL Server Database engine.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS11.InstanceName \Setup Keys: Edition ,PatchLevel , Version.



    Thanks,
    Lydia Zhang

    • ManuMCD's avatar
      ManuMCD
      Regular Visitor
      9 years ago

      I have the same issue and I'm not able to publish BI reports via Gateway. Are there any solution about this issue?

       

      Thanks a lot.

      Regards

      Manuel

      • lopezd's avatar
        lopezd
        Regular Visitor
        9 years ago

        I updated to SQL 16 Enterprise, this issue is solved