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

Power BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.

Reply
tomordonezmiron
Frequent Visitor

Cannot open PBIP in latest release Feb 2025

Opening a PBIP file throws this popup error:

There's a problem with the definition content in your Power BI Project.
Multiple SaveChanges without transaction

 

It allows copying the details of the error which shows the following:

 

InnerException0.PowerBINonFatalError_ErrorCode:
DataModelLoadFailed

 

More details at the bottom of this post.

 

This is what I did so far:

  • Downloaded the semantic model from the PBI service which downloads as PBIX. Then save this file as PBIP into another directory.
  • Started to compare TMDL files between problem PBIP and new PBIP
  • There is a difference in the file model.tmdl
  • Problem PBIP says "annotation PBIDesktopVersion = 2.139.2054.0 (24.12)". New PBIP says "annotation PBIDesktopVersion = 2.140.1078.0 (25.02)"
  • In the problem PBIP, modified model.tmdl to what the new PBIP says
  • Now the report opens without the thrown error
  • Other PBIP files that have 2.139.2054.0 (24.12) open without issues.

That's why I think that the latest release February 2025 breaks something in TMDL, because I did not have the problem a week ago.

 

Stack Trace:
at Microsoft.PowerBI.Client.Windows.Services.BiProjectOperationHandler.<LoadFromProject>d__35.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.Services.BiProjectOperationHandler.<LoadFromPbip>d__33.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.Services.BiProjectOperationHandler.<LoadArtifact>d__28.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.Services.CurrentArtifactManager.<ExecuteAndHandleFileOpenErrors>d__55.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.Services.CurrentArtifactManager.<>c__DisplayClass36_0.<<OpenArtifactAndSetAsCurrent>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.Services.UIBlockingService.<>c__DisplayClass17_0`1.<<BlockUIAndRun>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.WaitOnUIThreadForTaskCompletion[T](Task`1 task)
at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.BlockUIAndRun[T](Func`1 asyncMethod, PowerBIProgress progress)
at Microsoft.PowerBI.Client.Windows.Services.CurrentArtifactManager.OpenArtifactAndSetAsCurrent(IPowerBIWindowService windowService, IPowerBIArtifact artifactToOpen, IExceptionHandler exceptionHandler, Nullable`1 entryPoint)
at Microsoft.PowerBI.Client.CommandLineFileService.TryOpenOrCreateReport(IPowerBIWindowService windowService, IExceptionHandler exceptionHandler, Boolean forceCreate)
at Microsoft.PowerBI.Client.Program.<>c__DisplayClass7_0.<RunApplicationLegacy>b__0()
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<>c__DisplayClass3_0.<HandleExceptionsWithNestedTasks>b__0()
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)

Stack Trace Message:
Multiple SaveChanges without transaction

Invocation Stack Trace:
at Microsoft.Mashup.Host.Document.ExceptionExtensions.GetCurrentInvocationStackTrace()
at Microsoft.Mashup.Client.UI.Shared.FeedbackErrorInfo..ctor(String message, Exception exception, Nullable`1 stackTraceInfo, String messageDetail)
at Microsoft.PowerBI.Client.PowerBIUnexpectedExceptionHandler.HandleKnownExceptions(Exception e)
at Microsoft.PowerBI.Client.PowerBIUnexpectedExceptionHandler.HandleException(Exception e)
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
at Microsoft.PowerBI.Client.Program.RunApplicationLegacy(String[] args, IPowerBIRootTrace trace)
at Microsoft.PowerBI.Client.Program.Main(String[] args)


InnerException0.Stack Trace Message:
Multiple SaveChanges without transaction

InnerException0.Stack Trace:
at Microsoft.PowerBI.Client.Windows.Services.LocalAnalysisServicesDatabaseCreator.<CreateAnalysisServicesDatabaseAsync>d__7.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.Services.BiProjectOperationHandler.<LoadFromProject>d__35.MoveNext()

InnerException0.Invocation Stack Trace:
at Microsoft.Mashup.Host.Document.ExceptionExtensions.GetCurrentInvocationStackTrace()
at Microsoft.Mashup.Client.UI.Shared.FeedbackErrorInfo.GetFeedbackValuesFromException(Exception e, String prefix)
at Microsoft.Mashup.Client.UI.Shared.FeedbackErrorInfo.GetFeedbackValuesFromInnerExceptions(Exception e, Int32 depth)
at Microsoft.Mashup.Client.UI.Shared.FeedbackErrorInfo.CreateAdditionalErrorInfo(Exception e)
at Microsoft.Mashup.Client.UI.Shared.FeedbackErrorInfo..ctor(String message, Exception exception, Nullable`1 stackTraceInfo, String messageDetail)
at Microsoft.PowerBI.Client.PowerBIUnexpectedExceptionHandler.HandleKnownExceptions(Exception e)
at Microsoft.PowerBI.Client.PowerBIUnexpectedExceptionHandler.HandleException(Exception e)
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
at Microsoft.PowerBI.Client.Program.RunApplicationLegacy(String[] args, IPowerBIRootTrace trace)
at Microsoft.PowerBI.Client.Program.Main(String[] args)


InnerException1.Stack Trace Message:
Multiple SaveChanges without transaction

InnerException1.Stack Trace:
at Microsoft.PowerBI.Modeling.Common.Contract.FailCore(String msg)
at Microsoft.PowerBI.Modeler.ModelManager.TransactionlessTransactionStrategy.SaveChanges()
at Microsoft.PowerBI.Modeler.ModelManager.InternalTransaction.<>c__DisplayClass13_1.<SaveChanges>b__2()
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.Modeler.ModelManager.InternalTransaction.Commit(Boolean recalc)
at Microsoft.PowerBI.Modeling.Engine.Authoring.AsyncModelAuthoringService.ModelAuthoringTransaction.Commit(RecalcBehavior recalcBehavior)
at Microsoft.PowerBI.Client.Windows.Modeling.Utilities.ModelChangeScopeExtensions.ExecuteAndCommitTrustedChangeAsSingleTransaction(IExtendedModelChangeScope scope, ModelChange modelChange, Boolean validateChange, RecalcBehavior recalcBehavior, String descriptionToTrace)
at Microsoft.PowerBI.Client.Windows.AnalysisServices.TmslApplier.<>c__DisplayClass4_0.<ApplySchemaChanges>b__0(IExtendedModelChangeScope scope)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.DesktopModelingHost.<>c__DisplayClass25_0.<RunOutOfBandExtendedModelChange>b__0(IExtendedModelChangeScope scope)
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.AnalysisServices.TmslApplier.<ApplySchemaChanges>d__4.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.AnalysisServices.TmslApplier.<ApplyTmsl>d__3.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.AnalysisServices.AnalysisServicesService.<LoadDatabaseFromStreamAndSchema>d__42.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.Services.LocalAnalysisServicesDatabaseCreator.<CreateAnalysisServicesDatabaseAsync>d__7.MoveNext()

InnerException1.Invocation Stack Trace:
at Microsoft.Mashup.Host.Document.ExceptionExtensions.GetCurrentInvocationStackTrace()
at Microsoft.Mashup.Client.UI.Shared.FeedbackErrorInfo.GetFeedbackValuesFromException(Exception e, String prefix)
at Microsoft.Mashup.Client.UI.Shared.FeedbackErrorInfo.GetFeedbackValuesFromInnerExceptions(Exception e, Int32 depth)
at Microsoft.Mashup.Client.UI.Shared.FeedbackErrorInfo.GetFeedbackValuesFromInnerExceptions(Exception e, Int32 depth)
at Microsoft.Mashup.Client.UI.Shared.FeedbackErrorInfo.CreateAdditionalErrorInfo(Exception e)
at Microsoft.Mashup.Client.UI.Shared.FeedbackErrorInfo..ctor(String message, Exception exception, Nullable`1 stackTraceInfo, String messageDetail)
at Microsoft.PowerBI.Client.PowerBIUnexpectedExceptionHandler.HandleKnownExceptions(Exception e)
at Microsoft.PowerBI.Client.PowerBIUnexpectedExceptionHandler.HandleException(Exception e)
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
at Microsoft.PowerBI.Client.Program.RunApplicationLegacy(String[] args, IPowerBIRootTrace trace)
at Microsoft.PowerBI.Client.Program.Main(String[] args)

 

 

1 ACCEPTED SOLUTION
otets
Advocate I
Advocate I

The issue is with your cache.abf file. My assumption is that this file not only stores your report’s local cache but also may include metadata tied to a specific Power BI version.
To resolve this:
  1. Go to the Dataset(SemanticModel)/.pbi folder.
  2. Delete the cache.abf file.
  3. Reopen your report in Power BI Desktop and refresh it from scratch.

View solution in original post

7 REPLIES 7
DavidKuhry
Frequent Visitor

Just wanted to add into this. I've had this issue a few times, and the solution offered by the others of deleting the cache.abf has not solved the issue. In fact, I really haven't been able to solve it, only work around it. I do all my dev against a workspace called "GIT Development" I then deploy that to "Development" and then to "Validation". I have GIT configured on the GIT Dev workspace and the Validation worksapce. So I end up having to disconnect GIT from GIT Dev and connect it to Validation to pull that version of the code into the workspace. Then reattached it to the normal repo, sync it, and pull it back down locally. 

 

I suspect that something I'm doing in Tabular Editor 3 while connected directly to the .pbip is causing the issue, but I have no idea what or where. 

otets
Advocate I
Advocate I

The issue is with your cache.abf file. My assumption is that this file not only stores your report’s local cache but also may include metadata tied to a specific Power BI version.
To resolve this:
  1. Go to the Dataset(SemanticModel)/.pbi folder.
  2. Delete the cache.abf file.
  3. Reopen your report in Power BI Desktop and refresh it from scratch.

Deleting cache.abf worked. Thanks.

I had the same issue, deleting cache.abf solved it. Thank you so much for the help!!! 🙂

tomordonezmiron
Frequent Visitor

I tried the same solution as seen here: Solved: Can't Open .pbip File - Microsoft Fabric Community

 

Removing the local repo and cloning again seems to work

This workaround helped because the problematic cache.abf file was removed along with the entire repository.
lbendlin
Super User
Super User

If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June 2025 Power BI Update Carousel

Power BI Monthly Update - June 2025

Check out the June 2025 Power BI update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.