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

Don't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.

Power BI Desktop Crashes Completely

Hello,

After updating to the November 2024 version of Power BI, the application crashes randomly when calculations are running in the background (We are encountering problems. Please close and restart Power BI Desktop.). This issue prevents saving the file through the usual "Save" option and gives the same error, although using "Ctrl + S" allows you to save. However, upon reopening the saved file, all the data disappears. 

please assist

error details:

Feedback Type:
Frown (Error)

Timestamp:
2025-01-17T15:26:14.1837502Z

Local Time:
2025-01-17T18:26:14.1837502+03:00

Session ID:
6bbdd37d-c306-44e8-9e6b-b1ba2b774487

Release:
November 2024

Product Version:
2.138.1452.0 (24.11) (x64)

Error Message:
We are encountering problems. Please close and restart Power BI Desktop.

Stack Trace:
Microsoft.PowerBI.Client.Windows.MainWindow+AnalysisServicesCrashedAfterSuccessfulConnectionException
at Microsoft.PowerBI.Client.Windows.MainWindow.OnAnalysisServicesProcessExited(AnalysisServicesProcessExitedEventArgs e)
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__DisplayClass19_0`2.<PublishAndMarshalExceptions>b__0()
at Microsoft.Mashup.Host.Document.SynchronizationContextExtensions.<>c__DisplayClass2_0.<SendAndMarshalExceptions>b__0(Object null)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.Mashup.Host.Document.SynchronizationContextExtensions.SendAndMarshalExceptions(SynchronizationContext context, Action callback)
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)

Stack Trace Message:
We are encountering problems. Please close and restart Power BI Desktop.

Invocation Stack Trace:
at Microsoft.Mashup.Host.Document.ExceptionExtensions.GetCurrentInvocationStackTrace()
at Microsoft.Mashup.Client.UI.Shared.StackTraceInfo..ctor(String exceptionStackTrace, String invocationStackTrace, String exceptionMessage)
at Microsoft.PowerBI.Client.Windows.Telemetry.PowerBIUserFeedbackServices.GetStackTraceInfo(Exception e)
at Microsoft.PowerBI.Client.Windows.Telemetry.PowerBIUserFeedbackServices.ReportException(IWindowHandle activeWindow, IUIHost uiHost, FeedbackPackageInfo feedbackPackageInfo, Exception e, Boolean useGDICapture)
at Microsoft.Mashup.Client.UI.Shared.UnexpectedExceptionHandler.<>c__DisplayClass14_0.<HandleException>b__0()
at Microsoft.Mashup.Host.Document.SynchronizationContextExtensions.<>c__DisplayClass2_0.<SendAndMarshalExceptions>b__0(Object null)
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.UI.Shared.WindowManager.ShowModal[T](T dialog, Func`1 showModalFunction)
at Microsoft.PowerBI.Client.Program.<>c__DisplayClass7_0.<RunApplicationLegacy>b__0()
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<>c__DisplayClass3_0.<HandleExceptionsWithNestedTasks>b__0()
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
at Microsoft.PowerBI.Client.Program.RunApplicationLegacy(String[] args)
at Microsoft.PowerBI.Client.Program.Main(String[] args)


PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.138.1452.0","ModuleName":"Microsoft.PowerBI.Client.Windows.dll","Component":"Microsoft.PowerBI.Client.Windows.MainWindow","Error":"Microsoft.PowerBI.Client.Windows.MainWindow+AnalysisServicesCrashedAfterSuccessfulConnectionException","MethodDef":"OnAnalysisServicesProcessExited","ErrorOffset":"44","ErrorCode":""}

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

CLR Version:
4.8 or later [Release Number = 533320]

Peak Virtual Memory:
71.5 GB

Private Memory:
1.07 GB

Peak Working Set:
1.34 GB

IE Version:
11.1882.26100.0

User ID:
d200133b-6815-4d5c-8752-c60f72b30822

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

Telemetry Enabled:
True

Snapshot Trace Logs:
C:\Users\ashra\AppData\Local\Microsoft\Power BI Desktop\FrownSnapShot0f6aeb4d-4d00-4886-9a8c-628db5c7717d.zip

Model Default Mode:
Composite

Model Version:
PowerBI_V3

Performance Trace Logs:
C:\Users\ashra\AppData\Local\Microsoft\Power BI Desktop\PerformanceTraces.zip

Enabled Preview Features:
PBI_sparklines
PBI_scorecardVisual
PBI_fieldParametersSuperSwitch
PBI_setLabelOnExportPdf
PBI_oneDriveSave
PBI_oneDriveShare
PBI_useModernPublishDialogs
PBI_gitIntegration
PBI_newCard
PBI_buttonSlicerAuthoring
PBI_EimLessElevatedUser
PBI_mobileAutoReportLayout
PBI_daxInlineCopilot
PBI_aiNarrativesVisual
PBI_generateMeasureDescriptionsButton
PBI_visualCalculationsAuthoring
PBI_desktopReportAuthoringCopilot

Disabled Preview Features:
PBI_shapeMapVisualEnabled
PBI_SpanishLinguisticsEnabled
PBI_qnaLiveConnect
PBI_metricsArtifactsOnDesktop
PBI_b2bExternalDatasetSharing
PBI_enhancedTooltips
PBI_onObject
PBI_odspSaveBackgroundUpload
PBI_publishDialogsSupportSubfolders
PBI_tmdlInDataset
PBI_enhancedReportFormat
PBI_directLakeRemoteModeling
PBI_advancedSlicerTypeList
PBI_textSlicer
PBI_qnaImproveLsdlCopilot

Disabled DirectQuery Options:
TreatHanaAsRelationalSource

Cloud:
GlobalCloud

PowerBIUserFeedbackServices_IsReported:
True

DPI Scale:
100%

Supported Services:
Power BI

Formulas:

 

Analysis Services Started Process ID:
25740

Status: Investigating

Hi @ashrafezz817 ,

 

We noticed that you seem to be using the MS app store version. Have you tried uninstalling the current version and downloading and installing Power BI Desktop from the official download link?

 

Best regards.
Community Support Team_Caitlyn

Comments
v-xiaoyan-msft
Community Support
Status changed to: Investigating

Hi @ashrafezz817 ,

 

We noticed that you seem to be using the MS app store version. Have you tried uninstalling the current version and downloading and installing Power BI Desktop from the official download link?

 

Best regards.
Community Support Team_Caitlyn

SLuscombe
New Member

I have a colleague with what appears to be the exact same issue.

We push out the MS app store version, so I've asked them to try using the other version.

ashrafezz817
Regular Visitor

@v-xiaoyan-msft i upgraded to jan version and i no longer have the issue