Exchange calendar not syncing in macOS Monterey 12.3

I'm no longer seeing the issue since upgrading to 12.4.

Thanks,

Jonathan

At work they commonly use this command to get Calendar unstuck

pkill -9 -i calendar

This is just a lower-tech version of Jonathan's solution, but I find that unchecking Mail for the account in Internet Accounts, waiting for the events to disappear from Calendar, and then checking it again causes it to start syncing again...temporarily.

I’m having the same issue. A reboot fixes it for awhile but if I sleep my MacBook for an extended period of time the issue re-emerges and needs another reboot.

one other comment, my iOS devices aren’t having this issue and calendar sync is working there. It’s just the macOS device.

I gave up and purchased BusyCal which works beautifully. At times it will sync faster than the desktop MS Outlook client! It's not worth the grief trying to get macOS calendar to work with Exchange, when BusyCal 'just works.'

You can type that into the Terminal app.

Upgrading to 12.4 fixed the issue for me so those commands are no longer needed. You might consider upgrading.

Jonathan

Our whole company suffers from this issue. With Monterey, we were able to delete the calendar cache in case the sync issues started, but it seems as if the cache file got moved. This issue is not valid for Catalina and other 3rd party apps like Fantastical do not have any problems on Ventura.

Apple, this is a clear-cut bug. Please fix!

I gave these steps a try: https://appletoolbox.com/calendar-app-slow-macos-monterey/

I still have this issue on Monterey 12.3.1. I can fix it for a while by removing the Internet Account and re adding it, but it happens again after a few days.

I updated to 12.6 a couple of days ago and confirming the bug still occurs. Tricky one since after a restart it always seems to work just fine, not sure if its a length of time that occurs before it shows up or if some kind of event like say someone modifying an existing event or deleting an event causes the sync hang up to occur. But here I am on 12.6 and still having to use the terminal fix. not even sure we'll get a 12.7 or other update ahead of 13 launch next month but hopefully fixed no later than that.

Most recent MacOS update seems to have fixed this for me.

The stop/start of com.apple.CalendarAgent used to work well for me. I had even wrapped it into an Automator app which I could just click on. In macOS Ventura, the problem still exists, but there is no com.apple.CalendarAgent anymore to stop/start :( Anyone know what the new analogue in Ventura is? What's the background agent doing calendar sync?

What the?! I had no idea. My Mac running Ventura is NOT the Mac that stops syncing. In my situation it's the Mac still on Monterey but hopefully someone will post what the new calendarAgent is.

Looking at my Monterey Mac, CalendarAgent is an Executable in the Private Frameworks: /System/Library/PrivateFrameworks/CalendarAgent.framework

Looking through the various Frameworks in Ventura for the Calendar, I don't see any executables now so maybe that is why its process doesn't show up in Activity Monitor and of course isn't found via the Terminal command.

I doubt that it is the CalendarWidgetExtension or the com.apple.CalendarWeatherKitService. I'm not seeing any activity in Activity Monitor when adding and syncing events between the two computers.

BUT MAYBE this could be it?!

There is a CalendarDaemon now in the PrivateFrameworks and the process it runs is called "calaccessd"

I'm not sure launchctl to stop and run should be calaccessd (/System/Library/PrivateFrameworks/CalendarDaemon.framework/Support/calaccessd)

But I think that is likely the best place to start.

I'm amending my reply here to say - do what BobHarris, above, says - that'll kill all processes containing [c|C]alendar. I'm not sure whether killing CalNCService or CalendarAgent did the trick; BobHarris's approach gets them both.

I am on 12.6 and it does appear to be working properly for me now. But I've thought that with other updates, and then suddenly it will start being an issue again. But at the moment, seems to be good.