On So, 2011-09-11 at 22:25 +0100, Justas Poderys wrote: > When I sync via http server I get this output: > > [INFO] syncevo-http: new SyncML session for 192.168.2.141 > [INFO] sync: matched deviceID fac-352212045389751 against config jphtc > (/home/justas/.config/syncevolution/default/peers/jphtc) > <snip>
So this is not the first sync attempt, is it? It must have worked before to get the device ID and create a corresponding config. > [INFO] sync: addressbook: starting first time sync, two-way > [INFO] sync: Local data changes to be applied during synchronization: > [INFO] sync: *** addressbook *** > [INFO] sync: no changes > [INFO] sync: > [INFO] sync: addressbook: started > [INFO] sync: addressbook: first time sync done unsuccessfully > [ERROR] sync: SML (or SAN) error processing incoming message (local, > status 20007) > <snip> Looks like the Funambol Android client is sending a malformed message. There were reports like that a while back; I think the answer in the Funambol forums at that time was that it was only tested with the Funambol server. Can you increase the loglevel to 5 in /home/justas/.config/syncevolution/default/peers/jphtc/config.ini and try again? The resulting log will have message dumps of the raw and translated messages, that may help with debugging. Send them to me and I can have a look. > evolution-log.html is not very helpful as well: > > <snip> > [2011-09-11 21:59:57.208] addressbook: started > [2011-09-11 21:59:57.209] ===> smlProcessData failed, returned 0x200B > – It's a parser error deep down in the SyncML Toolkit. -- 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. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
