And no, we didn't choreograph that one!Scott">http://www.zimbra.com/forums/announceme ... 3-out.html
Scott
Search found 96 matches
- Thu Mar 20, 2008 6:37 pm
- Forum: CalDAV / CardDAV / iSync
- Topic: iSync Connector not performing full sync
- Replies: 21
- Views: 6312
iSync Connector not performing full sync
Actually I think it just came out about 10 minutes ago. How's that for fairly soon? And no, we didn't choreograph that one!
Scott">http://www.zimbra.com/forums/announceme ... 3-out.html
Scott
And no, we didn't choreograph that one!Scott">http://www.zimbra.com/forums/announceme ... 3-out.html
Scott
- Thu Mar 20, 2008 6:28 pm
- Forum: CalDAV / CardDAV / iSync
- Topic: iSync Connector not performing full sync
- Replies: 21
- Views: 6312
iSync Connector not performing full sync
It's a connector issue. The problem is caused by duplicate appts in iCal...which can be pretty challenging to catch (at least challenging to catch all of them...it only takes one to screw things up).
5.0.3 will be out fairly soon from what I understand.
Hope that helps,
Scott
5.0.3 will be out fairly soon from what I understand.
Hope that helps,
Scott
- Thu Mar 20, 2008 6:13 pm
- Forum: CalDAV / CardDAV / iSync
- Topic: iSync Connector not performing full sync
- Replies: 21
- Views: 6312
iSync Connector not performing full sync
This is a known bug and will be fixed in the upcoming 5.0.3 release. Sorry for the inconvenience.
Scott
Scott
- Thu Mar 20, 2008 12:03 pm
- Forum: CalDAV / CardDAV / iSync
- Topic: iSync connector + entourage = no sync?
- Replies: 11
- Views: 3463
iSync connector + entourage = no sync?
Hey Ryan. That is a known bug and will be fixed in the upcoming 5.0.3 release. Sorry for the inconvenience.
Take care,
Scott
Take care,
Scott
- Sun Mar 09, 2008 8:27 pm
- Forum: CalDAV / CardDAV / iSync
- Topic: [SOLVED] Timezone issues
- Replies: 8
- Views: 2388
[SOLVED] Timezone issues
Have you turned on timezone support in iCal?
Thanks,
Scott
Thanks,
Scott
- Mon Mar 03, 2008 11:54 am
- Forum: CalDAV / CardDAV / iSync
- Topic: Zimbra 5.0.2_GA_1976 - OS X 1.5.2 - Entourage 2008 (version 12)
- Replies: 6
- Views: 2287
Zimbra 5.0.2_GA_1976 - OS X 1.5.2 - Entourage 2008 (version 12)
A dup in this case means any appointment in iCal that has the same title and the same start time. Other attributes of the appt might be different, but they are considered the same if the title and start time of the appts are the same. Why you are getting inconsistent behavior is strange. I'm assumin...
- Fri Feb 29, 2008 2:32 pm
- Forum: CalDAV / CardDAV / iSync
- Topic: Zimbra 5.0.2_GA_1976 - OS X 1.5.2 - Entourage 2008 (version 12)
- Replies: 6
- Views: 2287
Zimbra 5.0.2_GA_1976 - OS X 1.5.2 - Entourage 2008 (version 12)
Thanks for the logs. What you are seeing is a problem that results from the dups in your Entourage/iCal calendars. This bug has been identified and fixed (bugzilla #25151) and will be in the 5.0.3 release.
Thanks,
Scott
Thanks,
Scott
- Fri Feb 29, 2008 12:44 pm
- Forum: CalDAV / CardDAV / iSync
- Topic: Zimbra 5.0.2_GA_1976 - OS X 1.5.2 - Entourage 2008 (version 12)
- Replies: 6
- Views: 2287
Zimbra 5.0.2_GA_1976 - OS X 1.5.2 - Entourage 2008 (version 12)
I'm sorry to hear that you're having problems. Can you attach the sync logs (found in ~/Library/Logs/Zimbra) so we can pinpoint what might be happening? That would be very helpful in diagnosing what the problem might be.
Thanks,
Scott
Thanks,
Scott
- Thu Feb 28, 2008 3:36 pm
- Forum: CalDAV / CardDAV / iSync
- Topic: "attempt to insert nil key" error
- Replies: 6
- Views: 2441
"attempt to insert nil key" error
To follow up on David Strauss's post...both 24949 and 24658 can cause exactly these types of exceptions, but it's more likely that what people are experiencing are malformed URLs. Regardless, both of the bugs are fixed.
Scott
Scott
- Thu Feb 28, 2008 3:33 pm
- Forum: CalDAV / CardDAV / iSync
- Topic: "attempt to insert nil key" error
- Replies: 6
- Views: 2441
"attempt to insert nil key" error
The problem has been fixed. I believe it's bug 24949. The problem is that there is a malformed URL in one or more of the contact fields that is causing the exception. The fix will be in 5.0.3. Very sorry about the problem...I know it's annoying. And I know the question...when will 5.0.3 be out? Unfo...