mcoppock

Q: Calendar - Exchange sync issue

I'm having a problem with Calendar and Exchange syncing (my company uses Exchange 2010), with the following error:

 

"Calendar can’t save the event “Item title” to the Exchange server.

 

The account "Exchange" 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."

 

The options on the dialog box are:

 

Revert to Server

Try Again

Ignore

 

Syncing in general is working, i.e., items added in either system show up as they should. And, I'm not actually changing anything on the items on my MBA. The error pops up apparently randomly--so far, at least, I haven't been able to identify a pattern. I've checked credentials, which seem to be correct, and I've verified that time zone settings are turned on as I think they're supposed to be.

 

Any ideas?

MacBook Air (13-inch, Mid 2012), OS X Mountain Lion

Posted on Aug 3, 2012 12:42 PM

Close

Q: Calendar - Exchange sync issue

  • All replies
  • Helpful answers

first Previous Page 10 of 10
  • by rdj,

    rdj rdj Nov 12, 2014 5:59 AM in response to myshkin5
    Level 1 (15 points)
    Nov 12, 2014 5:59 AM in response to myshkin5

    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?

  • by DowCo,

    DowCo DowCo Nov 12, 2014 8:00 AM in response to rdj
    Level 1 (0 points)
    Nov 12, 2014 8:00 AM in response to rdj

    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

  • by Frestyl,

    Frestyl Frestyl Nov 12, 2014 2:33 PM in response to rdj
    Level 1 (1 points)
    Nov 12, 2014 2:33 PM in response to rdj

    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.

  • by SmartPenwin,

    SmartPenwin SmartPenwin Nov 18, 2014 2:13 PM in response to mcoppock
    Level 1 (15 points)
    Nov 18, 2014 2:13 PM in response to mcoppock

    Hi All,

     

    Well, this still present even in Yosemite 10.10.1 after the "Exchange Sync improvements" fix.

     

    There are 2 things that really find annoying since 3/4 major OS X releases ago:

         -Mail's inability to send and read correctly Outlook-formatted email (which, for example Airmail does)

         -Calendar's inability to save a simple event (not to say with all additional data that goes in special iCloud fields like traffic&travel info) for some timezones  when using Exchange 2010 as a backend.

     

    After all the debugging and tests I've made, I really think that this is related to Apple's Mail.app not using the TZ name strings that Exchange 2010 would expect for an save-event request. This is specially noticeable when using a TZ that has Daylight variations (ex. Mexico City's TZ never achieves to save but I've worked  up to a couple of weeks using Canada's Saskatoon TZ with no problem, however issue manages to strike back)

     

    My guess is that Exchange changed its TZ naming when moving to 2010 and Mail.app still not, making the mismatch.

     

    So, best ways I've managed this is:

         -For Mail, well, still stuck at it as Indev's Mailtags and Mail Act-On add-ons are superb for email managing, which I find way more important than email formatting at this time. If Indev releases its products for Airmail or Airmail happens to do the job itself, then Mail.app will just go away.

         -For Calendar, the most reliable way is using BusyCal instead of Calendar and disable Calendar sync from the Exchange account in System Settings. If you don't want to spend money but time then DavMail (download from Sourceforge.net)

         -For tasks, I ditched all but Things, what a great and simple app

         -For notes, I rely on both: Evernote as the archive/trunk and DayOne as the daily note taking/journal. Btw, Evernote+Moleskine notebooks Evernote Edition is just amazing.

     

    Airmail, Evernote, Things, DayOne and BusyCal are available on Mac AppStore.

     

    Finally, 2 more cents:

         -A new MS Outlook along with a complete new Office:Mac suite is being rumoured to be released on Q1 2015, there are even some screenshots surfacing on the web which look a lot like the apps for iOS. Given the new focus of MS in its software (which never should had lost) I am betting on being a much more solid upgrade than previous releases, and at the price point of an office 356 "lease" looks like a real winner.

         -BusyCal makers, BusyMac, is releasing also a contact manager soon (yes! BusyContacts) which I believe will manage Exchange contacts much better than OS X Contacts, as it is very sad that until now we cannot save pictures to Exchange Contacts and even more than it can't "map" correctly iCloud fields to Exchange's

     

    Not the best answer (or hopes) for native productivity apps but I hope you guys/gals find anything on my experience useful.

  • by yosh089,

    yosh089 yosh089 Dec 10, 2014 5:28 AM in response to mcoppock
    Level 1 (0 points)
    Dec 10, 2014 5:28 AM in response to mcoppock

    Clear the cache file solves my problem. Finally

    Went to ~user/Library/Calendars and deleted Calendar.Cache file

     

    http://www.macsupportguy.com/viewtopic.php?t=613&p=2824

    Cheers,

    Joerg

  • by Chris Brandt1,

    Chris Brandt1 Chris Brandt1 Jan 19, 2015 8:27 AM in response to mcoppock
    Level 1 (35 points)
    Jan 19, 2015 8:27 AM in response to mcoppock

    The way I work around this problem is that I hit command-r before making any changes to a calendar invite. It seems like for me Calendar thinks the local version and the Exchange version have differences that it can not resolve and then spits out that error.

  • by MiguelReyes,

    MiguelReyes MiguelReyes Mar 30, 2015 7:15 AM in response to mcoppock
    Level 1 (0 points)
    Mar 30, 2015 7:15 AM in response to mcoppock

    Deleting "Users/your-user/Library/Calendars/Calendar\ Cache" file worked for me. (Remember to Close Calendar before deleting the file)

  • by ahmaduhhs,

    ahmaduhhs ahmaduhhs Jun 15, 2015 9:50 AM in response to Francesco Borraccino
    Level 1 (0 points)
    Jun 15, 2015 9:50 AM in response to Francesco Borraccino
  • by andresnorte,

    andresnorte andresnorte Jun 29, 2015 11:32 PM in response to ahmaduhhs
    Level 1 (0 points)
    Jun 29, 2015 11:32 PM in response to ahmaduhhs

    i tried the cache, changing timezones, etc. (im in mexico, and this issue occurs with mexico central standard time zones) i still have the problem.

     

    the only workaround i have is: if i choose a central standard time zone near the US (border cities) it works.

     

    but the directors doesnt want a workaround, so if anyone made a "custom" timezone or edited a timezone in exchange please let me know.

     

    by the way, this post worked for exchange 2010, but i have 2013 and the same solution cant be applied to the two versions.

    Ical can´t save the event "event name" to the exchange server

  • by wilburmeinen,

    wilburmeinen wilburmeinen Jul 22, 2015 10:21 AM in response to andresnorte
    Level 1 (14 points)
    Apple Music
    Jul 22, 2015 10:21 AM in response to andresnorte

    I had to manually change the time zone from Mexico City to Chicago. They are both in central and it now syncs with exchange.

  • by SmartPenwin,

    SmartPenwin SmartPenwin Sep 30, 2015 8:01 PM in response to mcoppock
    Level 1 (15 points)
    Sep 30, 2015 8:01 PM in response to mcoppock

    So... it's a fact, nobody cares about this @ apple.

    "El Capitan" still carries this issue. Can't sync calendar with exchange and it's proven by many of us cause is the timezone name sent by Calendar not matching latest TZ names in Exchange servers.

    Man it's SO disappointing as it's been a very long wait since Lion

    Filing another bug report.

first Previous Page 10 of 10