9:52 a.m.
I'm trying to use SyncEvolution for the first time, and I'm running into
a solid error when I try to do my first (refresh-from-client) sync:
[2009-11-06 15:16:51.381] SyncML server account: xxxxxxx
[2009-11-06 15:16:51.381] client: SyncEvolution 0.9.1 for desktop
[2009-11-06 15:16:51.381] device ID: sc-pim-51b0a4c3-f6a3-498a-a8eb-3b89feb4120d
[2009-11-06 15:16:51.381] using libedataserver-1.2.so.9
using libebook-1.2.so.9
using libecal-1.2.so.7
[2009-11-06 15:16:51.381] Scanning backend libraries in /usr/lib/syncevolution/backends/
Loading backend library syncecal.so
Loading backend library syncfile.so
Loading backend library syncaddressbook.so
Loading backend library syncebook.so
Loading backend library syncsqlite.so
[2009-11-06 15:16:51.418] creating
/home/jwd/.cache/syncevolution/scheduleworld-2009-11-06-15-16/todo.before
[2009-11-06 15:16:51.560]
/home/jwd/.cache/syncevolution/scheduleworld-2009-11-06-15-16/todo.before created
[2009-11-06 15:16:51.560] creating
/home/jwd/.cache/syncevolution/scheduleworld-2009-11-06-15-16/addressbook.before
[2009-11-06 15:16:54.877]
/home/jwd/.cache/syncevolution/scheduleworld-2009-11-06-15-16/addressbook.before created
[2009-11-06 15:16:54.878] creating
/home/jwd/.cache/syncevolution/scheduleworld-2009-11-06-15-16/calendar.before
[2009-11-06 15:16:55.186] calendar: could not encode item as iCal:
040000008200E00074C5B7101A82E00800000000308FEABFA05DC801000000000000000010000000F0D61F794250FC45A6D673BD47934D15-rid
I've tried doing the same thing on a different machine where the
Evolution calendar is empty except for a test entry, and things seem to
work fine. So this might well be a corrupted entry in the first
machine's default calendar, but the hex string in the error message
doesn't help me to find it.
I couldn't find anything relevant on the list archives or searching the
web. It appears that error message used to refer to the failing item in
a more recognizable way.
This is syncevolution-evolution_0.9.1-2_i386 running with Evolution
2.22.3.1 on Ubuntu Hardy. The server is ScheduleWorld.
Thanks for the help!
-- John
4:07 a.m.
On Fri, 2009-11-06 at 22:52 +0000, John Dykstra wrote:
[2009-11-06 15:16:55.186] calendar: could not encode item as iCal:
040000008200E00074C5B7101A82E00800000000308FEABFA05DC801000000000000000010000000F0D61F794250FC45A6D673BD47934D15-rid
I've tried doing the same thing on a different machine where the
Evolution calendar is empty except for a test entry, and things seem to
work fine. So this might well be a corrupted entry in the first
machine's default calendar, but the hex string in the error message
doesn't help me to find it.
The part before "-rid" should be the value of a UID property in that
default calendar. Have a look at the output of "syncevolution", it'll
tell you the path to the .ics file with the calendar data.
Make sure Evolution is not running (evolution --force-shutdown). Then
check that file, search for 040000008200... and remove the VEVENT which
contains it. Keep a copy, just in case.
One reason for this kind of failure is a VEVENT which refers to a
VTIMEZONE (via TZID) which is not available. The .ics file is corrupt in
such a case. There was a user with this problem before; we were
uncertain how to handle this and thus don't have a workaround in
SyncEvolution.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
3:48 a.m.
On Sun, 2009-11-08 at 18:07 +0100, Patrick Ohly wrote:
Make sure Evolution is not running (evolution --force-shutdown).
Then
check that file, search for 040000008200... and remove the VEVENT
which
contains it. Keep a copy, just in case.
After doing that, and repeating it for three other events, I was able to
sync successfully. Thanks for the help!
FWIW, all four events originated in Outlook and were recurring. I can
pull the data off one of my backups if it would be helpful.
-- John
4:04 a.m.
On Mon, 2009-11-09 at 16:48 +0000, John Dykstra wrote:
On Sun, 2009-11-08 at 18:07 +0100, Patrick Ohly wrote:
> Make sure Evolution is not running (evolution --force-shutdown). Then
> check that file, search for 040000008200... and remove the VEVENT
> which
> contains it. Keep a copy, just in case.
After doing that, and repeating it for three other events, I was able to
sync successfully. Thanks for the help!
FWIW, all four events originated in Outlook and were recurring. I can
pull the data off one of my backups if it would be helpful.
I think we can reproduce it with artificial VEVENTs, so this won't be
necessary. I added an issue for this:
http://bugzilla.moblin.org/show_bug.cgi?id=7879
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
4696
days inactive
4699
days old
syncevolution@synevolution.org
3 comments
2 participants
participants (2)
-
John Dykstra -
Patrick Ohly