Calendar - Exchange sync issue

I am very curious about DavMail. We just started using exchange 365. We have 15 macs and 20 pc. I am having a very hard time viewing the exchange shared calendars in Mac Calendar. I can add delegates on some mac, but on some of them, when I try to add a delegate, nothing propagates, so there is nothing to add. They all have the same version of software.

Anyway, my question is, can MailDav help with shared calendars? Will it help us see shared exchange calendars on iphone?

Any help is appreciated. I cannot believe they cannot play nice.

I downloaded BusyCal the moment I heard they'd added Exchange support. A month and a half later, I've yet to see this error or any other problem with Exchange, and it's basically got everything I like about Calendar.app. Pretty much an ideal solution.

But now that Mavericks is here, I'm giving the built-in calendar another chance. I really like the new look, enough that I'd probably switch back to Calendar.app for daily use if the Exchange error finally goes away.

BusyCal does have some nifty added features, but I can always open it up whenever I need them.

I feel like I should get some pom poms and become a one-man cheerleading squad for Calendar.app. 😁

Over the last OS versions I have been experiencing the same issues. I recently updated to OSX 10.9 Mavericks only to find out that this *extremely* annoying bug still persists. Please tell me, Apple developers of the Calendar app, why can't you fix this bug?

Hello mcoppock, I think you should uncheck the reply marked as "this solved my question" in an attempt to raise a flag in the forum in the hope someone at apple takes the time to review this lenghty thread.

Hello all,

Well, just to report that a new release of davmail came out and all became so reliable this time.

Calendar and mail syncs great.

Notes and reminders are not but for me it is not an issue as I use Evernote+Evermemo and Things for those.

Used it for 2 weeks and not slowing down yet.

Apple should take a look on how this amazing open source works when talking to Exchange.

Give it a shot.

You mean to make sure that both time zone and location are the same on both my Mac and the Exchange account?

I also failed to mention mine is an Exchange hosted on the cloud, the Office 365 kind.

Thanks for writing back. 😉

All these solutions seem to be pre-Mavericks (incl. the links to Apple's support site). Deleting the cache files in the library and resetting the time zone doesn't do the trick with the exchange server under 10.9.x.

Any help is greatly appreciated.

This is really disappointing. Apple's lack of interest in dealing with this MAIL issue.

I do have a fix.... switched to Outlook as an Exchange client - and shut off Calendar.

That should do it... but I would rather use MAIL.

No replies here lately and I'm suffering from this bug lately... With a caution about drawing conclusions about cause when it might only be correlation, I did notice that some of my problems seem to be tied to the wifi I was on. I don't usually use my companies wifi but I did a few weeks back and that's about the time this bug popped up again. After suffering for a while, today I noticed that everything seemed to fix itself when I did another sync from the companies wifi. If anyone has seen similar, report back here to see if we can pin this issue down.

Thanks!

Hi all,

Now I can confirm this is time zone support related issue.

After a while with Outlook, I decided to play around with many of the workarounds posted here and in other forums.

Happens that, when using Mexico City's timezone, it always fails and console message actually *is* related to the TZ issue.

1. If I select "Mexico City" or (of course) I allow Calendar to automatically switch, or disable TZ support, console shows:

08/10/14 09:45:11.988 p.m. Calendar[1190]: WARNING: -[GEOTimezoneHitMap fileNameAtLongitude:latitude:] no time zone area found

2. And as expected, creating/modifying an event throws

08/10/14 09:45:47.564 p.m. CalendarAgent[260]: [com.apple.calendar.store.log.exchange.queue] [error = Error Domain=CalExchangeErrorDomain Code=-3 "Calendar can’t save the event “New Event” to the Exchange server." UserInfo=0x7fa575a72a70 {NSLocalizedFailureReason=There was an error attempting to send your changes to the exchange server., CalFailedOperationKey=<CalExchangeCreateCalendarItemOperation: 0x7fa575ac0ce0>, NSLocalizedDescription=Calendar can’t save the event “New Event” to the Exchange server.}]

Same happens if I select LA, NY,

08/10/14 09:48:46.171 p.m. Calendar[1190]: WARNING: -[GEOTimezoneHitMap fileNameAtLongitude:latitude:] no time zone area found

But Denver, Ciudad Juarez, Memphis, Dallas, Boston. Do work.

For me, Saskatoon don't solve the issue as I need CST, so I used Winnipeg instead. It's been 2 weeks in row with intense calendar working (dragging and dropping tasks from Things, Reminders, Mails) scheduling confcalls, inviting, reviewing availabilities, answering invitations. So far, so good.

Try this and let me know if it worked for you:

1. Enable TZ support (better w/long names enabled)

2. Open Console.app and set a filter for "Calendar"

3. Go to the TZ menu and select a location on your same TZ

4. Check on Console, if "no time zone area found" appears, then try another location

5. Once you have a location that works for you, try to start using calendar, it should sync to exchange.

So, Apple, whatever your approach is to set the TZ automatically it is *not* working, and it looks like Exchange is rejecting to create/update/delete any record that lacks of TZ information. It may be using it as part of a key to locate the record. From my point of view this is totally on client side as it is not sending all information that customer needs to fulfill the request. I *do* expect this being solved in first update of Yosemite (or maybe in first release) as this shouldn't be much complicated to solve, its a missing parameter.

Have good one all!!!

This simple fix worked for me

To fix the issue, it is necessary to go to the Advanced tab of the iCal preferences (iCal -> Prefererences -> Advanced) and enable time zone support. I have OS X 10.9.5

found at..

http://sites.utexas.edu/glenmark/2012/02/07/issues-with-ical-saving-calendar-ite ms-to-exchange-in-snow-leopard/

The "enable time zone support" did not solve the issue for me.

However, the issue may be linked to time zones : I noticed that birthday events are displayed at the wrong date (1 day later). They are correct on iOS calendar.

Did anybody also see errors with birthdays ?

This problem STILL EXISTS IN YOSEMITE?!?!?!!!

It just happened (again) to me, first time in a long time, but there it is. Now that iCal doesn't necessarily manage its own cloud accounts, it's more difficult to "disable that calendar", but given that the problem existed way back when iCal did manage its own accounts completely separate from any other application, this seems to point to a very long-standing bug in iCal itself.

I did manage to disable my Exchange calendar (and there was some confusion between Preferences and iCal in the process), and – for the moment – the problem seems to have disappeared for me. And this is without any shell command wizardry.

Has anyone else noticed that this thread (begun years ago) has nearly 64K views now?

It's seems unreal that despite the fact that Exchange has got to be the most popular corporate mail server around, Apple has been unable to address this issue. A real shame if you ask me. #DisappointedAppleFanboy 😟

I too have seen a similar issue in Yosemite. The re-enable trick seems to stop it for a few minutes then the caution sign shows up again. The odd thing is none of my iOS devices seem to be effected. My Mac Pro which has been experiencing this problem (since Mountain Lion) is joined to our Mac OD Server and our Windows AD server running exchange.