CalDAV Calendars No Longer Work in Mountain Lion?!

Question

Level 1

4 points

CalDAV Calendars No Longer Work in Mountain Lion?!

Since upgrading to Mountain Lion, CalDAV no longer works for me - it fails to log in to the server (which I know is working because the same credentials and address still work on my iPhone and iPad).

I've tried deleting and re-adding the calendar and making sure alerts are not defaulted to none, but now, if I try to re-add it using the Wizard, it fails because it can't log in (it says it found a calendar but that my login failed), and if I edit the parameters for one that I know works to those now, it keeps telling me the server gave an error when I try to connect and asking for my password. This is not the problem with creating and modifying events in Zimbra - I never even get there, I cannot log in to my CalDAV server anymore using credentials that I know work using other CalDAV clients.

Any help would be appeciated, this is a disabling, showstopper problem, I don't want to have to back out the OS install for this or g-d forbid, pave my machine, but I must have a functional calendar.

Posted on Jul 28, 2012 2:20 PM

Reply

Answer 1

Best reply

JiminSF Author

Level 1

4 points

Jul 28, 2012 7:32 PM in response to JiminSF

Never mind, fixed this myself - turned out to be an old, unfixed bug in iCal relating to use of old keychain entries - see http://www.atpeaz.com/index.php/2011/fixing-lions-icals-caldav-password-problem/. After I removed the calendar, then removed all of keychain entries for this server, then re-added the calendar, it came back to life and stopped giving login errors.

Reply

Answer 2

Jul 30, 2012 10:09 AM in response to JiminSF

I'm going to try this, as I am having caldav and carddav errors in Moutain Lion where none existed before on Lion.

Reply

Answer 3

Jul 30, 2012 10:48 AM in response to Adam Blainey

This seemed to have solved my issue with Contacts.app in Mountain Lion, however, my Calendar.app is still throing up an error when I try to write to the server.

Reply

Answer 4

JiminSF Author

Level 1

4 points

Jul 30, 2012 11:21 AM in response to Adam Blainey

Have you made sure that the alerts are not set to none, and that the default alerts for that calendar are not none? Some folks are having problems with writes related to this in the current Zimbra release...

Reply

Answer 5

Jul 30, 2012 11:26 AM in response to JiminSF

Hey weird, Alerts were set to None. I tried to change it, and it sets it back.

Reply

Answer 6

Jul 30, 2012 11:30 AM in response to Adam Blainey

After finnicking around, that seems to have worked!!!!

Reply

Answer 7

JiminSF Author

Level 1

4 points

Jul 30, 2012 11:40 AM in response to Adam Blainey

Ha! Glad to hear it. Happy to be the helper instead of the helpee this time. ;-)

Reply

Answer 8

Aug 13, 2012 6:09 PM in response to JiminSF

I unfortunately am still getting a serious problem with connecting to a non-Zimbra caldav server. From looking in the logs, here is what I am seeing:

8/13/12 8:25:48.977 PM Calendar[6228]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.

8/13/12 8:37:54.494 PM Calendar[6658]: [com.apple.calendar.store.log.caldav.queue] [Not creating a POST schedule change-request, because the server doesn't have a schedule-outbox]

8/13/12 8:40:57.204 PM Calendar[6658]: [com.apple.calendar.ui.log.updatetext] [There was an error trying to get the status from CalendarAgent: 5]

(I tried the keychain fix and we're still getting this.)

Reply