Since Power BI April 2019 update can´t open PBIX file - error: A circular dependency was detected

[Anonymous]

Since the Power BI April update we can't open a PBIX-file anymore, also the published version of the solution in the online Power BI service won't refresh anymore. No changes are made in the solution before the error occured. The problem started first in the Power BI service on the 23th of march 2019. The scheduled refresh of the model lead to the error "A circular dependency was detected". After the Power BI desktop update in the beginning of April we can't open the PBIX-file anymore in Power BI desktop, so now we can't access our solution to examine the circular dependency error.

Below I posted the error message when I try to open the PBIX-file in Power BI desktop. Power BI desktop won't open the file and only gives the error below. The version of the solution in the Power BI service is the same as the PBIX-file we tried to open with Power BI desktop, we can't upload/publish the PBIX to the online Power BI service because Power BI desktop won't open the file.

Please advise, 

Greetings Ronald

Feedback Type:
Frown (Error)

Timestamp:
2019-04-16T09:43:08.4844302Z

Local Time:
2019-04-16T11:43:08.4844302+02:00

Session ID:
cd53e91d-acc2-4d38-8364-de04813d3d5e

Release:
April 2019

Product Version:
2.68.5432.661 (19.04) (x64)

Stack Trace:
at Microsoft.AnalysisServices.Tabular.Model.SaveChanges(SaveOptions saveOptions)
at Microsoft.PowerBI.Modeler.ModelManager.SaveChanges(String description)
at Microsoft.PowerBI.Modeler.ModelManager.InternalTransaction.Commit(Boolean recalc)
at Microsoft.PowerBI.Client.Windows.Modeling.AsyncModelAuthoringService.ModelAuthoringTransaction.<Commit>b__14_0()
at Microsoft.PowerBI.Client.Windows.Modeling.ModelAuthoringExceptionHandler.AddModelChangeResultToExceptions(Action action, ModelChangeResult modelChangeResult)
at Microsoft.PowerBI.Client.Windows.Modeling.AsyncModelAuthoringService.ModelAuthoringTransaction.Commit()
at Microsoft.PowerBI.Client.Windows.ReportUpgrader.<>c__DisplayClass3_0.<Upgrade>b__0(IExtendedModelChangeScope scope)
at Microsoft.PowerBI.Client.Windows.Modeling.AsyncModelAuthoringService.RunOutOfBandExtendedModelChange(Action`1 extendedModelChange, IAnalysisServicesDatabase analysisServicesDatabase, IModelManager modelManager, Boolean requireASDBToBeUnattached)
at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesDatabaseLocal.RunOutOfBandExtendedModelChangeCore(Action`1 extendedModelChange, Boolean requireASDBToBeUnattached)
at Microsoft.PowerBI.Client.Windows.ReportUpgrader.Upgrade(Report report, String fileName, Version pbixFileVersion)
at Microsoft.PowerBI.Client.Windows.ReportPreparer.UpgradeModel(Report report, IPowerBIWindowService windowService, String fileName, Version pbixFileVersion)
at Microsoft.PowerBI.Client.Windows.ReportPreparer.Prepare(Report report, PackageValidationResult mashupResult, IPowerBIWindowService windowService, String fileName, Nullable`1 entryPoint, Version pbixFileVersion)
at Microsoft.PowerBI.Client.Windows.Services.PowerBIPackagingService.Open(FileStream fileStream, IPowerBIWindowService windowService, Nullable`1 entryPoint, PowerBIPackageOpenOptions options, ReportPreparerResult& prepareResult)
at Microsoft.PowerBI.Client.Windows.Services.FileManager.<LoadFromPbix>d__20.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__DisplayClass15_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(Task task)
at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.BlockUIAndRun[T](Func`1 asyncMethod)
at Microsoft.PowerBI.Client.Windows.Services.FileManager.OpenFile(IPowerBIWindowService windowService, IPbixFile fileToOpen, Nullable`1 entryPoint)
at Microsoft.PowerBI.Client.Program.TryOpenOrCreateReport(IUIHost uiHost, ISplashScreen splashScreen, IFileManager fileManager, IFileHistoryManager fileHistoryManager, String filePath, FileType fileType)
at Microsoft.PowerBI.Client.Program.<>c__DisplayClass4_0.<Main>b__1()
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<>c__DisplayClass3_0.<HandleExceptionsWithNestedTasks>b__0()
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)

OS Version:
Microsoft Windows NT 10.0.17134.0 (x64 nl-NL)

CLR Version:
4.7 or later [Release Number = 461808]

Peak Virtual Memory:
37.3 GB

Private Memory:
153 MB

Peak Working Set:
237 MB

IE Version:
11.165.17134.0

User ID:
cc521f09-037a-4415-9c02-ac0a7c855048

Telemetry Enabled:
True

DPI Scale:
100%

Supported Services:
Power BI

[Anonymous]

I have the same issue.

[chris_e]

Same issue here.

[v-yulgu-msft]

Hi @Anonymous ,

I could not reproduce this problem on my side, with the latest desktop version: Version: 2.68.5432.761 64-bit (April 2019). Did you install this version?

Would you please send me a sample .pbix file which cannot be opened? Remember to avoid loading sensitive data into the shared .pbix file.

Best regards,

Yuliana Gu

[Anonymous]

same issue with version  2.75.5649.582 64-bit (November 2019)

@v-yulgu-msft