Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
I have recently been using the PBIP format via a GIT repo. After a change in the service, I re-Sync'd my files from the workspace and it keeps coming up with the following error when trying to reopen the file.
I've reverted to a previous version from the latest change and I'm still seeing the same issue.
I've also cleared my PBI cache folders.
Not sure what else to do.
Feedback Type:
Frown (Error)
Timestamp:
2025-04-25T07:56:48.8374273Z
Local Time:
2025-04-25T08:56:48.8374273+01:00
Session ID:
432de883-5b46-48ff-9869-d2f2b298b274
Release:
March 2025
Product Version:
2.141.1253.0 (25.03)+74f9999a1e95f78c739f3ea2b96ba340e9ba8729 (x64)
Error Message:
An error occurred while trying to open 'C:\Users\adm.martin.mcmillan\source\repos\....\'Semantic Model.pbip'. Value cannot be null.
Parameter name: Non-null assertion failure: mFormulaText
Stack Trace:
at Microsoft.PowerBI.Client.Windows.Storage.FileOpenError.HandleError(IWindowService windowService, LocalizedString title)
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:
An error occurred while trying to open 'C:\Users\adm.martin.mcmillan\source\repos\FerryPOC\Ferry Semantic Model.pbip'. Value cannot be null.
Parameter name: Non-null assertion failure: mFormulaText
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:
Value cannot be null.
Parameter name: Non-null assertion failure: mFormulaText
InnerException0.Stack Trace:
at Microsoft.PowerBI.Client.Shared.Contracts.FailArgumentNullCore(String msg)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingQueryBuilder.WithMFormulaText(String mFormulaText)
at Microsoft.PowerBI.Modeling.Engine.Query.ModelingMashupDocumentGenerator.BuildQuery(IQueryableObject obj, IModelingMashupDocumentBuilder mDocumentBuilder, Func`2 dataSourceTypeGetter, ITelemetryService telemetryService)
at Microsoft.PowerBI.Modeling.Engine.Query.ModelingMashupDocumentGenerator.BuildQueries(IDataModel dataModel, IModelingMashupDocumentBuilder mDocumentBuilder, Func`2 dataSourceTypeGetter, ITelemetryService telemetryService)
at Microsoft.PowerBI.Modeling.Engine.Query.ModelingMashupDocumentGenerator.GenerateQueriesFromModel(IDataModel dataModel, IModelingMashupDocumentBuilder mDocumentBuilder, Func`2 dataSourceTypeGetter, ITelemetryService telemetryService)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingQueriesGenerator.PopulateBuilderFromModel(IDataModel dataModel, QueriesSettings queriesSettings, ITelemetryService telemetryService)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingQueriesGenerator.GenerateRestorationInputFromModel(IDataModel dataModel, QueriesSettings queriesSettings, IMashupDiscoveryService mashupDiscoveryService, ITelemetryService telemetryService)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingQueriesGenerator.GenerateAndRestoreQueriesFromModel(Report report, IDataModel dataModel, Boolean restoreQueriesFromModel, ITelemetryService telemetryService)
at Microsoft.PowerBI.Client.Windows.Services.ReportFactory.<SetAnalysisServicesDatabaseToReport>d__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.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__57.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)
OS Version:
Microsoft Windows NT 10.0.20348.0 (x64 en-US)
CLR Version:
4.8 or later [Release Number = 528449]
Peak Virtual Memory:
70 GB
Private Memory:
279 MB
Peak Working Set:
421 MB
IE Version:
11.1.20348.0
User ID:
4d1ba516-6182-4b11-8638-924dd36eb809
Telemetry Enabled:
True
PowerBINonFatalError_ErrorCode:
InvalidReportFile
DPI Scale:
100%
Supported Services:
Power BI
Solved! Go to Solution.
Hi @martinmcmillan -
Check your GIT repo for corrupted or incomplete .m definitions:
Go to YourProjectFolder\DataModel\
Open the affected table folders (each table should have a .m file)
Look for any empty or missing .m files (especially for tables created from Query Editor or manual definitions)
Revert the DataModel and DataModelSchema folders to a working commit:
Even if you reverted the whole project, verify specifically that the *.m files are not null or blank.
Restore from a version that successfully opened before the sync/merge.
Clean and re-clone the repository:
Sometimes your local repo may cache corrupted metadata.
Delete your local repo, then re-clone from the remote, preferably from a known-good commit.
Use Power BI Desktop December 2024 or earlier:
The March 2025 update introduced more aggressive validation and may break loading PBIP projects with minor issues.
Try opening the PBIP with an older version and see if it loads.
Proud to be a Super User! | |
Hi @martinmcmillan ,
Could you please confirm if the issue has been resolved on your end? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.
Thank you for your understanding and assistance.
Hi @martinmcmillan ,
Has the issue been resolved on your end? If so, please share your solution and mark it as "Accept as Solution." This will assist others in the community who are dealing with similar problems and help them find a solution more quickly.
Thank you.
Hi @martinmcmillan ,
Thank you @rajendraongole1 for the prompt response!
I wanted to check and see if you had a chance to review my previous message or Please let me know if everything is sorted or if you need any further assistance.
Thank you.
Hi @martinmcmillan -
Check your GIT repo for corrupted or incomplete .m definitions:
Go to YourProjectFolder\DataModel\
Open the affected table folders (each table should have a .m file)
Look for any empty or missing .m files (especially for tables created from Query Editor or manual definitions)
Revert the DataModel and DataModelSchema folders to a working commit:
Even if you reverted the whole project, verify specifically that the *.m files are not null or blank.
Restore from a version that successfully opened before the sync/merge.
Clean and re-clone the repository:
Sometimes your local repo may cache corrupted metadata.
Delete your local repo, then re-clone from the remote, preferably from a known-good commit.
Use Power BI Desktop December 2024 or earlier:
The March 2025 update introduced more aggressive validation and may break loading PBIP projects with minor issues.
Try opening the PBIP with an older version and see if it loads.
Proud to be a Super User! | |
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
63 | |
59 | |
56 | |
38 | |
29 |
User | Count |
---|---|
82 | |
62 | |
45 | |
41 | |
40 |