Ticket #1116 (new defect)
sync fails with ERROR 415 - unable to commit change
|Reported by:||abourges||Owned by:||dgollub|
Description (last modified by felixmoeller) (diff)
...as posted on the mailinglist:
...I'm using opensync 0.22 from debian sid and was successfully syncing my Nokia E50 with a local file resource for the last year or so... Somehow during the last updates (last 2-3 weeks), something on my system changed in a way that makes synchronisation impossible.
At a first look everything looks ok, bluetooth connection works, contacts are transmitted from notebook to mobile, but finally msynctool throws an error:
andy@hal:~/PIM_TEST/CONTACTS$ msynctool --sync ContactsTest Synchronizing group "ContactsTest" Member 1 of type file-sync just connected received contact dsession Member 2 of type syncml-obex-client just connected All clients connected or error Received an entry 428 with data of size 4 from member 1 (file-sync). Changetype ADDED Member 1 of type file-sync just sent all changes Received an reply to our Alert Going to receive 0 changes Member 2 of type syncml-obex-client just sent all changes All clients sent changes or error All conflicts have been reported Member 1 of type file-sync committed all changes. Received an reply to our sync Error writing entry 428 to member 2 (syncml-obex-client): Unable to commit change. Error 415 Mapping Write Error: Unable to commit change. Error 415 Member 2 of type syncml-obex-client committed all changes. All clients have written Member 1 of type file-sync just disconnected Member 2 of type syncml-obex-client just disconnected All clients have disconnected The sync failed: Unable to write one or more objects Error while synchronizing: Unable to write one or more objects andy@hal:~/PIM_TEST/CONTACTS$
-> I'm currently using a single contact for testing and this behaviour is reproducable. Since opensync-version ist still 0.22 it might be related to another library causing the effekt (libsyncml?).
I'll attach log/trace files...