Starting PowerBI: An error occurred while rendering the report.

[AadFourpoints]

Dear Community,

When starting PowerBI Desktop version 2.78.5740.841 64-bit (februari 2020) I experiences this error "An error occurred while rendering the report." Emtpying cache by Options > dataload within PowerBI as below mentioned workaround does not work:

1) Close all instances of Power BI Desktop

2) Open file explorer and navigate to the folder <system drive>:\Users\<user>\AppData\Local\Microsoft\Power BI Desktop\CEF\cache

• replace <system drive> with your operating system hard disk partition
• replace <user> with your user profile name, typically the alias you login to Windows with

3) Delete all contents of this folder

4) Restart Power BI Desktop

Are there any other options to clear firing up PowerBI? Below this pos I placed the trace of the errormessage, which seems to me a bit like out-of-date functionality or some sort?

Thanks in advance for reacting and kind regards,

Aad Dijksman (The Netherlands)

Feedback Type:
Frown (Error)

Error Message:
An error occurred while rendering the report.

Stack Trace:
Error: Uncaught (in promise): All Custom Visual Endpoints Are Down
at resolvePromise (ms-pbi://pbi.microsoft.com/minerva/scripts/desktop.js:103583:43)
at resolvePromise (ms-pbi://pbi.microsoft.com/minerva/scripts/desktop.js:103560:25)
at ms-pbi://pbi.microsoft.com/minerva/scripts/desktop.js:103623:29
at ZoneDelegate.invokeTask (ms-pbi://pbi.microsoft.com/minerva/scripts/desktop.js:103311:189)
at Object.onInvokeTask (ms-pbi://pbi.microsoft.com/minerva/scripts/desktop.js:9065:60)
at ZoneDelegate.invokeTask (ms-pbi://pbi.microsoft.com/minerva/scripts/desktop.js:103311:72)
at Zone.runTask (ms-pbi://pbi.microsoft.com/minerva/scripts/desktop.js:103195:63)
at drainMicroTaskQueue (ms-pbi://pbi.microsoft.com/minerva/scripts/desktop.js:103400:47)
at ZoneTask.invokeTask [as invoke] (ms-pbi://pbi.microsoft.com/minerva/scripts/desktop.js:103353:63)
at invokeTask (ms-pbi://pbi.microsoft.com/minerva/scripts/desktop.js:103976:68)

Stack Trace Message:
An error occurred while rendering the report.

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__DisplayClass0_1.<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.WebDialogs.WebDialog.<>n__0(IWindowHandle owner)
at Microsoft.Mashup.Client.UI.Shared.WindowManager.ShowModal[T](T dialog, Func`1 showModalFunction)
at Microsoft.PowerBI.Client.Windows.FloatingDialog.StartDialog.Show(MainWindow mainWindow, IWindowService windowService, IUIHost uiHost, IPowerBIWindowServiceFactory windowServiceFactory, IFileHistoryManager fileHistoryManager, IAuthenticationManager authenticationManager, IAuthenticationUIHandler authenticationUIHandler, ICloudConfigurationManager cloudManager, UpdateNotificationManager updateNotificationManager, IApplicationCommands applicationCommands, IPowerBISettings powerBISettings, IUISettings uiSettings, IEventAggregationService eventAggregationService, IPowerBITelemetryService telemetryService)
at Microsoft.PowerBI.Client.Windows.MainWindow.ShowStartDialog()
at Microsoft.PowerBI.Client.Program.<>c__DisplayClass2_7.<<Main>b__7>d.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.Client.Program.<>c__DisplayClass2_7.<Main>b__7(MainWindow mainWindow)
at Microsoft.PowerBI.Client.Windows.MainWindow.<<OnMainWindowInitializationCompleted>b__202_2>d.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.Client.Windows.MainWindow.<OnMainWindowInitializationCompleted>b__202_2()
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<HandleAwaitableAsyncExceptions>d__1.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.MainWindow.<OnMainWindowInitializationCompleted>b__202_1()
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.UI.Shared.WebDialogs.WebDialog.<>n__0(IWindowHandle owner)
at Microsoft.Mashup.Client.UI.Shared.WindowManager.ShowModal[T](T dialog, Func`1 showModalFunction)
at Microsoft.PowerBI.Client.Program.<>c__DisplayClass2_0.<Main>b__1()
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.Main(String[] args)

JS Error Message:
Uncaught (in promise): All Custom Visual Endpoints Are Down

Snapshot Trace Logs:
C:\Users\F040043\AppData\Local\Microsoft\Power BI Desktop\FrownSnapShot1385532406.zip

Model Default Mode:
Empty

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

Disabled Preview Features:
PBI_shapeMapVisualEnabled
PBI_SpanishLinguisticsEnabled
PBI_NewWebTableInference
PBI_qnaLiveConnect
PQ_AIInsightsFunctionBrowser
PBI_realTimeRefresh
PBI_QueryDiagnostics
PBI_showMinervaRibbon
PBI_showMinervaViewNavigator
PBI_decompositionTree
PBI_themeDialog
PBI_hierarchicalSlicerCreation

Disabled DirectQuery Options:
TreatHanaAsRelationalSource

Cloud:
GlobalCloud

Formulas:

section Section1;

Active Section Contract:
{"id":0,"name":"ReportSection","displayName":"Page 1","filters":"[]","ordinal":0,"visualContainers":[],"config":{},"displayOption":1,"width":1280,"height":720}

[stephenlloyd]

Did you find a resolution to this?  I have the same issue.

[stephenlloyd]

Nevermind, it turns out I didn't have network connectivity on my VM.

[Greg_Deckler]

You could check the Issues forum here:

https://community.powerbi.com/t5/Issues/idb-p/Issues

And if it is not there, then you could post it.

If you have Pro account you could try to open a support ticket. If you have a Pro account it is free. Go to https://support.powerbi.com. Scroll down and click "CREATE SUPPORT TICKET".

[AadFourpoints]

@Greg_Deckler  Thanks for your quick reply. Just to be sure that I understand (English is not my native language): when experiencing an issue, first I have to check the Issue forum and if not described, then I can post mine? I did check the community and found two possible solutions but both didn't work in my specific case, but I will give it another try.

Thanks and kind regards,

Aad Dijksman

[AadFourpoints]

All,

I do not want to be rude, but I ploughed a lot through diverse topics, but all experience similar message when already running PowerBI and trying to open a report of using some functionality. All solutions / workarounds I read are not of use to me.

I just did a fresh, clean installation on a just delivered clean Windows 2019 server, with an admin account and the first time I start PowerBI I immideately see this message. It occurs during starting-up. Caches are empty, no need to delete folders in user directories because they were empty / not existing until starting PowerBI and tracing problems can't be set before starting, to mention a few ....

The strangest is that on a already existing Windows 2016 Server there is no problem starting this PowerBI version. But on a Windows 2012 server I got the same problem. I am a bit lost, do I miss something (knowledge, compatibility, drivers, needed Microsoft functionality not installed yet)?

Thanks for your patience and advice and kind regards,

Aad Dijksman

[Greg_Deckler]

Right, you can post it yourself. If you have a Pro account, I would recommend opening a support ticket with Microsoft.