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

Page 1 of 10 last Next
  • by Geof Corb,

    Geof Corb Geof Corb Aug 6, 2012 2:32 PM in response to mcoppock
    Level 1 (5 points)
    Aug 6, 2012 2:32 PM in response to mcoppock

    I have the same problem on two different Macs, both running Mountain Lion.  I did not have this problem on either machine prior to the upgrade.

     

    In my experience, these errors appear *after* the event has occurred.

  • by furyg3,Solvedanswer

    furyg3 furyg3 Aug 10, 2012 12:28 AM in response to mcoppock
    Level 1 (10 points)
    Aug 10, 2012 12:28 AM in response to mcoppock

    I also experianced this problem after an upgrade to Mountain Lion.

     

    I think it has to do with the fact that in Lion the account settings were managed from iCal, and now they are managed by the OS?

     

    Anyway I finally solved it by:

    • Open Calendar (formerly iCal).
    • Go to the Calendar menu and select Preferences.
    • Select the Accounts tab.
    • Remove the Exchange server account which is giving you the error messages.  This calendar will be removed from the Calendar app.
    • Go to System Preferences and click on the "Mail, Contacts & Calendars" pane, find your Exchange server account, and check the "Calendars & Reminders" option to re-enable your calendar.
    • Your Calendar should now sync properly.


    I had to do this for all of the accounts I had set up in Calander, and haven't had any problems since.

  • by mcoppock,

    mcoppock mcoppock Aug 10, 2012 9:10 AM in response to furyg3
    Level 1 (0 points)
    Aug 10, 2012 9:10 AM in response to furyg3

    Okay, I'll give that a shot and report back.

  • by mcoppock,

    mcoppock mcoppock Aug 10, 2012 9:32 AM in response to furyg3
    Level 1 (0 points)
    Aug 10, 2012 9:32 AM in response to furyg3

    Okay, knock on wood, that seems to be working so far. It does take a little longer than I'd like for changes to refresh (but they do eventually, so far), but I'm not getting the errors any longer.

     

    A side benefit is that Reminders now sync correctly, where they were a bit wonky before.

     

    Thanks!

  • by mcoppock,

    mcoppock mcoppock Aug 11, 2012 8:47 AM in response to furyg3
    Level 1 (0 points)
    Aug 11, 2012 8:47 AM in response to furyg3

    Okay, well, this didn't actually completely solve the problem. The original error is gone, but now I receive an error about improper invites on the MBA (don't have one in front of me at the moment). When I check the calendar item in Outlook, I see that it's now been set up for invitations but the invite line is blank. What I'm doing now is deleting invites in Outlook.

     

    This error kicks off with each new calendar item, as it comes due (i.e., for an 11:00am appointment, the error kicks off precisely at 11:00am). I'm going to check next week to see if perhaps it was old appointments set before the "fix" that have the error.

     

    Bottom line, I think Apple has some work to do still on syncing with Exchange.

  • by mcoppock,

    mcoppock mcoppock Aug 13, 2012 9:40 AM in response to mcoppock
    Level 1 (0 points)
    Aug 13, 2012 9:40 AM in response to mcoppock

    Aaaaand, this morning the problem came back. So, yeah, this didn't quite fix things.

     

    Hopefully it's something Apple is aware of and will fix in an update.

  • by robert222,

    robert222 robert222 Aug 14, 2012 10:25 AM in response to mcoppock
    Level 1 (0 points)
    Aug 14, 2012 10:25 AM in response to mcoppock

    This worked for me. Thank you.

  • by mcoppock,

    mcoppock mcoppock Aug 14, 2012 10:28 AM in response to robert222
    Level 1 (0 points)
    Aug 14, 2012 10:28 AM in response to robert222

    Give it a couple days, and if it's still working, please report back. Mine reverted to its previous behavior after about a day.

  • by Geof Corb,

    Geof Corb Geof Corb Aug 14, 2012 2:33 PM in response to furyg3
    Level 1 (5 points)
    Aug 14, 2012 2:33 PM in response to furyg3

    Didn't work for me. I have deleted accounts, blown out keychain config, and just about everything else I can think of to try to remedy this.  Something is clearly not right.

  • by GeoTowers,

    GeoTowers GeoTowers Aug 15, 2012 10:12 AM in response to mcoppock
    Level 1 (0 points)
    Aug 15, 2012 10:12 AM in response to mcoppock

    Didn't work for me too

  • by williamsc29,

    williamsc29 williamsc29 Aug 17, 2012 7:51 AM in response to mcoppock
    Level 1 (0 points)
    Mac OS X
    Aug 17, 2012 7:51 AM in response to mcoppock

    This didn't work for me either.  I completely removed my accounts and it came back.  It's happening on both of my Macs.

  • by williamsc29,

    williamsc29 williamsc29 Aug 23, 2012 2:07 PM in response to williamsc29
    Level 1 (0 points)
    Mac OS X
    Aug 23, 2012 2:07 PM in response to williamsc29

    I was hopeful this would be fixed in 10.8.1, but it's not.

  • by mcoppock,

    mcoppock mcoppock Aug 23, 2012 9:16 PM in response to mcoppock
    Level 1 (0 points)
    Aug 23, 2012 9:16 PM in response to mcoppock

    10.8.1 didn't fix it for me either.

  • by Francesco Borraccino,

    Francesco Borraccino Francesco Borraccino Aug 29, 2012 5:35 PM in response to mcoppock
    Level 1 (5 points)
    Aug 29, 2012 5:35 PM in response to mcoppock

    10.8.1 didn't fix it and this solution doesn't work unfortunately. This is a serious issue and I am shocked that Apple can't fix this. Can we escalate this? Who do we escalate to?

Page 1 of 10 last Next