Hi folks,
I found some issues here with 2016 date related to 'An error occurred while rendering the report.' and old versions of Power BI Desktop. So, I'm facing the message 'An error occurred while rendering the report.' in '.pbix' files that using Hierarchy Slicer complement after Power BI update to July 2017 version - 2.48.4792.721 (PBIDesktop) (x64). I tested with Hierarchy Slicer versions 0.7.9 and the most updated version 1.0.3.0 and the issue occur to both. I executed some fix steps posted in related issues and only removing this complement fix. I saw the same issue with R Power Visual - PowerBI-visuals-forcasting-ARIMA.1.0.1 but in this case the prediction is in test and not cause impact to data customer. Do you know any other way to solve this issue without remove Hierarchy Slicer from '.pbix' file?
Ps. I tried the step below but without success.
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
-------------------------------------------------------- Error print
-------------------------------------------------------- Error log
Feedback Type:
Frown (Error)
Timestamp:
2017-07-26T15:45:42.5244369Z
Local Time:
2017-07-26T12:45:42.5244369-03:00
Product Version:
2.48.4792.721 (PBIDesktop) (x64)
Release:
July 2017
IE Version:
11.1007.10586.0
OS Version:
Microsoft Windows NT 10.0.10586.0 (x64 en-US)
CLR Version:
4.6.1 or later [Release Number = 394254]
Workbook Package Info:
1* - en-US, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: True.
Peak Working Set:
347 MB
Private Memory:
234 MB
Peak Virtual Memory:
33.7 GB
JS Error Message:
Script error.
Error Message:
An error occurred while rendering the report.
Stack Trace:
Microsoft.Mashup.Host.Document.JavaScriptException: An error occurred while rendering the report.
at :line 0
Invocation Stack Trace:
at Microsoft.Mashup.Host.Document.ExceptionExtensions.GetCurrentInvocationStackTrace()
at Microsoft.Mashup.Client.ClientShared.StackTraceInfo..ctor(String exceptionStackTrace, String invocationStackTrace)
at Microsoft.Mashup.Client.ClientShared.FeedbackErrorInfo..ctor(String message, Nullable`1 errorCode, String requestId, Exception exception)
at Microsoft.Mashup.Client.ClientShared.UnexpectedExceptionHandler.<>c__DisplayClass1.<HandleException>b__0()
at Microsoft.Mashup.Host.Document.SynchronizationContextExtensions.<>c__DisplayClass3.<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.ClientShared.WindowManager.ShowDialog[T](T form, IWin32Window owner)
at Microsoft.PowerBI.Client.Program.<>c__DisplayClassd.<Main>b__0()
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
at Microsoft.PowerBI.Client.Program.Main(String[] args)
1 ACCEPTED SOLUTION
Hi everyone,
I see more people in other forums with the same issue. Looking in the app provider page, I could read some interesting information, It seems there is an issue with Hierarchy Slicer that will be fixed in the next release according app provider:
You can read all information in the app provider page:
