Hello Thomas! One of your user reported that the SyncEvolution<->Memotoo combination started failing for him more often since April. Have you changed anything in the SyncML implementation of Memotoo? The Synthesis engine in the client complains about a Sync command which comes too late: [2013-06-09 18:38:07.564] 'processCmd' - Processing incoming command, Cmd=Sync, IncomingMsgID=4, CmdID=2 [--][++] [->end] [->enclosing] [2013-06-09 18:38:07.565] Created command 'Status' (outgoing) [2013-06-09 18:38:07.565] Processing Sync, Source='note', Target='./memo' [2013-06-09 18:38:07.565] Sync command not allowed outside of sync phase (-> 403) – [2013-06-09 18:38:07.565] 'SessionAbort' - Aborting Session, Status=400, ProblemSource=LOCAL [--][++] [->end] [->enclosing] [2013-06-09 18:38:07.565] WARNING: Aborting Session with Reason Status 400 (LOCAL problem) *** The log that I got didn't include message dumps, but I suspect that the engine was right - that part hasn't changed for a long time. -- 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.