Forum Discussion
ERROR: Calendar Visual by MAQ Software showing error message
Hi, I used this visual for a couple of weeks and working fine. this last week I got this error and I can't find a solution.
Feedback Type:
Frown (Error)
Timestamp:
2026-02-25T13:55:27.1001158Z
Local Time:
2026-02-25T13:55:27.1001158+00:00
Session ID:
f2737b98-365b-4d46-b470-b949b6ab4882
Release:
February 2026
Product Version:
2.151.1052.0 (26.02)+f24ef72a680490da641de392ea586cef1b10bfc8 (x64)
Error Message:
An error occurred while rendering the report.
Stack Trace:
Javascript:TypeError
at SandboxDelegate.persistProperties (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:3036206)
at SandboxVisualProxy.onMessageReceived (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:12686173)
at https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:12681723
at MessageChannelProxy.invokeHandler (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:2854412)
at MessageChannelProxy.dispatchMessage (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:2854294)
at MessageChannelProxy.onMessageReceived (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:2853959)
at e.source._peerWindow._peerOrigin.e.origin._peerOrigin.e.data.type.e.data.nonce._handshakeNonce._peerPort.onmessage (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:2852283)
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.Client.UI.Shared.UnexpectedExceptionHandler.HandleException(Exception e)
at Microsoft.PowerBI.Client.PowerBIUnexpectedExceptionHandler.HandleException(Exception e)
at Microsoft.PowerBI.Client.Windows.Utilities.PowerBIFormUnexpectedExceptionHandler.HandleException(Exception e)
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.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at Microsoft.PowerBI.Client.Windows.WebView2.WebView2Interop.<>c__DisplayClass36_0.<InvokeCsMethod>b__0()
at Microsoft.PowerBI.Client.Windows.WebView2.WebView2Interop.<>c__DisplayClass39_0`1.<RunAsync>b__0(Object s)
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)
...
Hi!! You’re likely running into a known compatibility issue between the MAQ Calendar visual and the February 2026 version of Power BI Desktop.
The stack trace (Javascript: TypeError at SandboxDelegate.persistProperties) usually indicates the custom visual is failing inside the Power BI sandbox during rendering, not that there’s something wrong with your data model. This commonly happens when Power BI updates WebView2 or the visual sandbox and the custom visual hasn’t been updated to match.
In most cases, the fix is to update or reinstall the MAQ visual from AppSource. If the latest version is already installed and the issue persists, it’s very likely a visual-side bug that needs to be addressed by the MAQ developers.
As a quick sanity check, you can also try placing only Start Date, End Date, and Subject into a fresh MAQ visual. If it still fails, that further confirms it’s not your data but the visual compatibility.
Hope that help!
best regards!Thank you, I am having the same issue since yesterday. Let me add more info:
* The visual is updated to the latest build* The sample pbix that the provider (MAQ Software) have on the Marketplace have the same issue --> So no data issue applies
* I tried with two versions of PBI Desktop (Portal app and MSI version)
* More colleagues are having the same issue with different pbix and different machines.
Since this visual is PBI certified and this change comes from Microsoft, Microsoft should contact MAQ Software to solve this issue ASAP.Thanks
6 Replies
RicardoTraNaResponsive Resident
Hi!! You’re likely running into a known compatibility issue between the MAQ Calendar visual and the February 2026 version of Power BI Desktop.
The stack trace (Javascript: TypeError at SandboxDelegate.persistProperties) usually indicates the custom visual is failing inside the Power BI sandbox during rendering, not that there’s something wrong with your data model. This commonly happens when Power BI updates WebView2 or the visual sandbox and the custom visual hasn’t been updated to match.
In most cases, the fix is to update or reinstall the MAQ visual from AppSource. If the latest version is already installed and the issue persists, it’s very likely a visual-side bug that needs to be addressed by the MAQ developers.
As a quick sanity check, you can also try placing only Start Date, End Date, and Subject into a fresh MAQ visual. If it still fails, that further confirms it’s not your data but the visual compatibility.
Hope that help!
best regards!Thank you, I am having the same issue since yesterday. Let me add more info:
* The visual is updated to the latest build* The sample pbix that the provider (MAQ Software) have on the Marketplace have the same issue --> So no data issue applies
* I tried with two versions of PBI Desktop (Portal app and MSI version)
* More colleagues are having the same issue with different pbix and different machines.
Since this visual is PBI certified and this change comes from Microsoft, Microsoft should contact MAQ Software to solve this issue ASAP.Thanks
Hi SantiLuquez ,
Thank you RicardoTraNa for the response provided!
Has your issue been resolved? If the response provided by the community member addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.
Thank you.Hi SantiLuquez ,
I wanted to follow up and see if you had a chance to review the information shared. If you have any further questions or need additional assistance, feel free to reach out.
Thank you.
I have the same problem
Hi Fabric Community,
I reached out to MAQ Software and received the below response. Thought I'd share here with everyone else facing this issue:
Thank you for reaching out. We apologize for the disruption caused by the calendar visual issue in the February 2026 Power BI Desktop update. Our team has confirmed that the issue is limited to this release, and earlier versions continue to work as expected. We are actively working on a fix and will release an updated version to Microsoft AppSource soon.
In the meantime, please use one of the following workarounds:
Option 1: Power BI Service [Recommended]
The issue does not occur in the Power BI service (web version). You can continue editing reports and configuring the visual without interruption.
Option 2: Install an Older Power BI Desktop Version
If you prefer working locally, uninstall the current build and revert to the January 2026 version (or earlier).
We appreciate your patience while we work toward a resolution. If you have any questions or need assistance, please reply to this email—we’re happy to help.
