Problem with November 2024 update for PowerBI Reports - circular Dependency Issue

[MarkB63]

After the Nover 11 2024 update occurred,  all my projects are giving me a circular dependency errors when I first open them.  The Projects still open, but I have no clue what I might need to fix or what this is affecting.  I believe it may have to do with a DAX calculated date table using CALENDARAUTO(), but not 100% sure - An example of the error is shown below.

 I rolled back to October update and everything opens fine, no errors.

Please fix this issue for us asap.  I've seen posts about this on redit as well

Example:

Thanks

[Anonymous]

Hi @MarkB63 ,

Based on the above information, It's a reproducible issue. I would suggest opening a Support Ticket.

If you are a Power BI Pro or Fabric licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you. 
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.

The link of Power BI Support: Support | Microsoft Power BI

For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Power BI Community

Best Regards,
Community Support Team _ Caitlyn

[SokuTaIke]

We have the exact same problem at our company since the update! With existing and new reports! Sometimes it works when I delete the measure, column or table and write the (exact same) DAX over again. It happens mostly with variables and date tables.

[Voith]

I am having the same issue with our exsiting reports.  Reverting to the October version removed the error and the reports are running properly.  The error is also refrencing our CALANDERAUTO() table's [Date] column.

[Date], 216169d0-b336-c864-b81a-4558f99ac68a, [Date], and [Date]

Update:  I submitted a ticket.  They sent me a link to it being a current known issue (887-semantic-model-refresh-fails-circular-dependency). 

Essentially, you need to switch CALENDARAUTO() to CALENDAR(DATE (2015, 1, 1), DATE (2021, 12, 31)) (use your own dates) as a quick fix.  They said it would be fixed in the next update.

[MarkB63]

Thanks for the update.  For now rather than accomodating my project(s) to their bug, I rolled back to the October update and am no longer having issue.  guess I will wait for the next update to see if it is in fact fixed.

[selimscmr]

Hi, We are having the same error.  I cannot find a download for the october version.  Can you please share how your rolled back to the october version?
Thanks so much!

[MarkB63]

I found it in the link that follows.  I had to uninstall the version I had from the microsoft store first ... Good luck!  https://learn.microsoft.com/en-us/power-bi/fundamentals/desktop-latest-update-archive?tabs=powerbi-d...

[selimscmr]

Thank you @MarkB63 

[dgonzalezc]

i have the same issue from this version. i cann't modify any item of my reports by a "circulan dependency detected" 

[MarkB63]

It's a frustrating issue for sure.  I heard it would be addressed in Dec update, guess we will see.  For now I simply uninstalled my current version of PBI desktop, and reinstalled the one as of Oct.  I provided a link to that in the comments in case you are interested.  There could have been other ways to handle, but I am managing 6 projects that were all affected so this was the easiest way for me.  Good luck!!

[godwilltochukwu]

Feedback Type:
Frown (Error)

Timestamp:
2024-12-10T11:50:25.8721965Z

Local Time:
2024-12-10T03:50:25.8721965-08:00

Session ID:
2b26031f-7f1b-4439-a492-f84f162bee79

Release:
August 2024

Product Version:
2.132.1053.0 (24.08) (x64)

Stack Trace:
Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesProcessUnexpectedExitException
at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesProcess.AcquireServerDynamicPortInfo()
at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesProcess.EnsureServiceIsReady()
at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesProcess.Start()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesService.<StartProcess>d__30.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.PowerBI.Client.Windows.Utilities.AggregateExceptionHandlingExtensions.WaitAndUnpackException(Task task)
at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesService.CreateEmptyDatabase()
at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesService.<StartProcess>d__30.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.132.1053.0","ModuleName":"Microsoft.PowerBI.Client.Windows.dll","Component":"Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesProcess","Error":"Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesProcessUnexpectedExitException","MethodDef":"AcquireServerDynamicPortInfo","ErrorOffset":"110","ErrorCode":""}

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

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

Peak Virtual Memory:
70.1 GB

Private Memory:
234 MB

Peak Working Set:
566 MB

IE Version:
11.1.22621.0

User ID:
1e0e94c0-239e-428f-9540-b25f726fb7f9

Workbook Package Info:
None

Telemetry Enabled:
True

DPI Scale:
125%

Supported Services:
Power BI