Connector creating new CalDAV account during each sync after 10.6.4 upgrade

shawnlhood · Post by **shawnlhood** » Thu Jun 17, 2010 2:19 pm

I'm running Zimbra 6.0.5 Network. I just upgraded Mac OS X from 10.6.3 to 10.6.4. Using Zimbra Connector 6.0.2423.
After upgrading to 10.6.4 I opened iCal. My Connector is set to sync every minute. At the time of each sync, a new Zimbra CalDAV account would be created. I reinstalled the Connector and the behavior still manifests.
I am trying to track down some relevant log messages.

dstoliker · Post by **dstoliker** » Thu Jun 17, 2010 3:16 pm

We've got a user reporting the exact same issue. Any resolution on this?

shawnlhood · Post by **shawnlhood** » Thu Jun 17, 2010 3:39 pm

Opened up a case w/ Zimbra support. Nothing yet.
A workaround for now:
Go to the Connector preferences pane and disable the 'Sync my iCal calendars using CalDav'. Then go delete all but one of the replicated CalDav accounts within iCal. I'm not sure what functionality, if any, is compromised by doing this.

shawnlhood · Post by **shawnlhood** » Mon Jun 21, 2010 10:22 am

Bug 48250 – iSync creating duplicate CalDAV accounts after OSX 10.6.4 upgrade

ewilen · Post by **ewilen** » Mon Jun 21, 2010 10:36 am

That workaround should work fine without compromising any functionality. At most, if you have the box checked in the system prefs, then the Zimbra system pref can trigger CalDAV refreshes. I'm not sure it does; just saying it could. But iCal has its own refresh schedule and can be triggered manually as well.
In the Apple support discussion linked off the bug, I mentioned that it's not affecting my Mac and I give my version of the connector. Also, we're currently on ZCS 6.0.6.

shawnlhood · Post by **shawnlhood** » Mon Jun 21, 2010 11:23 am

We're on 6.0.5 Network and three users have experienced the problem. Upgrading to 6.0.7 on Wednesday, but I doubt that will provide any resolution.

ddrazyk · Post by **ddrazyk** » Sun Jul 04, 2010 2:26 pm

The duplication of calendar exists on ZCS 6.0.1 and an upgrade to 6.0.7 did not solve anything. The workaround is ok for most users.

Rodi · Post by **Rodi** » Fri Jul 23, 2010 12:37 pm

A temporary workaround should be to configure the iSync account using the full

email address rather than just . This way the changing

principalURL of the iCal account will not happen.
clean all your iCal accounts, all your iSync accounts an recreate a new account with user@domain.com username.
Rodi

ewilen · Post by **ewilen** » Fri Jul 23, 2010 1:47 pm

Thanks, Rodi. This explains why I wasn't seeing the problem--my iSync & iCal were already set up that way.