Homepage | Products | OX Knowledge Base | Support | Try Now | Contact | Company
OX Logo
Results 1 to 1 of 1
  1. #1
    Join Date
    Jul 2009
    Posts
    24

    Default CalDAV Problem in Lighning

    Hi,

    after Updating from 7.6 to 7.8 (7.8.0 Rev 14 2016-01-13), I have a strange problem.

    We use the calendar of one user as a big calendar for our whole company. So every user has the right to see this calendar and some have the right to add appointments to it and some to change these appointments.

    In OX itself, everything works.

    Because we use Thundebird as our Mail-Client, many of our users also use Lightning for their daily work and sync calendars to it. After some changes, I'm pretty sure, that every calendar is synced correctly, but the said one.

    From Thunderbird, I get a CalDAV Error 400:
    "CalDAV failed: Get failed: CalDAV: Error: got status 400 fetching calendar data for ML, null"

    With a more detailed log, I also see this error:
    "CalDAV: webdav-sync Token: null"

    Other calendars can be synced without problems and regardless of access right, it's just this special calendar, that worked with 7.6 and stopped with updating. Sadly, we need this calendar and I get a lot of trouble, if I tell my users, that they can't use Lightning anymore, so any hints how to solve this?

    On OX site, there are no errors in the logfile, I just see a successful connect via CalDAV and thats it, no errors, neither in OX nor Apache Logs.

    A more complete log from adding the calendar to my Lightning from Thunderbird Error Console:
    Code:
    CalDAV: Retrieving server info from cache for ML
    [calCachedCalendar] Performing playback operation add on 0 items to ML
    [calCachedCalendar] Performing playback operation modify on 0 items to ML
    [calCachedCalendar] Performing playback operation delete on 0 items to ML
    [calCachedCalendar] Doing changelog based sync for calendar https://<caldav-url>
    CalDAV: send: <?xml version="1.0" encoding="UTF-8"?>
    <D:propfind xmlns:D="DAV:" xmlns:CS="http://calendarserver.org/ns/" xmlns:C="urn:ietf:params:xml:ns:caldav"><D:prop><D:resourcetype/><D:owner/><D:current-user-principal/><D:supported-report-set/><C:supported-calendar-component-set/><CS:getctag/></D:prop></D:propfind>
    CalDAV: Status 207 on initial PROPFIND for calendar ML
    CalDAV: Authentication scheme for ML is Basic
    CalDAV: recv: <?xml version="1.0" encoding="UTF-8"?>
    <D:multistatus xmlns:D="DAV:" xmlns:APPLE="http://apple.com/ns/ical/" xmlns:CAL="urn:ietf:params:xml:ns:caldav" xmlns:CS="http://calendarserver.org/ns/"><D:response><D:href>/caldav/238/</D:href><D:propstat><D:prop><D:resourcetype><D:collection /><CAL:calendar /><CS:shared /></D:resourcetype><D:supported-report-set><D:supported-report><D:report><CAL:calendar-multiget /></D:report></D:supported-report><D:supported-report><D:report><CAL:calendar-query /></D:report></D:supported-report><D:supported-report><D:report><D:sync-collection /></D:report></D:supported-report></D:supported-report-set><supported-calendar-component-set xmlns="urn:ietf:params:xml:ns:caldav"><CAL:comp name="VEVENT" /></supported-calendar-component-set><D:current-user-principal><D:href>/principals/users/<user>/</D:href></D:current-user-principal><getctag xmlns="http://calendarserver.org/ns/">http://www.open-xchange.com/ctags/238-1453192878034</getctag></D:prop><D:status>HTTP/1.1 200 OK</D:status></D:propstat><D:propstat><D:prop><D:owner></D:owner></D:prop><D:status>HTTP/1.1 404 NOT FOUND</D:status></D:propstat></D:response></D:multistatus>
    CalDAV: Collection has webdav sync support
    Adding supported items: VEVENT for calendar: ML
    CalDAV: Found principal url from DAV:current-user-principal /principals/users/<user>/
    CalDAV: send: OPTIONS https://<our-dav-server>/caldav/
    CalDAV: DAV header: 1, 2, 3, access-control, calendar-access, addressbook, extended-mkcol, calendar-auto-schedule, calendar-schedule, calendarserver-sharing, calendarserver-principal-search, calendarserver-principal-property-search
    CalDAV: Calendar ML supports calendar-auto-schedule
    CalDAV: send: PROPFIND https://<our-dav-server>/principals/users/<user>/
    <?xml version="1.0" encoding="UTF-8"?>
    <D:propfind xmlns:D="DAV:" xmlns:C="urn:ietf:params:xml:ns:caldav"><D:prop><C:calendar-home-set/><C:calendar-user-address-set/><C:schedule-inbox-URL/><C:schedule-outbox-URL/></D:prop></D:propfind>
    CalDAV: recv: <?xml version="1.0" encoding="UTF-8"?>
    <D:multistatus xmlns:D="DAV:" xmlns:APPLE="http://apple.com/ns/ical/" xmlns:CAL="urn:ietf:params:xml:ns:caldav" xmlns:CS="http://calendarserver.org/ns/"><D:response><D:href>/principals/users/<user>/</D:href><D:propstat><D:prop><schedule-outbox-URL xmlns="urn:ietf:params:xml:ns:caldav"><D:href>/caldav/schedule-outbox</D:href></schedule-outbox-URL><schedule-inbox-URL xmlns="urn:ietf:params:xml:ns:caldav"><D:href>/caldav/schedule-inbox</D:href></schedule-inbox-URL><calendar-home-set xmlns="urn:ietf:params:xml:ns:caldav"><D:href>/caldav/</D:href></calendar-home-set><calendar-user-address-set xmlns="urn:ietf:params:xml:ns:caldav"><D:href>mailto:<mail-address></D:href><D:href>/principals/users/<user>/</D:href></calendar-user-address-set></D:prop><D:status>HTTP/1.1 200 OK</D:status></D:propstat></D:response></D:multistatus>
    CalDAV: send(https://<caldav-url>): <?xml version="1.0" encoding="UTF-8"?>
    <sync-collection xmlns="DAV:"><sync-token/><sync-level>1</sync-level><prop><getcontenttype/><getetag/></prop></sync-collection>
    CalDAV: webdav-sync Token: null
    CalDAV recv: <big data portion with lots of status 200>
    CalDAV: send(https://<dav-url>)... <another big data portion>
    Zeitstempel: 19.01.2016 10:32:24
    Warnung: CalDAV: Get failed: CalDAV: Error: got status 400 fetching calendar data for ML, null
    Quelldatei: file:///C:/Users/<user>/AppData/Roaming/Thunderbird/Profiles/sjzp3zbs.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/components/calDavCalendar.js
    Zeile: 1213
    Zeitstempel: 19.01.2016 10:32:24
    Fehler: [calCachedCalendar] replay action failed: null, uri=https://<dav-url>, result=2147500037, op=[xpconnect wrapped calIOperation]
    Quelldatei: file:///C:/Users/<user>/AppData/Roaming/Thunderbird/Profiles/sjzp3zbs.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calCachedCalendar.js
    Zeile: 322
    [calCachedCalendar] replayChangesOn finished.
    [calCachedCalendar] sync queue empty.
    Zeitstempel: 19.01.2016 10:32:24
    Warnung: Fehler beim Lesen von Daten für Kalender: ML. Allerdings ist dieser Fehler wahrscheinlich vernachlässigbar, daher versucht das Programm fortzufahren. Fehlercode: 0x80004005. Beschreibung: CalDAV: Error: got status 400 fetching calendar data for ML, null
    Quelldatei: file:///C:/Users/<user>/AppData/Roaming/Thunderbird/Profiles/sjzp3zbs.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calCalendarManager.js
    Zeile: 960
    Zeitstempel: 19.01.2016 10:32:24
    Warnung: Fehler beim Lesen von Daten für Kalender: ML. Allerdings ist dieser Fehler wahrscheinlich vernachlässigbar, daher versucht das Programm fortzufahren. Fehlercode: READ_FAILED. Beschreibung: 
    Quelldatei: file:///C:/Users/<user>/AppData/Roaming/Thunderbird/Profiles/sjzp3zbs.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calCalendarManager.js
    Zeile: 960
    CalDAV: recv: null
    CalDAV: onStopRequest: no reader
    Last edited by shecki; 01-19-2016 at 11:50 AM.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •