cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
dataguy Member
Member

How To Troubleshoot Unexpected Error Live Connect to SSAS OLAP Database

My team is having a hard time getting all of our cubes to be able to be used in Power BI.  Many work just fine but when we try to connect to others in the desktop we get "An error occurred while loading the model for the item or data source 'QuerySystemError'. Verify that the connection information is correct and that you have permissions to access the data source.

 

Our DBAs setup a profiler session trying to see if there was anything to give a hint as to why we are getting the error message.

 

1) Here is the event ID raised on the SSAS server in the Application log at the OS level:

 

Log Name:      Application

Source:        MSSQLServerOLAPService

Date:          12/27/2017 9:18:29 AM

Event ID:      22

Task Category: (256)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      XXX

Description:

The description for Event ID 22 from source MSSQLServerOLAPService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

 

If the event originated on another computer, the display information had to be saved with the event.

 

The following information was included with the event:

 

Internal error: An unexpected exception occurred.

 

the message resource is present but the message is not found in the string/message table

 

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="MSSQLServerOLAPService" />

    <EventID Qualifiers="49408">22</EventID>

    <Level>2</Level>

    <Task>256</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2017-12-27T15:18:29.000000000Z" />

    <EventRecordID>475867</EventRecordID>

    <Channel>Application</Channel>

    <Computer>XXX</Computer>

    <Security />

  </System>

  <EventData>

    <Data>Internal error: An unexpected exception occurred.</Data>

  </EventData>

</Event>

 

 

2) Here is the error text logged to the msmdsrv.log file on the SSAS server:

 

(12/27/2017 9:18:30 AM) Message:  (Source: \\?\Z:\SQLMountPoint\SQLTLogs\ASLogs\msmdsrv.log, Type: 3, Category: 256, Event ID: 0xC1000016)

 

  

3) The file FlightRecorder_20171222.trc was capture and the DBAs noticed Error # -1056964586 while the connection was trying to be made from Power BI Desktop.

 

What can we do to try to figure out what Power BI doesn't like about this cube?

 

Thanks

 

11 REPLIES 11
v-jiascu-msft Super Contributor
Super Contributor

Re: How To Troubleshoot Unexpected Error Live Connect to SSAS OLAP Database

Hi @dataguy,

 

Please refer to this documention that solves the exact same issue with yours. It seems your DBA needs to upgrade the SQL Server or applies a workaround.

 

Best Regards,

Dale

Community Support Team _ Dale
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Highlighted
dataguy Member
Member

Re: How To Troubleshoot Unexpected Error Live Connect to SSAS OLAP Database

I will have our DBAs check our current SP levels for the SSAS 2012 servers we are accessing.  Thanks!

dataguy Member
Member

Re: How To Troubleshoot Unexpected Error Live Connect to SSAS OLAP Database

So SP4 for SSAS 2012 was applied and we are still getting the same error message when trying to connect to the cube from the Power BI Desktop.  Running traces again. 

dataguy Member
Member

Re: How To Troubleshoot Unexpected Error Live Connect to SSAS OLAP Database

Here is the frown details from the Power BI Desktop when trying to access the cube in SSAS 2012 SP4

 

Feedback Type:
Frown (Error)

Timestamp:
2017-12-29T15:36:39.1426024Z

Local Time:
2017-12-29T09:36:39.1426024-06:00

Session ID:
e8f9456a-46fd-4cf0-95f1-dbfb5ab6f04e

Release:
December 2017

Product Version:
2.53.4954.481 (PBIDesktop) (x64)

Error Message:
An error occurred while loading the model for the item or data source 'QuerySystemError'. Verify that the connection information is correct and that you have permissions to access the data source.

Stack Trace:
Microsoft.ReportingServices.Diagnostics.Utilities.CannotRetrieveModelException: An error occurred while loading the model for the item or data source 'QuerySystemError'. Verify that the connection information is correct and that you have permissions to access the data source. ---> Microsoft.PowerBI.DataExtension.Contracts.DataExtensionException: Failed to get CSDL. ---> MsolapWrapper.MsolapWrapperException: Failure encountered while getting schema

Invocation Stack Trace:
at Microsoft.Mashup.Host.Document.ExceptionExtensions.GetCurrentInvocationStackTrace()
at Microsoft.Mashup.Client.ClientShared.FeedbackErrorInfo..ctor(String message, Exception exception)
at Microsoft.PowerBI.Client.Windows.Telemetry.PowerBIUserFeedbackServices.ReportException(IWin32Window activeWindow, WindowsHost windowsHost, FeedbackPackageInfo feedbackPackageInfo, Exception e)
at Microsoft.Mashup.Client.ClientShared.UnexpectedExceptionHandler.<>c__DisplayClass1.<HandleException>b__0()
at Microsoft.Mashup.Client.ClientShared.UnexpectedExceptionHandler.HandleException(Exception e)
at Microsoft.PowerBI.Client.Windows.Utilities.UIBlockingAwareExceptionHandler.HandleException(Exception e)
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions[T](IExceptionHandler exceptionHandler, Func`1 func)
at Microsoft.PowerBI.Client.Windows.Commands.CommandFactory.<>c__DisplayClass6.<FromSyncHandlers>b__5(CommandParameter p)
at Microsoft.Practices.Prism.Commands.CompositeCommand.CanExecute(Object parameter)
at Microsoft.Mashup.Client.Windows.UICommands.CommandAction.IsEnabled(UInt32 commandId)
at Microsoft.Mashup.Client.Windows.Ribbon.RibbonCommandHandler.UpdateProperty(UInt32 commandId, PropertyKey& key, PropVariantRef currentValue, PropVariant& newValue)
at Microsoft.Mashup.Client.Windows.Ribbon.Interop.IUIFramework.FlushPendingInvalidations()
at Microsoft.Mashup.Client.Windows.Ribbon.Interop.IUIFramework.FlushPendingInvalidations()
at Microsoft.Mashup.Client.Windows.Ribbon.RibbonCommandHandler.FlushInvalidations()
at Microsoft.Mashup.Client.Windows.Ribbon.RibbonCommandHandler.InvalidateAllCommands(Boolean invalidateAllProperties)
at Microsoft.Mashup.Client.Windows.Ribbon.EditorRibbonControlBase.InternalInvalidateRibbon()
at Microsoft.PowerBI.Client.Windows.Ribbon.ApplicationRibbonControl.InternalInvalidateRibbon()
at Microsoft.Mashup.Client.Windows.Ribbon.EditorRibbonControlBase.Invalidate()
at Microsoft.Practices.Prism.PubSubEvents.EventSubscription`1.<>c__DisplayClass2.<GetExecutionStrategy>b__0(Object[] arguments)
at Microsoft.Practices.Prism.PubSubEvents.EventBase.InternalPublish(Object[] arguments)
at Microsoft.PowerBI.Client.Windows.Services.EventAggregationService.<>c__DisplayClassf`2.<<PublishInternal>b__e>d__11.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.Client.Windows.Services.EventAggregationService.<>c__DisplayClassf`2.<PublishInternal>b__e()
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<HandleAwaitableAsyncExceptions>d__3.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.HandleAwaitableAsyncExceptions(IExceptionHandler exceptionHandler, Func`1 asyncFunc)
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<HandleAsyncExceptions>d__0.MoveNext()
at System.Runtime.CompilerServices.AsyncVoidMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.HandleAsyncExceptions(IExceptionHandler exceptionHandler, Func`1 asyncFunc)
at Microsoft.PowerBI.Client.Windows.Services.EventAggregationService.Publish[TEvent](EventArgsBase eventArgs)
at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesDatabaseHelper.PublishDataChangeEvent()
at Microsoft.PowerBI.Client.Windows.Report.set_AnalysisServicesDatabase(IAnalysisServicesDatabase value)
at Microsoft.PowerBI.Client.Windows.PowerBIDataImporter.ValidateAndCreateLiveConnection(ILiveConnectionProperties connectionProperties)
at Microsoft.Mashup.Client.ClientShared.DataImporter.<>c__DisplayClass8.<TryAddSource>b__4(JsonUpdate builderResults, Formula updatedFormula)
at Microsoft.Mashup.Client.ClientShared.DataImporter.ShowBuilderDialog(PackageReference packageReference, FormulaPath formulaPath, FormulaPartInfo formulaPartInfo, Query query, Action`2 successCallback, Action failureCallback, Boolean isNewQuery, Boolean isFromEditor)
at Microsoft.Mashup.Client.ClientShared.DataImporter.ResolveQuerySettings(Query query, Action`2 successCallback, Action failureCallback, ResolutionSetting resolutionSetting, Boolean isNewQuery, Boolean isFromEditor)
at Microsoft.Mashup.Client.ClientShared.DataImporter.TryAddSource(String sourceID, Query& newQuery)
at Microsoft.Mashup.Client.ClientShared.ConnectHelper.Connect(IWin32Window owner, IDataSourceTemplateProvider dataSourceTemplateProvider, WindowsHost windowsHost, ITelemetryService telemetryService, DataImporter dataImporter, CommandUIControlBase commandUIControl, String sourceId, Nullable`1 targetQueryGroupId)
at Microsoft.PowerBI.Client.Windows.Commands.ApplicationCommands.DataImportCommands.Connect(IPowerBIWindowService windowService, IExceptionHandler exceptionHandler, ConnectParameters parameters)
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
at Microsoft.PowerBI.Client.Windows.Commands.CommandFactory.<>c__DisplayClass42`1.<FromSyncHandlers>b__3f(UICommandParameter`1 p)
at Microsoft.Practices.Prism.Commands.DelegateCommandBase.<>c__DisplayClass2.<.ctor>b__0(Object arg)
at Microsoft.Practices.Prism.Commands.DelegateCommandBase.<Execute>d__7.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.Practices.Prism.Commands.DelegateCommandBase.Execute(Object parameter)
at Microsoft.Practices.Prism.Commands.DelegateCommandBase.<System.Windows.Input.ICommand.Execute>d__4.MoveNext()
at System.Runtime.CompilerServices.AsyncVoidMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.Practices.Prism.Commands.DelegateCommandBase.System.Windows.Input.ICommand.Execute(Object parameter)
at Microsoft.Practices.Prism.Commands.CompositeCommand.Execute(Object parameter)
at Microsoft.PowerBI.Client.Windows.PowerBIDataSourceTemplateProvider.ConnectInternal(String formulaId, Nullable`1 targetQueryGroupId)
at Microsoft.Mashup.Host.Document.DataSourceTemplateProvider.Connect(String formulaId, Nullable`1 targetQueryGroupId)
at Microsoft.Mashup.Client.ClientShared.Ux.FloatingDialog.SimpleDialog.DataSourceGalleryDialog.<>c__DisplayClass2.<ConnectToDataSource>b__0()
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at Microsoft.Mashup.Client.ClientShared.WindowManager.ShowDialog[T](T form, IWin32Window owner)
at Microsoft.PowerBI.Client.Program.<>c__DisplayClassb.<Main>b__0()
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<>c__DisplayClass7.<HandleExceptionsWithNestedTasks>b__6()
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
at Microsoft.PowerBI.Client.Program.Main(String[] args)


OS Version:
Microsoft Windows NT 10.0.16299.0 (x64 en-US)

CLR Version:
4.7 or later [Release Number = 461308]

Peak Virtual Memory:
33.9 GB

Private Memory:
308 MB

Peak Working Set:
421 MB

IE Version:
11.64.16299.0

User ID:
YYY

Workbook Package Info:
1* - en-US, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: True.

Telemetry Enabled:
True

Screenshot:


AS Live Connection:
True

dataguy Member
Member

Re: How To Troubleshoot Unexpected Error Live Connect to SSAS OLAP Database

Same issue when connecting to SSAS 2016

 

Feedback Type:
Frown (Error)

Timestamp:
2017-12-29T15:38:42.4490728Z

Local Time:
2017-12-29T09:38:42.4490728-06:00

Session ID:
d7424bfb-36a3-42ac-a59b-88426e6acdba

Release:
December 2017

Product Version:
2.53.4954.481 (PBIDesktop) (x64)

Error Message:
An error occurred while loading the model for the item or data source 'QuerySystemError'. Verify that the connection information is correct and that you have permissions to access the data source.

Stack Trace:
Microsoft.ReportingServices.Diagnostics.Utilities.CannotRetrieveModelException: An error occurred while loading the model for the item or data source 'QuerySystemError'. Verify that the connection information is correct and that you have permissions to access the data source. ---> Microsoft.PowerBI.DataExtension.Contracts.DataExtensionException: Failed to get CSDL. ---> MsolapWrapper.MsolapWrapperException: Failure encountered while getting schema

Invocation Stack Trace:
at Microsoft.Mashup.Host.Document.ExceptionExtensions.GetCurrentInvocationStackTrace()
at Microsoft.Mashup.Client.ClientShared.FeedbackErrorInfo..ctor(String message, Exception exception)
at Microsoft.PowerBI.Client.Windows.Telemetry.PowerBIUserFeedbackServices.ReportException(IWin32Window activeWindow, WindowsHost windowsHost, FeedbackPackageInfo feedbackPackageInfo, Exception e)
at Microsoft.Mashup.Client.ClientShared.UnexpectedExceptionHandler.<>c__DisplayClass1.<HandleException>b__0()
at Microsoft.Mashup.Client.ClientShared.UnexpectedExceptionHandler.HandleException(Exception e)
at Microsoft.PowerBI.Client.Windows.Utilities.UIBlockingAwareExceptionHandler.HandleException(Exception e)
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions[T](IExceptionHandler exceptionHandler, Func`1 func)
at Microsoft.PowerBI.Client.Windows.Commands.CommandFactory.<>c__DisplayClass6.<FromSyncHandlers>b__5(CommandParameter p)
at Microsoft.Practices.Prism.Commands.CompositeCommand.CanExecute(Object parameter)
at Microsoft.Mashup.Client.Windows.UICommands.CommandAction.IsEnabled(UInt32 commandId)
at Microsoft.Mashup.Client.Windows.Ribbon.RibbonCommandHandler.UpdateProperty(UInt32 commandId, PropertyKey& key, PropVariantRef currentValue, PropVariant& newValue)
at Microsoft.Mashup.Client.Windows.Ribbon.Interop.IUIFramework.FlushPendingInvalidations()
at Microsoft.Mashup.Client.Windows.Ribbon.Interop.IUIFramework.FlushPendingInvalidations()
at Microsoft.Mashup.Client.Windows.Ribbon.RibbonCommandHandler.FlushInvalidations()
at Microsoft.Mashup.Client.Windows.Ribbon.RibbonCommandHandler.InvalidateAllCommands(Boolean invalidateAllProperties)
at Microsoft.Mashup.Client.Windows.Ribbon.EditorRibbonControlBase.InternalInvalidateRibbon()
at Microsoft.PowerBI.Client.Windows.Ribbon.ApplicationRibbonControl.InternalInvalidateRibbon()
at Microsoft.Mashup.Client.Windows.Ribbon.EditorRibbonControlBase.Invalidate()
at Microsoft.Practices.Prism.PubSubEvents.EventSubscription`1.<>c__DisplayClass2.<GetExecutionStrategy>b__0(Object[] arguments)
at Microsoft.Practices.Prism.PubSubEvents.EventBase.InternalPublish(Object[] arguments)
at Microsoft.PowerBI.Client.Windows.Services.EventAggregationService.<>c__DisplayClassf`2.<<PublishInternal>b__e>d__11.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.Client.Windows.Services.EventAggregationService.<>c__DisplayClassf`2.<PublishInternal>b__e()
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<HandleAwaitableAsyncExceptions>d__3.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.HandleAwaitableAsyncExceptions(IExceptionHandler exceptionHandler, Func`1 asyncFunc)
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<HandleAsyncExceptions>d__0.MoveNext()
at System.Runtime.CompilerServices.AsyncVoidMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.HandleAsyncExceptions(IExceptionHandler exceptionHandler, Func`1 asyncFunc)
at Microsoft.PowerBI.Client.Windows.Services.EventAggregationService.Publish[TEvent](EventArgsBase eventArgs)
at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesDatabaseHelper.PublishDataChangeEvent()
at Microsoft.PowerBI.Client.Windows.Report.set_AnalysisServicesDatabase(IAnalysisServicesDatabase value)
at Microsoft.PowerBI.Client.Windows.PowerBIDataImporter.ValidateAndCreateLiveConnection(ILiveConnectionProperties connectionProperties)
at Microsoft.Mashup.Client.ClientShared.DataImporter.<>c__DisplayClass8.<TryAddSource>b__4(JsonUpdate builderResults, Formula updatedFormula)
at Microsoft.Mashup.Client.ClientShared.DataImporter.ShowBuilderDialog(PackageReference packageReference, FormulaPath formulaPath, FormulaPartInfo formulaPartInfo, Query query, Action`2 successCallback, Action failureCallback, Boolean isNewQuery, Boolean isFromEditor)
at Microsoft.Mashup.Client.ClientShared.DataImporter.ResolveQuerySettings(Query query, Action`2 successCallback, Action failureCallback, ResolutionSetting resolutionSetting, Boolean isNewQuery, Boolean isFromEditor)
at Microsoft.Mashup.Client.ClientShared.DataImporter.TryAddSource(String sourceID, Query& newQuery)
at Microsoft.Mashup.Client.ClientShared.ConnectHelper.Connect(IWin32Window owner, IDataSourceTemplateProvider dataSourceTemplateProvider, WindowsHost windowsHost, ITelemetryService telemetryService, DataImporter dataImporter, CommandUIControlBase commandUIControl, String sourceId, Nullable`1 targetQueryGroupId)
at Microsoft.PowerBI.Client.Windows.Commands.ApplicationCommands.DataImportCommands.Connect(IPowerBIWindowService windowService, IExceptionHandler exceptionHandler, ConnectParameters parameters)
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
at Microsoft.PowerBI.Client.Windows.Commands.CommandFactory.<>c__DisplayClass42`1.<FromSyncHandlers>b__3f(UICommandParameter`1 p)
at Microsoft.Practices.Prism.Commands.DelegateCommandBase.<>c__DisplayClass2.<.ctor>b__0(Object arg)
at Microsoft.Practices.Prism.Commands.DelegateCommandBase.<Execute>d__7.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.Practices.Prism.Commands.DelegateCommandBase.Execute(Object parameter)
at Microsoft.Practices.Prism.Commands.DelegateCommandBase.<System.Windows.Input.ICommand.Execute>d__4.MoveNext()
at System.Runtime.CompilerServices.AsyncVoidMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.Practices.Prism.Commands.DelegateCommandBase.System.Windows.Input.ICommand.Execute(Object parameter)
at Microsoft.Practices.Prism.Commands.CompositeCommand.Execute(Object parameter)
at Microsoft.PowerBI.Client.Windows.PowerBIDataSourceTemplateProvider.ConnectInternal(String formulaId, Nullable`1 targetQueryGroupId)
at Microsoft.Mashup.Host.Document.DataSourceTemplateProvider.Connect(String formulaId, Nullable`1 targetQueryGroupId)
at Microsoft.Mashup.Client.ClientShared.Ux.FloatingDialog.SimpleDialog.DataSourceGalleryDialog.<>c__DisplayClass2.<ConnectToDataSource>b__0()
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at Microsoft.Mashup.Client.ClientShared.WindowManager.ShowDialog[T](T form, IWin32Window owner)
at Microsoft.PowerBI.Client.Program.<>c__DisplayClassb.<Main>b__0()
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<>c__DisplayClass7.<HandleExceptionsWithNestedTasks>b__6()
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
at Microsoft.PowerBI.Client.Program.Main(String[] args)


OS Version:
Microsoft Windows NT 10.0.16299.0 (x64 en-US)

CLR Version:
4.7 or later [Release Number = 461308]

Peak Virtual Memory:
33.8 GB

Private Memory:
309 MB

Peak Working Set:
418 MB

IE Version:
11.64.16299.0

User ID:
YYY

Workbook Package Info:
1* - en-US, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: True.

Telemetry Enabled:
True

Screenshot:


AS Live Connection:
True

PFeedback Type:
Frown (Error)

Timestamp:
2017-12-29T15:38:42.4490728Z

Local Time:
2017-12-29T09:38:42.4490728-06:00

Session ID:
d7424bfb-36a3-42ac-a59b-88426e6acdba

Release:
December 2017

Product Version:
2.53.4954.481 (PBIDesktop) (x64)

Error Message:
An error occurred while loading the model for the item or data source 'QuerySystemError'. Verify that the connection information is correct and that you have permissions to access the data source.

dataguy Member
Member

Re: How To Troubleshoot Unexpected Error Live Connect to SSAS OLAP Database

Extended Events Captured

 

So from runnuing the extended events, the following metadata queries succeeded before the failure occured

 

  1.  select [MEASURE_CAPTION] from $system.mdschema_measures where [CUBE_NAME] = @CubeName and [MEASURE_IS_VISIBLE]
  2. select [DIMENSION_CAPTION]from $system.mdschema_dimensions where [CUBE_NAME] = @CubeName and [DIMENSION_UNIQUE_NAME] <> '[Measures]' and [DIMENSION_IS_VISIBLE]
  3. select [CUBE_NAME], [LAST_DATA_UPDATE], [DESCRIPTION], [BASE_CUBE_NAME] from $system.MDSCHEMA_CUBES where [CATALOG_NAME] = @CatalogName and [CUBE_SOURCE] = 1
  4. select [CUBE_NAME] from $system.MDSCHEMA_CUBES where [CUBE_SOURCE] = 1
  5. select [CUBE_NAME] from $system.MDSCHEMA_CUBES where [CUBE_SOURCE] = 1

Then we get the error -1056964586   Internal error: An unexpected exception occurred

v-jiascu-msft Super Contributor
Super Contributor

Re: How To Troubleshoot Unexpected Error Live Connect to SSAS OLAP Database

Hi @dataguy,

 

Does the credential you used in the Power BI have enough privileges? I would suggest you go to here for professional help.

 

Please mask your private data.

 

Best Regards,

Dale

Community Support Team _ Dale
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
dataguy Member
Member

Re: How To Troubleshoot Unexpected Error Live Connect to SSAS OLAP Database

Dale,

 

The credential works just fine in SSMS browsing the cube and via Excel. I am 99.9% sure this is not a privileges issue.  Also when you say to mask your private data what data are you referring to?  

 

Thanks.

dataguy Member
Member

Re: How To Troubleshoot Unexpected Error Live Connect to SSAS OLAP Database

I think I might have potenially solved this but I would need confirmation from whomever knows what the code is doing when reading the metadata.

 

I ended up removing all of the Dimensions via Dimension Usage and starting adding them back in one by one.  Each time testing to see if Power BI could do a Live Connect on the cube. By the end when I got through all 100+ dimensions, I was still able to connect via Power BI.

 

I generated the xmla from the original cube not working and the rebuilt (sort of speak) one that was working. It turns out there are some differences like the UnknownMember property is missing on some of the original cube dimensions. The cube was originally built in 2005 or 2008 and migrated to 2012.  The UnknownMember property was introduced in SSAS 2012 from what I can tell.

 

It would be nice if someone could confirm my suspension on this.   

Thanks!

Helpful resources

Announcements
Community Highlights

Community Highlights

Find out what's new in the Power BI Community!

Summit North America

Power Platform Summit North America

Register by September 5 to save $200

Virtual Launch Event

Microsoft Business Applications Virtual Launch Event

Watch the event on demand for an in-depth look at the new innovations across Dynamics 365 and the Microsoft Power Platform.

MBAS Gallery

Watch Sessions On Demand!

Continue your learning in our online communities.

Users Online
Currently online: 238 members 2,639 guests
Please welcome our newest community members: