Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
Hallow everyone,
after updating Power BI desktop from version 2.114 (Feb 2023 Release) to the March 2023 version, the app crashed immediately on startup giving an error that an external component has thrown an exception. the application is installed on a windows server 2012 R2, some error details are below.
I thought I would roll back to Dec. 2022 version to see if it works, I unfortunatlly don't have the 2.114 setup file anymore.
Please help.
Feedback Type:
Frown (Error)
Timestamp:
2023-03-15T08:47:28.9016104Z
Local Time:
2023-03-15T11:47:28.9016104+03:00
Session ID:
7cfb7f39-7cf7-44db-8be6-d6e192c4b1e2
Release:
March 2023
Product Version:
2.115.663.0 (x86)
Stack Trace:
System.Runtime.InteropServices.SEHException
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.Application.RunDialog(Form form)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at Microsoft.Mashup.Client.UI.Windows.DialogWindowBase.ShowModal(IWindowHandle windowHandle)
at Microsoft.Mashup.Client.UI.Shared.WebDialogs.WebDialog.<>n__0(IWindowHandle owner)
at Microsoft.Mashup.Client.UI.Shared.WebDialogs.WebDialog.<>c__DisplayClass57_0.<ShowModal>b__0()
at Microsoft.Mashup.Client.UI.Shared.WindowManager.ShowModal[T](T dialog, Func`1 showModalFunction)
at Microsoft.Mashup.Client.UI.Shared.WebDialogs.WebDialog.ShowModal(IWindowHandle owner)
at Microsoft.Mashup.Client.UI.Shared.Ux.WindowService.ShowDialog(IDialog dialog)
at Microsoft.PowerBI.Client.Windows.FloatingDialog.StartDialog.Show(IPowerBIWindowService windowService, IExceptionHandler exceptionHandler, IPowerBIQueryUIService queryServices, IReportManager reportManager, IAutoRecoveryManager autoRecoveryManager, ILegacyUIHost uiHost, IUIBlockingService uiBlockingService, IPowerBIWindowServiceFactory windowServiceFactory, IFileHistoryManager fileHistoryManager, IAuthenticationManager authenticationManager, IUpdateNotificationManager updateNotificationManager, IApplicationCommands applicationCommands, IPowerBISettings powerBISettings, IUISettings uiSettings, IEventAggregationService eventAggregationService, IPowerBITelemetryService telemetryService, IUrlOpener urlOpener)
at Microsoft.PowerBI.Client.Windows.MainWindow.<ShowStartDialog>d__96.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 System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Microsoft.PowerBI.Client.Program.<>c__DisplayClass5_3.<<RunApplication>b__12>d.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.Client.Windows.MainWindow.<<ActivateMainWindow>b__116_1>d.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.Client.Windows.IExceptionHandlerExtensions.<HandleAwaitableAsyncExceptions>d__1.MoveNext()
Error Code:
-2147467259 (0x80004005)
PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.115.663.0","ModuleName":"Microsoft.Mashup.Client.UI.dll","Component":"Microsoft.Mashup.Client.UI.Windows.DialogWindowBase","Error":"System.Runtime.InteropServices.SEHException","MethodDef":"ShowModal","ErrorOffset":"17"}
OS Version:
Microsoft Windows NT 6.3.9600.0 (x64 en-US)
CLR Version:
4.8 or later [Release Number = 528049]
Peak Virtual Memory:
1.58 GB
Private Memory:
519 MB
Peak Working Set:
687 MB
IE Version:
11.0.9600.20874
User ID:
4259c6c6-f912-426e-8a86-b621577bd7f5
Workbook Package Info:
1* - en-US, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: False.
Telemetry Enabled:
True
Model Default Mode:
Empty
Model Version:
PowerBI_V1
Enabled Preview Features:
PBI_enableWebView2
PQ_WebView2Connector
PBI_sparklines
PBI_scorecardVisual
PBI_fieldParametersSuperSwitch
PBI_horizontalFusion
PBI_relationshipEditPane
PBI_setLabelOnExportPdf
Disabled Preview Features:
PBI_shapeMapVisualEnabled
PBI_SpanishLinguisticsEnabled
PBI_qnaLiveConnect
PBI_azureMapVisual
PBI_compositeModelsOverAS
PBI_b2bExternalDatasetSharing
PBI_enhancedTooltips
PBI_NlToDax
PBI_optimizeTabRibbon
PBI_angularRls
PBI_onObject
Disabled DirectQuery Options:
TreatHanaAsRelationalSource
Cloud:
GlobalCloud
DPI Scale:
100%
Supported Services:
Power BI
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi all,
Update:
Power BI released the latest version 2.115.842.0 64-bit (March 2023) , please download it to see if the problem still exists.
Download Microsoft Power BI Desktop from Official Microsoft Download Center
----------------------------------------------------------------------------------------------------------
We have seen this issue submitted by engineers on our internal platform to the product team.
Problem: After installing Power BI Desktop "March 2023 Update (2.115.663.0) " version, there was a startup error "External Component has thrown an exception"
They have been aware of the issue and the engineers will do their best to resolve it. I will update here if there is any progress, so please be patient.
Best regards.
Community Support Team_ Caitlyn