(In reply to comment #2) > Created attachment 87667 [details] > Log after running "syncevolution loglevel=4 --sync refresh-from-server > memotoo calendar" This shows that even very simply events fail to be stored by EDS, which is most likely a bug in EDS. It should be possible to reproduce that without syncing like this: cat >/tmp/test.ics <<EOF BEGIN:VCALENDAR VERSION:2.0 PRODID:-//Synthesis AG//NONSGML SyncML Engine V22.214.171.124//EN BEGIN:VEVENT LAST-MODIFIED:20130916T131237 DTSTAMP:20131015T094707Z CLASS:PUBLIC SUMMARY:Philippine Madrigal Singers LOCATION:SOTA Concert hall\, 1 Zubir Said Drive\, Singapore 227968 DTSTART:20131104T190000 DTEND:20131104T210000 BEGIN:VALARM TRIGGER;VALUE=DURATION:-P1D ACTION:DISPLAY END:VALARM END:VEVENT END:VCALENDAR EOF syncevolution --import /tmp/test.ics \ backend=evolution-calendar \ database=... where the value of "database" comes from "--print-databases" and matches the database that you are using for syncing. Does this fail as expected? Then please file a bug with Debian for their version of EDS. You might also try upstream EDS, but it is less likely that they'll support 3.8. But just to be sure (as you didn't answer that part of the question) - it is intentional that you try to store in Exchange?