Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers. Get Fabric certified for FREE! Learn more

Something Went Wrong - Trying to Refresh a Report

I am clearly not a technical person since the error report told me "We may be able to fix your problem faster if you report it on issues.powerbi.com and include these details" (which i pasted below)

 

Feedback Type:
Frown (Error)

Timestamp:
2025-01-31T20:14:26.9901665Z

Local Time:
2025-01-31T12:14:26.9901665-08:00

Session ID:
d5268893-8546-4139-9840-60a83d4cc421

Release:
February 2025

Product Version:
2.140.356.0 (25.02)+34a7eeacd0df8b5924a98d4049544cf31db4fd94 (x64)

Stack Trace:
Microsoft.PowerBI.Modeler.ModelingASOperationException
at Microsoft.PowerBI.Modeler.TomExceptionExtensions.ThrowAsModelingASOperationException(Exception ex)
at Microsoft.PowerBI.Modeler.TomExtensions.ExecuteTomOperation(Action action)
at Microsoft.PowerBI.Modeler.ModelManager.InternalTransaction.<>c__DisplayClass13_0.<SaveChanges>b__0()
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.<>c__DisplayClass9_0`1.<RunInActivity>b__0()
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.RunInActivity(ModelingActivityKind activity, Action action)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.RunInActivity[T](ModelingActivityKind activity, Func`1 action)
at Microsoft.PowerBI.Modeler.ModelManager.InternalTransaction.SaveChanges(String description)
at Microsoft.PowerBI.Modeler.ModelManager.InternalTransaction.SaveChangesForCommit(String description, Boolean recalc)
at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.ApplyQueriesToModel(IExtendedModelChangeScope modelChangeScope, ModelSchemaSyncContext modelSchemaSyncContext, DataModelSnapshot preTransactionModelSnapshot, Boolean& runRelationshipDetection, List`1& newTableColumnPairs, HashSet`1& existingTableInputs, Boolean& upgradedModel, V3UpgradeStatus& v3UpgradeStatus)
at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.<>c__DisplayClass27_0.<ApplyQueryChangesAndCreateRelationships>b__1()
at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.ExecuteInTransaction(IExtendedModelChangeScope modelChangeScope, Func`1 action)
at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.<ApplyQueryChangesAndCreateRelationships>d__27.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.<ApplyQueryChangesAndCreateRelationships>d__27.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.<ProcessLoadInputs>d__25.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.<>c__DisplayClass21_0.<<PerformLoadAsync>b__3>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.<>c__DisplayClass21_0.<<PerformLoadAsync>b__3>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.<>c__DisplayClass11_0`1.<<RunInAsyncActivity>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.<RunInAsyncActivity>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.<RunInAsyncActivity>d__11`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Modeling.Engine.Loader.LoadToReportFlow.<PerformLoadToAnalysisServices>d__15.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Modeling.Engine.Loader.LoadToReportFlow.<ExecuteInternal>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Modeling.Engine.Loader.LoadToReportFlow.<Execute>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.<>c__DisplayClass11_0`1.<<RunInAsyncActivity>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.<RunInAsyncActivity>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.<RunInAsyncActivity>d__11`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.DesktopModelingHost.<>c__DisplayClass18_0.<<LoadToModel>b__1>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Modeling.Engine.Authoring.AsyncModelAuthoringService.<>c__DisplayClass10_0.<<RunExtendedModelChangeAsync>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.PowerBI.Modeling.Engine.Authoring.AsyncModelAuthoringService.<>c__DisplayClass10_0.<<RunExtendedModelChangeAsync>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Modeling.Engine.Authoring.AsyncModelAuthoringService.<ContinueWithAsyncOperation>d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.DesktopModelingHost.<LoadToModel>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.FloatingDialog.KoLoadToReportDialog.<>c__DisplayClass44_0.<<StartLoadToReportFlow>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<HandleAwaitableAsyncExceptions>d__1.MoveNext()

PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.140.356.0","ModuleName":"Microsoft.PowerBI.Modeler.dll","Component":"Microsoft.PowerBI.Modeler.TomExceptionExtensions","Error":"Microsoft.PowerBI.Modeler.ModelingASOperationException","MethodDef":"ThrowAsModelingASOperationException - PFE_OLEDB,PFE_OLEDB,PFE_SERVERBASE_OPERATION_CANCELLED_BECAUSE_OTHER_ONE_FAILED","ErrorOffset":"17","ErrorCode":""}

InnerException0.Stack Trace:
at Microsoft.AnalysisServices.Tabular.Model.SaveChangesImpl(SaveFlags flags, Int32 maxParallelism)
at Microsoft.PowerBI.Modeler.ModelManager.InternalTransaction.<>c__DisplayClass13_1.<SaveChanges>b__2()
at Microsoft.PowerBI.Modeler.TomExtensions.ExecuteTomOperation(Action action)

OS Version:
Microsoft Windows NT 10.0.26100.0 (x64 en-US)

CLR Version:
4.8 or later [Release Number = 533320]

Peak Virtual Memory:
71.2 GB

Private Memory:
855 MB

Peak Working Set:
1.32 GB

IE Version:
11.1882.26100.0

User ID:
96cf0147-2cbe-42a3-a270-6ef9fe01e52f

Workbook Package Info:
1* - en-US, Query Groups: 3, fastCombine: Enabled, runBackgroundAnalysis: False.

Telemetry Enabled:
True

Model Default Mode:
Import

Model Version:
PowerBI_V3

Enabled Preview Features:
PBI_snowflakeAdbcVersionEnabled
PBI_sparklines
PBI_scorecardVisual
PBI_fieldParametersSuperSwitch
PBI_setLabelOnExportPdf
PBI_oneDriveSave
PBI_oneDriveShare
PBI_useModernPublishDialogs
PBI_gitIntegration
PBI_tmdlInDataset
PBI_directLakeRemoteModeling
PBI_newCard
PBI_buttonSlicerAuthoring
PBI_EimLessElevatedUser
PBI_mobileAutoReportLayout
PBI_daxInlineCopilot
PBI_aiNarrativesVisual
PBI_generateMeasureDescriptionsButton
PBI_visualCalculationsAuthoring
PBI_desktopReportAuthoringCopilot

Disabled Preview Features:
PBI_shapeMapVisualEnabled
PBI_SpanishLinguisticsEnabled
PBI_qnaLiveConnect
PBI_metricsArtifactsOnDesktop
PBI_b2bExternalDatasetSharing
PBI_enhancedTooltips
PBI_onObject
PBI_odspSaveBackgroundUpload
PBI_modernOfficeFilePicker
PBI_publishDialogsSupportSubfolders
PBI_enhancedReportFormat
PBI_advancedSlicerTypeList
PBI_textSlicer
PBI_qnaImproveLsdlCopilot
PBI_tmdlViewToggle
PBI_customCalendars
PBI_UserInstalledVerticaODBCDriver

Disabled DirectQuery Options:
TreatHanaAsRelationalSource

Cloud:
MSIT

DPI Scale:
150%

Supported Services:
Power BI

Status: Investigating

Hi, @KarolD 

Thanks for the information. When multiple queries refer to each other (append queries, merge queries, etc.), the error caused by interface/network throughput may be due to the fact that some data is not returned, which may prevent the subsequent query steps from being completed.
You can try adding the Table.buffer function in your power query to buffer the table in memory, isolating it from external changes during evaluation.

 

Best Regards

Jianpeng Li

Comments
v-jianpeng-msft
Community Support
Status changed to: Investigating

Hi, @KarolD 

Based on the information you provided, you get this error when you try to refresh Power BI desktop.
I took a closer look at the errors and I think the causes of the errors are as follows:
1. You made an error in the step in Power Query
2. Some of the data from your data source does not fit into your current Power Query step or the relationship established in Power BI desktop. This is what I think is the most likely.

If you get the above error, you should first check that the data type is correct, that the steps referenced in Power Query are correct, and that the relationships in Power BI are able to satisfy the refreshed model.

 

 

Best Regards

Jianpeng Li

KarolD
Microsoft Employee
@v-jianpeng-msft Thank you for trying to help me. All I know how to do is open the report and hit the refresh button and answer any messages that pop-up. After spending all day Thursday and Friday trying to run the refresh, I was finally able to run it after 5pm on Friday leading me to suspect it has to do with traffic on the systems the refresh is trying to access since traffic would have slowed down after work hours allowing the refresh to finally work without timing out (that was another error I received). I have a meeting set up with our IT folks and hopefully they can shed some light on it.
v-jianpeng-msft
Community Support
Status changed to: Investigating

Hi, @KarolD 

Thanks for the information. When multiple queries refer to each other (append queries, merge queries, etc.), the error caused by interface/network throughput may be due to the fact that some data is not returned, which may prevent the subsequent query steps from being completed.
You can try adding the Table.buffer function in your power query to buffer the table in memory, isolating it from external changes during evaluation.

 

Best Regards

Jianpeng Li

KarolD
Microsoft Employee
Thanks for the suggestion. I was able to meet with some IT folks and we have a timeline for them to take over the refresh at the end of the month 🙂 So I only need to struggle with it for the next 3 weeks.