GatewayPipelineErrorCode=DM_GWPipeline_UnknownError

[lopezd]

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=AdomdErrorResponseException
InnerMessage=<pi>Errors related to feature availability and configuration: The 'Tabular View' feature is not included in the '64 Bit Standard' edition of Analysis Services.</pi>
InnerToString=<pi>Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: Errors related to feature availability and configuration: The 'Tabular View' feature is not included in the '64 Bit Standard' edition of Analysis Services.
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.AdomdConnection.IXmlaClientProviderEx.Discover(String requestType, String requestNamespace, IDictionary restrictions, InlineErrorHandlingType inlineErrorHandling, IDictionary requestProperties)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.GetSchemaDataSet(String schemaName, String schemaNamespace, IDictionary adomdRestrictions, Boolean throwOnInlineErrors, IDictionary requestProperties)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.GetSchemaDataSet(String schemaName, String schemaNamespace, AdomdRestrictionCollection restrictions, Boolean throwOnInlineErrors, AdomdPropertyCollection requestProperties)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.AdomdProcessor.GetSchemaDataSet(AdomdConnection connection, GetSchemaDataSetRequest request)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.AdomdProcessor.<>c__DisplayClass1.<<GetSchemaDataSet>b__0>d__3.MoveNext()</pi>
InnerCallStack=   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.AdomdConnection.IXmlaClientProviderEx.Discover(String requestType, String requestNamespace, IDictionary restrictions, InlineErrorHandlingType inlineErrorHandling, IDictionary requestProperties)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.GetSchemaDataSet(String schemaName, String schemaNamespace, IDictionary adomdRestrictions, Boolean throwOnInlineErrors, IDictionary requestProperties)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.GetSchemaDataSet(String schemaName, String schemaNamespace, AdomdRestrictionCollection restrictions, Boolean throwOnInlineErrors, AdomdPropertyCollection requestProperties)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.AdomdProcessor.GetSchemaDataSet(AdomdConnection connection, GetSchemaDataSetRequest request)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.AdomdProcessor.<>c__DisplayClass1.<<GetSchemaDataSet>b__0>d__3.MoveNext()
  ([1]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.GatewayPipelineWrapperException.StackTrace:)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.AdomdConnection.IXmlaClientProviderEx.Discover(String requestType, String requestNamespace, IDictionary restrictions, InlineErrorHandlingType inlineErrorHandling, IDictionary requestProperties)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.GetSchemaDataSet(String schemaName, String schemaNamespace, IDictionary adomdRestrictions, Boolean throwOnInlineErrors, IDictionary requestProperties)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.GetSchemaDataSet(String schemaName, String schemaNamespace, AdomdRestrictionCollection restrictions, Boolean throwOnInlineErrors, AdomdPropertyCollection requestProperties)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.AdomdProcessor.GetSchemaDataSet(AdomdConnection connection, GetSchemaDataSetRequest request)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.AdomdProcessor.<>c__DisplayClass1.<<GetSchemaDataSet>b__0>d__3.MoveNext()
   --- End of inner exception stack trace ---
  ([0]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.AdomdDataAccessErrorResponseException.StackTrace:)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.AdomdProcessor.<>c__DisplayClass1.<<GetSchemaDataSet>b__0>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.Common.Diagnostics.PipelineTelemetryService.<ExecuteInActivity>d__a`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.AdomdProcessor.<GetSchemaDataSet>d__c.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessorDispatcher.<DispatchImpl>d__e.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessorDispatcher.<Dispatch>d__b.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.Serialization.GatewayDeserializer.<DeserializeImpl>d__e.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.Serialization.GatewayDeserializer.<>c__DisplayClass4.<<Deserialize>b__2>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.Common.Diagnostics.PipelineTelemetryService.<ExecuteInActivity>d__a`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.Serialization.GatewayDeserializer.<Deserialize>d__9.MoveNext()

Do you know what can it be?

[v-yuezhe-msft]

Hi @lopezd,

Do you connect to multi-dimensional model on SQL Server 2012/2014 Standard edition? If that is the case, it is not supported currently.  As stated in this article, you need to have an Enterprise or Business Intelligence edition of SQL Server 2012/2014 Analysis Services, otherwise, you will get the above error message. Regarding to this limitation, you can also vote it in this idea: https://ideas.powerbi.com/forums/265200-power-bi/suggestions/11331360-connect-multidimensional-to-sq...

However, you are able connect to multi-dimensional models on SQL Server 2016 Standard edition from Power BI.

Thanks,
Lydia Zhang

[lopezd]

Hi Lydia, thanks for your response. We are using the enterprise edition.

We can connect our Analysis services cube by importing the data but not in a live connection. I been looking for almost all the videos, we have been trying a lot of dirrerent things.

We get this message for PB Pro:

"There was a data source error. Please contact the gateway administrator"

And this message fot PB desktop:

"This data source does not support exploring with a live connection"

Do you know why we can´t connect?

Thanks

[v-yuezhe-msft]

Hi @lopezd,

Firstly, please verify that if you are connecting to SQL Server 2012 Analysis Services SP1 CU4 or later versions. You can execute "Select @@version" in SQL Server to check version and edition.

Secondly, make sure that you don't have unprocessed SSAS databases.

Thirdly, please use the latest version of Power BI Desktop.

Thanks,
Lydia Zhang

[lopezd]

Hi Lydia,

1.- We are connected to SQL Server 2012 Analysis Services SP1 CU4

2.-All databases are updated

3.-I unistall power bi destop and Download it again yesterday. How can i check if it´s the latest version?

Thanks

[v-yuezhe-msft]

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]

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

[v-yuezhe-msft · Accepted solution]

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]

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]

I updated to SQL 16 Enterprise, this issue is solved