Caldev and iCal error "this is not a valid location"

Questions, comments, and problems with Zimbra on Apple desktops & general CalDAV / CardDAV questions.
Costa-101
Advanced member
Advanced member
Posts: 169
Joined: Fri Sep 12, 2014 10:16 pm

Caldev and iCal error "this is not a valid location"

Post by Costa-101 »

John perhaps you can help me to understand the root of the problem here.
Apparently the zimbra connector is available in the dowloads part of the admin console.
I must be blind or stupid or both but where in the attached image might I find the said connector please?
Picture 1.jpg
User avatar
jholder
Ambassador
Ambassador
Posts: 4824
Joined: Fri Sep 12, 2014 10:00 pm

Caldev and iCal error "this is not a valid location"

Post by jholder »

You need to install the network edition. It isn't available in the open source version.
Service
Elite member
Elite member
Posts: 1023
Joined: Tue Apr 14, 2009 2:44 pm

Caldev and iCal error "this is not a valid location"

Post by Service »

We deleted our calendars and re-added using one word only (i.e. Calendar, instead of Shared Calendar)
All calendars now sync properly with iCal/Zimbra web Cal
(servers don't like spaces???)
Service
Elite member
Elite member
Posts: 1023
Joined: Tue Apr 14, 2009 2:44 pm

Caldev and iCal error "this is not a valid location"

Post by Service »

We deleted our calendars and re-added using one word only (i.e. Calendar, instead of Shared Calendar)
All calendars now sync properly with iCal/Zimbra web Cal
Zlender
Posts: 1
Joined: Fri Sep 12, 2014 11:37 pm

Caldev and iCal error "this is not a valid location"

Post by Zlender »

Simple rename of calendars in Web Zimbra solved this problem for me. Right click -> edit properties and then change from Shared Calendar to Shared_Calendar and iCal error is gone.

Zimbra 5.0.6

MacOS 10.5.4
User avatar
jholder
Ambassador
Ambassador
Posts: 4824
Joined: Fri Sep 12, 2014 10:00 pm

Caldev and iCal error "this is not a valid location"

Post by jholder »

[quote user="Zlender"]Simple rename of calendars in Web Zimbra solved this problem for me. Right click -> edit properties and then change from Shared Calendar to Shared_Calendar and iCal error is gone.

Zimbra 5.0.6

MacOS 10.5.4[/QUOTE]
This is fixed in 5.0.7. CalDav is much more reliable in .7
BarefootPanda
Advanced member
Advanced member
Posts: 110
Joined: Fri Sep 12, 2014 11:33 pm

Caldev and iCal error "this is not a valid location"

Post by BarefootPanda »

5.0.7 didn't fix this for me.
I'm still getting tons issues with sharing calendars. I have the same issue on both my Network and Open Source installs.
BarefootPanda
Advanced member
Advanced member
Posts: 110
Joined: Fri Sep 12, 2014 11:33 pm

Caldev and iCal error "this is not a valid location"

Post by BarefootPanda »

This thread now has over 1000 views and no updates. Does anyone have a suggestion that might lead to a fix?
User avatar
jholder
Ambassador
Ambassador
Posts: 4824
Joined: Fri Sep 12, 2014 10:00 pm

Caldev and iCal error "this is not a valid location"

Post by jholder »

Can you please provide more info? Screenshots, errors, etc? "It doesn't work" won't get you a solution. Also, several posts on here aren't relevant to the topic, which is why it has so many views.
BarefootPanda
Advanced member
Advanced member
Posts: 110
Joined: Fri Sep 12, 2014 11:33 pm

Caldev and iCal error "this is not a valid location"

Post by BarefootPanda »

I've posted a few times with screenshots of this error.
One can be found here...
http://www.zimbra.com/forums/isync-cald ... #post98307
http://www.zimbra.com/forums/isync-cald ... #post98304" update the 5.0.6 to 7 or 8. None of them are working and give the same results.
When giving a co-worker full access (admin) to my calendar they cannot edit it through iCal. I have tried this on CentOS OpenSource 5.0.8 and OS X 10.4.11 with 5.0.7 and it still gives the same errors it has since 5.0.6
I have tried manually setting up the calendar and using the iSync connector. I've tried new users on the server and on the client machines. No luck at all. I've been chasing this issue for months it seems.
Post Reply