Forum Discussion
Non-null assertion failure: "Value cannot be null"
I'm running into this consistent issue. I save a .pbip file against a custom connector with a very basic query. If I then close PowerBI and reopen it, the first time I attempt to open the file I get this assertion. (I'll attach the details at the bottom). If I then - without closing PowerBI - attempt to open the .pbip file again it'll work. But if I close PowerBI and attempt to open it from scratch it fails.
Below are the copied details. Any help would be appreciated.
Feedback Type:
Frown (Error)
Timestamp:
2026-06-09T15:57:43.0492471Z
Local Time:
2026-06-09T11:57:43.0492471-04:00
Session ID:
2a2beb4e-7cbd-448f-9b6e-0d0d8d1bcf6b
Release:
June 2026
Product Version:
2.155.756.0 (26.06)+7f1da5803bfe48beff98093405280405ddb467dd (x64)
Stack Trace:
System.ArgumentNullException
at Microsoft.PowerBI.Modeling.Common.Contract.FailArgumentNullCore(String msg)
at Microsoft.PowerBI.Client.Windows.QueryFolding.FoldedArtifactsGenerator.GenerateFoldedArtifactsForQueriesWithoutCache(Report report, IDataModel model, IExceptionHandler exceptionHandler, IPowerBIWindowService windowService)
at Microsoft.PowerBI.Client.Windows.Services.FileOperationUIHandler.<ExecuteOpenAndApplyCore>d__54.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.FileOperationUIHandler.<OpenFileInternal>d__52.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.155.756.0","ModuleName":"Microsoft.PowerBI.Modeling.Common.dll","Component":"Microsoft.PowerBI.Modeling.Common.Contract","Error":"System.ArgumentNullException","MethodDef":"FailArgumentNullCore","ErrorOffset":"28","ErrorCode":""}
OS Version:
Microsoft Windows NT 10.0.26200.0 (x64 en-US)
CLR Version:
4.8 or later [Release Number = 533509]
Peak Virtual Memory:
85.9 GB
Private Memory:
484 MB
Peak Working Set:
616 MB
IE Version:
11.1882.26100.0
User ID:
da4eedd9-8185-4d92-8c6f-2e6cd39ac179
Workbook Package Info:
1* - en-US, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: False.
Telemetry Enabled:
True
Model Default Mode:
Empty
Model Version:
PowerBI_V3
Enabled Preview Features:
PBI_DatabricksAdbcVersionEnabled
PBI_googleBigQueryAdbcVersionEnabled
PBI_scorecardVisual
PBI_setLabelOnExportPdf
PBI_oneDriveSave
PBI_oneDriveShare
PBI_useModernPublishDialogs
PBI_gitIntegration
PBI_tmdlInDataset
PBI_enhancedReportFormat
PBI_advancedSlicerTypeList
PBI_aiNarrativesVisual
PBI_copilotUnifiedTooling
MashupFlight_EnableOracleBundledOdacProviderV2
PBI_sqlDbNativeArtifactsOnDesktop
PBI_warehouseSnapshotArtifactsOnDesktop
PBI_DesktopNamedPipeBridge
Disabled Preview Features:
PBI_UseRedshiftODBCV2
PQ_UseBaseViewXmlForSharePoint
PBI_snowflakeLegacyOdbcVersionEnabled
PBI_SpanishLinguisticsEnabled
PBI_qnaLiveConnect
PBI_b2bExternalDatasetSharing
PBI_onObject
PBI_publishDialogsSupportSubfolders
PBI_enhancedReportFormatPBIX
PBI_useModernMashupEditor
PBI_customCalendars
PBI_enableOracleBundledOdacProviderForDQ
PBI_dynamicCalcColumn
PBI_newVisualDefaults2026
PBI_enableExportQueries
PBI_dateSlicerPreselectionAuthoring
Disabled DirectQuery Options:
TreatHanaAsRelationalSource
Cloud:
GlobalCloud
DPI Scale:
150%
Supported Services:
Power BI
WebView2 Runtime Version:
149.0.4022.52
WebView2 SDK Version:
1.0.2365.46
Hi jzkirtley
This is a Power BI Desktop June 2026 bug with .pbip files and custom connectors.
You can do some workarounds-
1.Keep Power BI Desktop open: Once you’ve opened the file successfully in a session, avoid closing/reopening until you’re done.
2. Rollback to May 2026 build: If you need stability, install the May build (2.154.x) — this issue doesn’t occur there.
3. Use PBIX instead of PBIP: If you don’t need Git integration, saving as .pbix avoids the folded artifacts path entirely.
4. Disable preview features: Some users reported fewer crashes after disabling PBI_gitIntegration and PBI_tmdlInDataset in Options → Preview Features.
Log a bug: Use Help → Send Feedback →so the Power BI team can track it. Include your connector details and the repro steps you shared.
If this reply helped, please mark it as a solution .a kudos would mean a lot! It encourages contributors and keeps the community strong.
Thank You
Sunita
3 Replies
Hi jzkirtley
This is a Power BI Desktop June 2026 bug with .pbip files and custom connectors.
You can do some workarounds-
1.Keep Power BI Desktop open: Once you’ve opened the file successfully in a session, avoid closing/reopening until you’re done.
2. Rollback to May 2026 build: If you need stability, install the May build (2.154.x) — this issue doesn’t occur there.
3. Use PBIX instead of PBIP: If you don’t need Git integration, saving as .pbix avoids the folded artifacts path entirely.
4. Disable preview features: Some users reported fewer crashes after disabling PBI_gitIntegration and PBI_tmdlInDataset in Options → Preview Features.
Log a bug: Use Help → Send Feedback →so the Power BI team can track it. Include your connector details and the repro steps you shared.
If this reply helped, please mark it as a solution .a kudos would mean a lot! It encourages contributors and keeps the community strong.
Thank You
Sunita
Hi jzkirtley
Thank you for submitting your question to the Microsoft Fabric Community Forum, and thanks to trivedisunita for sharing helpful suggestions.
Could you let us know if the suggested solution resolved your issue? If not, please share any additional details so we can assist further.
Best regards,
Community Support Team.Hi jzkirtley
We would like to confirm whether the issue has been resolved. If it is still outstanding, please share any additional information so we can assist you further.
Thank you.
