Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
dbeavon3
Continued Contributor
Continued Contributor

SSAS MD cube measures not displaying

I have a "live" connection to an SSAS MD cube.  I wrote a report in Power BI desktop and published to the service back in March and it worked fine.  I'm reopening that report now and it breaks (both in the service and in the desktop).

 

I'm really not certain what changed, but it probably wasn't something in the SSAS MD cube itself.  It may have been related to reinstalling the latest gateway and the latest desktop client.

 

The message that I see (both in the desktop and in the gateway logs) is probably a red herring:  Tabular metadata and DAX queries are not supported when there are dimension calculations defined for this session or query scope. Please contact your administrator for more information.

 

This is unhelpful.  I'd guess that the message is a generic one which just means that something bad happened with the MSOLAP OLEDB client.  Below is the full error log for the failure..

 

The problem happens all the time for any reports against a certain MD cube.  But for other MD cubes, there is no problem.  It may be related to the structure/metadata.  We do not use "cell security" or anything like that, although we do have dimension security.  Another interesting thing is that the power bi service in the portal is able to show the entire schema of the cube but just can't process queries against it.

 

 

 

 

 

 

DM.EnterpriseGateway Error: 0 : 2019-06-25T14:50:36.8159872Z DM.EnterpriseGateway	bcb660b5-dca9-43c8-b3dd-4a070c8106c2	180e1757-aa09-bb47-a988-117ac84a15fe	MGEO	f64fa6a5-785b-4b64-8ac4-4e6910d128a3	37357e6d-10f5-433b-b68b-ed1b30e7aa26	37357e6d-10f5-433b-b68b-ed1b30e7aa26	007657AE [DM.GatewayCore] Oledb Command Properties : Microsoft.PowerBI.DataMovement.Pipeline.InternalContracts.Communication.OleDbProperty[]
DM.EnterpriseGateway Error: 0 : 2019-06-25T14:50:36.8159872Z DM.EnterpriseGateway	bcb660b5-dca9-43c8-b3dd-4a070c8106c2	180e1757-aa09-bb47-a988-117ac84a15fe	MGEO	f64fa6a5-785b-4b64-8ac4-4e6910d128a3	37357e6d-10f5-433b-b68b-ed1b30e7aa26	37357e6d-10f5-433b-b68b-ed1b30e7aa26	758090EC [DM.GatewayCore] Oledb Command Data Source : Microsoft.PowerBI.DataMovement.ExternalContracts.Gateway.DataSourceGatewayDetails
DM.EnterpriseGateway Error: 0 : 2019-06-25T14:50:36.8159872Z DM.EnterpriseGateway	bcb660b5-dca9-43c8-b3dd-4a070c8106c2	180e1757-aa09-bb47-a988-117ac84a15fe	MGEO	f64fa6a5-785b-4b64-8ac4-4e6910d128a3	37357e6d-10f5-433b-b68b-ed1b30e7aa26	37357e6d-10f5-433b-b68b-ed1b30e7aa26	F7B520D9 [DM.GatewayCore] Oledb Command Data Source Properties: Microsoft.PowerBI.DataMovement.Pipeline.InternalContracts.Communication.OleDbProperty[]
DM.EnterpriseGateway Error: 0 : 2019-06-25T14:50:36.8169846Z DM.EnterpriseGateway	bcb660b5-dca9-43c8-b3dd-4a070c8106c2	180e1757-aa09-bb47-a988-117ac84a15fe	MGEO	f64fa6a5-785b-4b64-8ac4-4e6910d128a3	37357e6d-10f5-433b-b68b-ed1b30e7aa26	37357e6d-10f5-433b-b68b-ed1b30e7aa26	AA1668A5 [DM.GatewayCore] Oledb Command Text Exception :
DM.EnterpriseGateway Error: 0 : 2019-06-25T14:50:37.2003950Z DM.EnterpriseGateway	16e2afc9-2778-45db-ac34-68c148618962	180e1757-aa09-bb47-a988-117ac84a15fe	MGEF	f64fa6a5-785b-4b64-8ac4-4e6910d128a3	37357e6d-10f5-433b-b68b-ed1b30e7aa26	37357e6d-10f5-433b-b68b-ed1b30e7aa26	9F0B5CAE [DM.Pipeline.Common] Non-gateway exception encountered in activity scope: System.Runtime.InteropServices.COMException (0x80004005): Tabular metadata and DAX queries are not supported when there are dimension calculations defined for this session or query scope. Please contact your administrator for more information.
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at Microsoft.PowerBI.DataMovement.Pipeline.OleDbBase.ICommandTextExtensions.ExecuteMultipleResults(ICommandText commandText, DBPARAMS* parameters)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayPipelineTelemetry.PipelineTelemetryService.ExecuteInActivity[T](PipelineActivityType pipelineActivityType, Func`1 action)
DM.EnterpriseGateway Error: 0 : 2019-06-25T14:50:37.2003950Z DM.EnterpriseGateway	16e2afc9-2778-45db-ac34-68c148618962	180e1757-aa09-bb47-a988-117ac84a15fe	MGEF	f64fa6a5-785b-4b64-8ac4-4e6910d128a3	37357e6d-10f5-433b-b68b-ed1b30e7aa26	37357e6d-10f5-433b-b68b-ed1b30e7aa26	E05182D4 [DM.Pipeline.Common.TracingTelemetryService] Event: FireActivityCompletedWithFailureEvent (duration=247, err=COMException, rootcauseErrorEventId=0)
DM.EnterpriseGateway Error: 0 : 2019-06-25T14:50:37.2003950Z DM.EnterpriseGateway	bcb660b5-dca9-43c8-b3dd-4a070c8106c2	180e1757-aa09-bb47-a988-117ac84a15fe	MGEO	f64fa6a5-785b-4b64-8ac4-4e6910d128a3	37357e6d-10f5-433b-b68b-ed1b30e7aa26	37357e6d-10f5-433b-b68b-ed1b30e7aa26	CDE9D07D [DM.GatewayCore] Oledb Command Text Causing Error : <pi>EVALUATE
  ADDCOLUMNS(
    KEEPFILTERS(
      TOPN(
        1002,
        ADDCOLUMNS(
          KEEPFILTERS(
            FILTER(
              KEEPFILTERS(VALUES('Product'[Product Type Code])),
              NOT(ISBLANK('Activity'[Sales]))
            )
          ),
          "Sales_Product_Type_Code", 'Activity'[Sales]
        ),
        [Sales_Product_Type_Code],
        0,
        'Product'[Product Type Code],
        1
      )
    ),
    "Sales", [Sales_Product_Type_Code],
    "Sales_FormatString", 'Activity'[Sales.FormatString],
    "ActivitySales", CALCULATE(
      'Activity'[Sales],
      KEEPFILTERS(
        FILTER(
          KEEPFILTERS(ALL('Branch'[Branch Company DB Code])),
          'Branch'[Branch Company DB Code] = "COR"
        )
      )
    ),
    "ActivitySales_FormatString", CALCULATE(
      'Activity'[Sales.FormatString],
      KEEPFILTERS(
        FILTER(
          KEEPFILTERS(ALL('Branch'[Branch Company DB Code])),
          'Branch'[Branch Company DB Code] = "COR"
        )
      )
    )
  )

ORDER BY
  [Sales_Product_Type_Code] DESC, 'Product'[Product Type Code]</pi>
DM.EnterpriseGateway Error: 0 : 2019-06-25T14:50:37.2003950Z DM.EnterpriseGateway	bcb660b5-dca9-43c8-b3dd-4a070c8106c2	180e1757-aa09-bb47-a988-117ac84a15fe	MGEO	f64fa6a5-785b-4b64-8ac4-4e6910d128a3	37357e6d-10f5-433b-b68b-ed1b30e7aa26	37357e6d-10f5-433b-b68b-ed1b30e7aa26	007657AE [DM.GatewayCore] Oledb Command Properties : Microsoft.PowerBI.DataMovement.Pipeline.InternalContracts.Communication.OleDbProperty[]
DM.EnterpriseGateway Error: 0 : 2019-06-25T14:50:37.2003950Z DM.EnterpriseGateway	bcb660b5-dca9-43c8-b3dd-4a070c8106c2	180e1757-aa09-bb47-a988-117ac84a15fe	MGEO	f64fa6a5-785b-4b64-8ac4-4e6910d128a3	37357e6d-10f5-433b-b68b-ed1b30e7aa26	37357e6d-10f5-433b-b68b-ed1b30e7aa26	758090EC [DM.GatewayCore] Oledb Command Data Source : Microsoft.PowerBI.DataMovement.ExternalContracts.Gateway.DataSourceGatewayDetails
DM.EnterpriseGateway Error: 0 : 2019-06-25T14:50:37.2003950Z DM.EnterpriseGateway	bcb660b5-dca9-43c8-b3dd-4a070c8106c2	180e1757-aa09-bb47-a988-117ac84a15fe	MGEO	f64fa6a5-785b-4b64-8ac4-4e6910d128a3	37357e6d-10f5-433b-b68b-ed1b30e7aa26	37357e6d-10f5-433b-b68b-ed1b30e7aa26	F7B520D9 [DM.GatewayCore] Oledb Command Data Source Properties: Microsoft.PowerBI.DataMovement.Pipeline.InternalContracts.Communication.OleDbProperty[]
DM.EnterpriseGateway Error: 0 : 2019-06-25T14:50:37.2003950Z DM.EnterpriseGateway	bcb660b5-dca9-43c8-b3dd-4a070c8106c2	180e1757-aa09-bb47-a988-117ac84a15fe	MGEO	f64fa6a5-785b-4b64-8ac4-4e6910d128a3	37357e6d-10f5-433b-b68b-ed1b30e7aa26	37357e6d-10f5-433b-b68b-ed1b30e7aa26	AA1668A5 [DM.GatewayCore] Oledb Command Text Exception :
DM.EnterpriseGateway Error: 0 : 2019-06-25T14:50:37.2103943Z DM.EnterpriseGateway	bcb660b5-dca9-43c8-b3dd-4a070c8106c2	180e1757-aa09-bb47-a988-117ac84a15fe	MGEO	f64fa6a5-785b-4b64-8ac4-4e6910d128a3	37357e6d-10f5-433b-b68b-ed1b30e7aa26	37357e6d-10f5-433b-b68b-ed1b30e7aa26	8A86571C [DM.Pipeline.Diagnostics] Exception object created [IsBenign=True]: Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.OleDbCreateRowsetFailedException: Error creating OLE DB row set.; ErrorShortName: OleDbCreateRowsetFailedException[ErrorCode=-2147467259,HResult=-2147467259]/Wrapped(COMException)[ErrorCode=-2147467259,HResult=-2147467259]
DM.EnterpriseGateway Error: 0 : 2019-06-25T14:50:37.2103943Z DM.EnterpriseGateway	bcb660b5-dca9-43c8-b3dd-4a070c8106c2	180e1757-aa09-bb47-a988-117ac84a15fe	MGEO	f64fa6a5-785b-4b64-8ac4-4e6910d128a3	37357e6d-10f5-433b-b68b-ed1b30e7aa26	37357e6d-10f5-433b-b68b-ed1b30e7aa26	DFA28060 [DM.Pipeline.Common.TracingTelemetryService] Event: FireActivityCompletedWithFailureEvent (duration=904, err=OleDbCreateRowsetFailedException, rootcauseErrorEventId=0)
DM.EnterpriseGateway Error: 0 : 2019-06-25T14:50:37.2103943Z DM.EnterpriseGateway	fc79dccb-5ae1-4343-a5d9-2fb1160da715	180e1757-aa09-bb47-a988-117ac84a15fe	MGPP	f64fa6a5-785b-4b64-8ac4-4e6910d128a3	37357e6d-10f5-433b-b68b-ed1b30e7aa26	37357e6d-10f5-433b-b68b-ed1b30e7aa26	32280606 [DM.Pipeline.Common.TracingTelemetryService] Event: FireActivityCompletedWithFailureEvent (duration=915, err=OleDbCreateRowsetFailedException, rootcauseErrorEventId=0)
DM.EnterpriseGateway Error: 0 : 2019-06-25T14:50:37.2173498Z DM.EnterpriseGateway	93eaf679-aae3-4705-9787-91805c4ef40a	180e1757-aa09-bb47-a988-117ac84a15fe	MDSR	f64fa6a5-785b-4b64-8ac4-4e6910d128a3	37357e6d-10f5-433b-b68b-ed1b30e7aa26	37357e6d-10f5-433b-b68b-ed1b30e7aa26	D52E3545 [DM.GatewayCore] Error processing request: [0]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.OleDbCreateRowsetFailedException: Error creating OLE DB row set.

GatewayPipelineErrorCode=DM_GWPipeline_Gateway_DataSourceAccessError
GatewayVersion= --->
[1]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.GatewayPipelineWrapperException: Substituted: COMException:<pi>System.Runtime.InteropServices.COMException (0x80004005): Tabular metadata and DAX queries are not supported when there are dimension calculations defined for this session or query scope. Please contact your administrator for more information.
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at Microsoft.PowerBI.DataMovement.Pipeline.OleDbBase.ICommandTextExtensions.ExecuteMultipleResults(ICommandText commandText, DBPARAMS* parameters)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayPipelineTelemetry.PipelineTelemetryService.ExecuteInActivity[T](PipelineActivityType pipelineActivityType, Func`1 action)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.OleDbProcessor.<>c__DisplayClass4_0.<ExecuteOleDbQuery>b__1(IOleDbRequestSession requestSession)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.OleDbProcessor.ProcessRequest[TRequest](GatewaySerializationContext serverContext, TRequest request, OleDbInternalErrorKind errorKind, Func`2 operation, Action`1 onOperationFailure, Guid requestId)</pi>

GatewayPipelineErrorCode=DM_GWPipeline_UnknownError
GatewayVersion=
InnerType=COMException
InnerMessage=<pi>Tabular metadata and DAX queries are not supported when there are dimension calculations defined for this session or query scope. Please contact your administrator for more information.</pi>
InnerToString=<pi>System.Runtime.InteropServices.COMException (0x80004005): Tabular metadata and DAX queries are not supported when there are dimension calculations defined for this session or query scope. Please contact your administrator for more information.
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at Microsoft.PowerBI.DataMovement.Pipeline.OleDbBase.ICommandTextExtensions.ExecuteMultipleResults(ICommandText commandText, DBPARAMS* parameters)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayPipelineTelemetry.PipelineTelemetryService.ExecuteInActivity[T](PipelineActivityType pipelineActivityType, Func`1 action)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.OleDbProcessor.<>c__DisplayClass4_0.<ExecuteOleDbQuery>b__1(IOleDbRequestSession requestSession)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.OleDbProcessor.ProcessRequest[TRequest](GatewaySerializationContext serverContext, TRequest request, OleDbInternalErrorKind errorKind, Func`2 operation, Action`1 onOperationFailure, Guid requestId)</pi>
InnerCallStack=   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at Microsoft.PowerBI.DataMovement.Pipeline.OleDbBase.ICommandTextExtensions.ExecuteMultipleResults(ICommandText commandText, DBPARAMS* parameters)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayPipelineTelemetry.PipelineTelemetryService.ExecuteInActivity[T](PipelineActivityType pipelineActivityType, Func`1 action)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.OleDbProcessor.<>c__DisplayClass4_0.<ExecuteOleDbQuery>b__1(IOleDbRequestSession requestSession)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.OleDbProcessor.ProcessRequest[TRequest](GatewaySerializationContext serverContext, TRequest request, OleDbInternalErrorKind errorKind, Func`2 operation, Action`1 onOperationFailure, Guid requestId)
  ([1]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.GatewayPipelineWrapperException.StackTrace:)
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at Microsoft.PowerBI.DataMovement.Pipeline.OleDbBase.ICommandTextExtensions.ExecuteMultipleResults(ICommandText commandText, DBPARAMS* parameters)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayPipelineTelemetry.PipelineTelemetryService.ExecuteInActivity[T](PipelineActivityType pipelineActivityType, Func`1 action)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.OleDbProcessor.<>c__DisplayClass4_0.<ExecuteOleDbQuery>b__1(IOleDbRequestSession requestSession)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.OleDbProcessor.ProcessRequest[TRequest](GatewaySerializationContext serverContext, TRequest request, OleDbInternalErrorKind errorKind, Func`2 operation, Action`1 onOperationFailure, Guid requestId)
   --- End of inner exception stack trace ---
  ([0]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.OleDbCreateRowsetFailedException.StackTrace:)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.OleDbProcessor.ProcessRequest[TRequest](GatewaySerializationContext serverContext, TRequest request, OleDbInternalErrorKind errorKind, Func`2 operation, Action`1 onOperationFailure, Guid requestId)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.OleDbProcessor.<>c__DisplayClass4_0.<ExecuteOleDbQuery>b__0()
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayPipelineTelemetry.PipelineTelemetryService.ExecuteInActivity[T](PipelineActivityType pipelineActivityType, Func`1 action)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessorDispatcher.<DispatchImpl>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessorDispatcher.<Dispatch>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.Serialization.GatewayDeserializer.<DeserializeImpl>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.Serialization.GatewayDeserializer.<>c__DisplayClass8_0.<<Deserialize>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayPipelineTelemetry.PipelineTelemetryService.<ExecuteInActivity>d__7`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.Serialization.GatewayDeserializer.<Deserialize>d__8.MoveNext()

 

If anyone understands why the live connection is no longer working, I would be very interested to hear.

 

1 ACCEPTED SOLUTION
dbeavon3
Continued Contributor
Continued Contributor

I figured this out. The cube in question was using a feature called "personalization extensions" that makes enhancements to the available members of dimensions. (The "personalization" process will add stuff into the session on the fly).

 

The DAXMD is apparently not happy with the use of this type of feature.


I'm still not sure why it would cause a problem. Perhaps, while it can detect the session calcs, the DAXMD is not sophisticated enough to interact with them. It would be nice if it would just avoid them rather than throwing out an error. My query didn't actually rely on any new calculations which were being defined in the session.

 

More info:

https://social.msdn.microsoft.com/Forums/en-US/ef92d1a6-6ae0-4b87-b459-6403f789a153/tabular-metadata...

View solution in original post

2 REPLIES 2
dbeavon3
Continued Contributor
Continued Contributor

I tried updating my MSOLAP client driver to the latest and it doesn't help.

https://docs.microsoft.com/en-us/azure/analysis-services/analysis-services-data-providers

 

I also tested to see what happens when I run the same DAXMD from SSMS and it works fine in there!

 

So this appears to be a problem that is specific to the Power BI code itself?

 

dbeavon3
Continued Contributor
Continued Contributor

I figured this out. The cube in question was using a feature called "personalization extensions" that makes enhancements to the available members of dimensions. (The "personalization" process will add stuff into the session on the fly).

 

The DAXMD is apparently not happy with the use of this type of feature.


I'm still not sure why it would cause a problem. Perhaps, while it can detect the session calcs, the DAXMD is not sophisticated enough to interact with them. It would be nice if it would just avoid them rather than throwing out an error. My query didn't actually rely on any new calculations which were being defined in the session.

 

More info:

https://social.msdn.microsoft.com/Forums/en-US/ef92d1a6-6ae0-4b87-b459-6403f789a153/tabular-metadata...

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors