Mountain Lion iCal issue with ZCS 7.2.0

mfehr · Post by **mfehr** » Thu Jul 26, 2012 8:57 am

I upgraded one of my Macs to OS X Mountain Lion. Today, I found out, that iCal communication has changed. I cannot enter nor modify calendar entries which are hosted on a Zimbra server and accessed through the CalDAV protocol. - The same calendar can be updated from a 10.7 OS X Client without any problem.
So it seems that Mountain Lion changed the way of its communication to CalDAV servers. I get the following error message in iCal: The server responded with Ã‚â€œ400Ã‚â€ to operation CalDAVWriteEntityQueueableOperation.
In the trace.log, I can see the following entry:
15:44:46.256:btpool0-9361://my.server.com/dav/user%40server.com/Calendar/02E2EF91-CA7D-4122-84C7-7AB6E3A32F69.ics 10.0.0.231 PUT null; Mac OS X/10.8 (12A269) CalendarAgent/47

15:44:46.256:btpool0-9361://my.server.com/dav/user%40server.com/Calendar/02E2EF91-CA7D-4122-84C7-7AB6E3A32F69.ics 401 null 0

15:44:46.312:btpool0-9361://my.server.com/dav/user%40server.com/Calendar/02E2EF91-CA7D-4122-84C7-7AB6E3A32F69.ics 10.0.0.231 PUT null; Mac OS X/10.8 (12A269) CalendarAgent/47

15:44:46.318:btpool0-9361://my.server.com/dav/user%40server.com/Calendar/02E2EF91-CA7D-4122-84C7-7AB6E3A32F69.ics 400 null 0
Any idea if this can be fixed somehow?

3648JHill · Post by **3648JHill** » Thu Jul 26, 2012 9:28 am

[quote user="mfehr"]I get the following error message in iCal: The server responded with Ã‚â€œ400Ã‚â€ to operation CalDAVWriteEntityQueueableOperation.

[/QUOTE]
Experiencing the same issue... mfehr, did you file a bug report?

mfehr · Post by **mfehr** » Thu Jul 26, 2012 9:44 am

A bug was just submitted by someone else. I added my findings to the bug for further info.
Bug 76402 – iCal - Server Responded with Error

eike_reinel · Post by **eike_reinel** » Thu Jul 26, 2012 9:46 am

Yep, same problem after my migration. Until this morning, my calendar access to our Zimbra server was OK, after the upgrade to Mountain Lion, I get the 400 error...

(It seems, that every new MAC OS X release breaks the sync between calendar and the Zimbra server...

)

matt321 · Post by **matt321** » Thu Jul 26, 2012 2:38 pm

I have experienced the same issue after doing an upgrade from Lion to Mountain Lion.
My Fix: Removing the CalDav account from iCal and re-adding it seems to have fixed the issue.
YMMV....

Omeganon · Post by **Omeganon** » Thu Jul 26, 2012 2:41 pm

This is interesting. A co-worker is experiencing the exact same issue but for me, all my iCal problems went away and iCal works great. Free/Busy and changing the calendar an event was on both used to break under Lion but are working great now. I am not seeing this under ML.
7.1.4_GA_2555
--

Marc

eike_reinel · Post by **eike_reinel** » Thu Jul 26, 2012 2:53 pm

[quote user="matt321"]I have experienced the same issue after doing an upgrade from Lion to Mountain Lion.
My Fix: Removing the CalDav account from iCal and re-adding it seems to have fixed the issue.
YMMV....[/QUOTE]
Hm, I exactly did this (removing and readding the CalDAV account), but I still have the problem...

MACscr · Post by **MACscr** » Thu Jul 26, 2012 3:33 pm

Removing it and readding it didnt work. I just had to set a default reminder setting for all events for this particular calendar and that seemed fix the issue. Not sure how those settings got wiped as their should have already been default reminder settings for it. Oh well. It works now.

mfehr · Post by **mfehr** » Thu Jul 26, 2012 4:28 pm

I received a work around that works:
[QUOTE]It's to do with the Default Alarm setting. There is a bug that does not allow "Alert" to be set to "None".
To temporarily solve this bug, set the default alarm for that account to anything other than "None". And also, don't change alert setting of any existing event to None.[/QUOTE]
In the mean time, the bug is already fixed: http://bugzilla.zimbra.com/show_bug.cgi?id=74229 - Now we need to wait for the next release to be published so we can reset the default alarm to None.

Simulcast · Post by **Simulcast** » Mon Jul 30, 2012 12:23 pm

Note that we run Zimbra 7.13 GA and could not set the default alarm setting (v6 under Mountain Lion) to 'None' (the change would always revert back to 'None') until iCal delegation was enabled for the account. Hope this helps.