This ist the error message in the Thunderbird error console:
Warnung: There has been an error reading data for calendar: eGW.
However, this error is believed to be minor, so the program will attempt
to continue. Error code: DAV_NOT_DAV. Description: The resource at
http://xxxxxxxxxxxxxxxx:yyyyyy...@intranet.tld.local/groupdav.php/calendar/
is either not a DAV collection or not available
Warnung: There has been an error reading data for calendar: eGW.
However, this error is believed to be minor, so the program will attempt
to continue. Error code: READ_FAILED. Description:
Warnung: CalDAV: Fatal Error parsing etags for Basis
(i repaced the username with xxxxxxxxxxxxxxxx and the userpasseord with
yyyyyyyyyyyy)
This is reproducable on all Windows computers after upgrading
Thunderbird from 3.0.x to 3.1
Please help
Tom
Known regression: https://bugzilla.mozilla.org/show_bug.cgi?id=569572
I don't think, that's the reason, because it worked well with TB3.0.x
and Lighting 1.0b1 and 1.0b2. But after upgrading TB to 3.1 it doesn't
work anymore.
The bugrequest is for reminders not working properly., but here the
whole calendar is denoted as "unavailable" (with a yellow triangle)
here are 2 log sniplets taken from the same apache log
Linux - TB3.0.4 -> works.
192.168.98.200 - xxxxxx [23/Jul/2010:20:17:16 +0200] "PROPFIND
/egroupware/groupdav.php/calendar/ HTTP/1.1" 207 43944 "-" "Mozilla/5.0
(X11; U; Linux i686; de-DE; rv:1.9.1.9) Gecko/20100430
Fedora/3.0.4-2.fc12 Lightning/1.0b2pre Thunderbird/3.0.4"
192.168.98.200 - xxxxxx [23/Jul/2010:20:17:16 +0200] "PROPFIND
/egroupware/groupdav.php/base/calendar/ HTTP/1.1" 207 15645 "-"
"Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.9.1.9) Gecko/20100430
Fedora/3.0.4-2.fc12 Lightning/1.0b2pre Thunderbird/3.0.4"
Win7-TB3.1 -> doesn't wokr
The TB-profile was working well with TB3.0.x. It's an import from the
Linux box, while they was on the same 3.0.x level
192.168.98.237 - xxxxxx [23/Jul/2010:20:17:08 +0200] "PROPFIND
/egroupware/groupdav.php/calendar/ HTTP/1.1" 207 1066 "-" "Mozilla/5.0
(Windows; U; Windows NT 6.1; de-DE; rv:1.9.2.4) Gecko/20100608
Lightning/1.0b2 Thunderbird/3.1"
192.168.98.237 - xxxxxx [23/Jul/2010:20:17:08 +0200] "PROPFIND
/egroupware/groupdav.php/base/calendar/ HTTP/1.1" 207 1071 "-"
"Mozilla/5.0 (Windows; U; Windows NT 6.1; de-DE; rv:1.9.2.4)
Gecko/20100608 Lightning/1.0b2 Thunderbird/3.1"
192.168.98.237 - - [23/Jul/2010:20:19:27 +0200] "PROPFIND
/egroupware/groupdav.php/base/calendar/ HTTP/1.1" 401 91 "-"
"Mozilla/5.0 (Windows; U; Windows NT 6.1; de-DE; rv:1.9.2.4)
Gecko/20100608 Lightning/1.0b2 Thunderbird/3.1"
192.168.98.237 - - [23/Jul/2010:20:19:27 +0200] "PROPFIND
/egroupware/groupdav.php/calendar/ HTTP/1.1" 401 91 "-" "Mozilla/5.0
(Windows; U; Windows NT 6.1; de-DE; rv:1.9.2.4) Gecko/20100608
Lightning/1.0b2 Thunderbird/3.1"
192.168.98.237 - xxxxxx [23/Jul/2010:20:19:30 +0200] "PROPFIND
/egroupware/groupdav.php/calendar/ HTTP/1.1" 207 1066 "-" "Mozilla/5.0
(Windows; U; Windows NT 6.1; de-DE; rv:1.9.2.4) Gecko/20100608
Lightning/1.0b2 Thunderbird/3.1"
192.168.98.237 - xxxxxx [23/Jul/2010:20:20:00 +0200] "PROPFIND
/egroupware/groupdav.php/base/calendar/ HTTP/1.1" 207 1071 "-"
"Mozilla/5.0 (Windows; U; Windows NT 6.1; de-DE; rv:1.9.2.4)
Gecko/20100608 Lightning/1.0b2 Thunderbird/3.1"
xxxxxx is the username
Downgrading to 3.0.x and lightning works again.
What's wron g with TB 3.1.x or Lightning 1.0b2
Thunderbird 3.0 works only with Lightning 1.0b1.
Thunderbird 3.1 works only with Lightning 1.0b2.
This implies you never used Thunderbird 3.0 with Lightning 1.0b2.
> The bugrequest is for reminders not working properly., but here the
> whole calendar is denoted as "unavailable" (with a yellow triangle)
Maybe you read the wrong bug report? The one linked above is "Bug 569572
- Events from eGroupware CalDAV resource are not displayed".
But maybe you see "Bug 579553 - Lightning no longer syncs with
eGroupware calendar via GroupDAV"
<https://bugzilla.mozilla.org/show_bug.cgi?id=579553>.
Two weeks ago I raised the question if the patch in Bug 569572 fixes Bug
579553 too. But developers did not respond yet.