"Calendar can't save event X to Exchange Server"

[RMo]

Ever since upgrading to Mountain Lion (and I've done two clean installs and set up the Exchange account at least twice now according to my organization's settings, so I don't think I'm doing anything wrong), I've had problems with events on my Exchange account in Calendar giving the following error:

Calendar can't save the event "event name" to the Exchange Server.

The account "Exchange account name" currently can't be modified. To discard your changes and continue using the version of your calendars that's on the server, click Revert to Server.

My options are Revert to Server, Try Again, and Ignore.

I get this with lots of events, and I think I've narrowed it down to using the "Sleep" button on calendar alerts that pop up. From looking at the event, it appears Calendar is trying to add a second alert to the event (at the snooze time). Exchange supports only one alert per event, so I'm guessing this is what's causing the problem.

Has anyone heard of this before or know a solution? The best thing I can do now is wait several minutes for Calendar to finish syncing with Exchange (and it freezes while that's happening!), then click "Revert to Server" and modify the event as I see fit when it's all OK again. As you can imagine, this is pretty annoying, and it seems that Mountain Lion's Calendar.app (almost didn't notice it changed from iCal) is a bit buggy.

I find it hard to believe that I'm the only one with this problem, but I can't seem to find much with a search.

 

[Lunchb0x8]

I had the same issue, I blew away the exchange account on my MBA and started fresh, haven't had it come back since... but that doesn't necessarily mean this is what had to be done...

 

[RMo]

Thanks for the reply. Unfortunately, I've blown away the account several times--and even reinstalled the OS once (for other reasons)--and the problem persists.

(Of course, it disappears afterwards for the specific event because it doesn't sync the unsyncable information and the sever info is fine until Snooze messes it up again...but I digress.)

 

[simonmaclean]

Solution?

Hi there,

Did you find a solution to this issue?

I have exactly the same problem. The only thing that the problem entries have in common, is that they are all birthdays.

 

[sausje]

Under Snow Leopard, Time Zone support would do the trick: http://blogs.utexas.edu/glenmark/20...g-calendar-items-to-exchange-in-snow-leopard/.

 

[kendallb]

Still looking for a solution, as the remove/add solution is simply temporary. I have done that multiple times and it keeps coming back...

 

[adammjenkins]

Bump - Has anyone found a solution?

I have finally come to the breaking point in my frustration with this issue. It is especially annoying that the Exchange bug in iOS 6.1.1 caused quite a stir in the blogs (and even prompted my university to send out a mass e-mail encouraging Exchange users to hold off on the update) until the issue was resolved. A few days later, iOS 6.1.2 was pushed out to resolve the issue.

Yet this annoying bug in Mountain Lion still persists after two point releases?

I have tried the numerous temporary fixes (deleted Exchange account and re-add, deleted within both Calendar.app's Account list in Preferences and within the Accounts portion of System Preferences), but found them, in fact, to only be temporary. I have also submitted the bug to the Apple via the Feedback page on the Apple website. Actually, I've submitted it twice, once after both point releases of 10.8.

I really hope that this issue is resolved soon. I just thought I'd vent a bit here and see if anyone else has discovered a potential fix to the issue. If you're anything like me, you've pretty much given up and just keep Calendar.app closed to avoid the annoying conflict messages.