Forum Discussion
Random Error Being Thrown
I am a relatively new Power BI user and was working with the data I was given for my internship. They have had me import their data from Snowflake and I began by manipulating the relationships. I did merge some queries so that I could relate all the data by one similar column into a single data sheet creating a "star schema" rather than a "snowflake schema". This seemed to be going well until I attepted to create a visual when it threw me an error. I copied the error and asked for a summary from copilot and it said the check that I was not using unsupported query operations. So just to be safe, I unmerged the queries and created relationships that accomplished the same thing. It continued to throw me errors, so I came here. My working theory is that it has to do with the date tabel I am using. The following message is the current error I'm being given:
Feedback Type:
Frown (Error)
Timestamp:
2025-06-04T12:46:37.2742986Z
Local Time:
2025-06-04T08:46:37.2742986-04:00
Session ID:
d8dd29e0-6448-46b0-8c06-5de8e2183ec2
Release:
May 2025
Product Version:
2.143.1204.0 (25.05)+23c84aace645781dd62b8a26eb0418c7e6a84b72 (x64)
Stack Trace:
Microsoft.Mashup.Host.Document.SerializedException
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.Mashup.OleDbProvider.DataHost.NonBufferingMashupEvaluator.MashupEvaluation.OnEvaluationComplete(AsyncResult`1 result)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.Mashup.OleDbProvider.MashupCommandEvaluation.get_PageReader()
at Microsoft.Mashup.OleDbProvider.TracingRowset.Microsoft.OleDb.IEvaluationResultSource.WaitForResults()
PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.143.1204.0","ModuleName":"","Component":"Microsoft.Mashup.OleDbProvider.DataHost.NonBufferingMashupEvaluator.MashupEvaluation","Error":"Microsoft.Mashup.Host.Document.SerializedException - Microsoft.Mashup.Evaluator.Interface.ErrorException","MethodDef":"OnEvaluationComplete","ErrorOffset":"","ErrorCode":""}
OS Version:
Microsoft Windows NT 10.0.22631.0 (x64 en-US)
CLR Version:
4.8 or later [Release Number = 533320]
Peak Virtual Memory:
71 GB
Private Memory:
911 MB
Peak Working Set:
1.3 GB
IE Version:
11.1.22621.0
User ID:
c2ad3e8b-f693-479a-9a38-502ec8a13cc2
Workbook Package Info:
1* - en-US, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: False.
Telemetry Enabled:
True
Model Default Mode:
DirectQuery
Model Version:
PowerBI_V3
Enabled Preview Features:
PBI_snowflakeAdbcVersionEnabled
PBI_sparklines
PBI_scorecardVisual
PBI_fieldParametersSuperSwitch
PBI_setLabelOnExportPdf
PBI_oneDriveSave
PBI_oneDriveShare
PBI_odspSaveBackgroundUpload
PBI_modernOfficeFilePicker
PBI_useModernPublishDialogs
PBI_gitIntegration
PBI_tmdlInDataset
PBI_directLakeRemoteModeling
PBI_newCard
PBI_buttonSlicerAuthoring
PBI_EimLessElevatedUser
PBI_daxInlineCopilot
PBI_aiNarrativesVisual
PBI_generateMeasureDescriptionsButton
PBI_visualCalculationsAuthoring
PBI_copilotUnifiedTooling
PBI_UserInstalledVerticaODBCDriver
PBI_sqlDbNativeArtifactsOnDesktop
Disabled Preview Features:
PBI_googleBigQueryAdbcVersionEnabled
PBI_shapeMapVisualEnabled
PBI_SpanishLinguisticsEnabled
PBI_qnaLiveConnect
PBI_metricsArtifactsOnDesktop
PBI_b2bExternalDatasetSharing
PBI_enhancedTooltips
PBI_onObject
PBI_publishDialogsSupportSubfolders
PBI_enhancedReportFormat
PBI_directLakeOnOneLake
PBI_advancedSlicerTypeList
PBI_textSlicer
PBI_qnaImproveLsdlCopilot
PBI_tmdlViewToggle
MashupFlight_EnableOracleBundledOdacProvider
PBI_dataFunctionActions
Disabled DirectQuery Options:
TreatHanaAsRelationalSource
Cloud:
GlobalCloud
DPI Scale:
150%
Supported Services:
Power BI
WebView2 Runtime Version:
136.0.3240.92
WebView2 SDK Version:
1.0.2365.46
Update: The problem only is thrown whenever I apply a filter that restricts the dates that are being looked at.
I am unsure of how I could of fixed on the model that was originally referenced in this question. What I did after experiencing this problem and not having any luck with the adivice I was given was try to use one of my compay's already existing datasets with similar data. This went well until I started getting thrown errors again, this time when I uploaded my data to Service. If you check my profile you'll see another post that occurred about a week after this one about this. So I followed the advice that was given in that post and deleted the data that was originally in the data set so that I could switch to Import storage and the reupload the data that had to be deleted. I wasn't too sure whther this would work since the date data table and many others that were giving me problems from when I posted this post would have to uploaded again, but it did. I know this likely won't help many situations, but if you're in a similar situation don't be afraid to save what you have and work on a copy of your work or restart and try different storage modes to see if your issue persists. Also, don't be afraid to post on here often. Everyone is so hknowledgable, helpful, and willing to look your way.
7 Replies
Hi Anonymous ,
Thanks for sharing the detailed error and context. These kinds of random errors in Power BI, especially when working with large or complex datasets, can be tricky to diagnose. Here are some steps and suggestions to help you narrow down and potentially resolve the issue:
Check for Data Type and Relationship Mismatches:
The error message references evaluation and relationship issues. Double-check that all your relationships are correctly defined and that data types match between related columns (for example, no text-to-number mismatches).Look for Duplicate or Ambiguous Relationships:
If the same column is used in multiple relationships, or there are inactive/ambiguous relationships, Power BI can throw odd errors. Try deactivating non-essential relationships and test again.Update Power BI and Data Sources:
Make sure you are using the latest version of Power BI Desktop and that all data connectors/drivers are up to date.Clear Cache and Re-import:
Sometimes, Power BI’s cache gets corrupted. Try clearing the cache (File > Options and settings > Options > Data Load > Clear cache) and reload your data.Simplify the Model:
If possible, temporarily remove some tables or relationships and see if the issue persists. This can help isolate the problematic area.Check for Special Characters or Unusual Data:
Sometimes, hidden characters or extremely large/complex values in the data can cause evaluation errors. Look for any such anomalies in your source data.Review Applied Steps:
Go through your Power Query “Applied Steps” one by one to see if a particular transformation is causing the error.Look for Known Issues:
Occasionally, new Power BI updates introduce bugs. Check the official Power BI community or support page for any known issues matching your error.
If you can share more about your data model structure or the specific steps that lead to the error, I can help with more targeted advice.
Let me know if any of these steps help or if the error message changes after troubleshooting.
translation and formatting supported by AIHi Anonymous,
Thanks for reaching out to the Microsoft fabric community forum and for the detailed breakdown. It seemd the root cause is related to how the date filter interacts with the DirectQuery model and possibly the date table’s relationships or transformations. As burakkaragoz have already responded to your query with trouble-shooting steps, kindly go through them and check if your issue gets resolved.
Apart from the mentioned steps, also go through:
* Try creating a duplicate of your current date table and use that in your visual or as a disconnected slicer to see if the problem persists. If the error disappears, the issue could be with the relationship or calculated columns in your original date table. This tests if the issue lies specifically within the date table logic or relationship.* Check for Auto-Date/Time in Power BI Settings. In Power BI Desktop, go to Options -> Data Load, and disable the "Auto Date/Time" option. It sometimes causes hidden relationships and conflicts in DirectQuery models, especially when date fields are reused in multiple visuals. This setting is usually overlooked and can cause unexpected filtering behaviors in DirectQuery.
If none of the above help, at this point it may be worth opening a support ticket with Microsoft. Since it's tied to DirectQuery evaluation and only breaks on date filtering, they might be able to capture backend traces that aren't visible through the UI.
Please refer below link on how to raise a contact support or support ticket.
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft LearnI would also take a moment to thank burakkaragoz, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support TeamIf this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Hi Anonymous,
As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or were you able to raise a support ticket with Microsoft Fabric Support?
If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.
If so, it would be really helpful for the community if you could mark the answer that helped you the most. If you're still looking for guidance, feel free to give us an update, we’re here for you!
I am unsure of how I could of fixed on the model that was originally referenced in this question. What I did after experiencing this problem and not having any luck with the adivice I was given was try to use one of my compay's already existing datasets with similar data. This went well until I started getting thrown errors again, this time when I uploaded my data to Service. If you check my profile you'll see another post that occurred about a week after this one about this. So I followed the advice that was given in that post and deleted the data that was originally in the data set so that I could switch to Import storage and the reupload the data that had to be deleted. I wasn't too sure whther this would work since the date data table and many others that were giving me problems from when I posted this post would have to uploaded again, but it did. I know this likely won't help many situations, but if you're in a similar situation don't be afraid to save what you have and work on a copy of your work or restart and try different storage modes to see if your issue persists. Also, don't be afraid to post on here often. Everyone is so hknowledgable, helpful, and willing to look your way.
