Error 500 with Nokia e65

[freinhard]

here's what i did to sync:

• nokia e65 over bluetooth and syncml plugin
• pc side with file plugin
• one single contact with just a lastname present on the phone
• syncing the first time copied the contact to the pc
• changed the lastname
• synced again, and below the output

---

osynctool --sync nokiae65 Synchronizing group "nokiae65" The previous synchronization was unclean. Slow-syncing contact sink of member 2 of type file-sync just connected Main sink of member 2 of type file-sync just connected Main sink of member 1 of type syncml-obex-client just connected contact sink of member 1 of type syncml-obex-client just connected All clients connected or error Main sink of member 1 of type syncml-obex-client just sent all changes Received an entry 5 (xmlformat-contact) from member 2 (file-sync). Changetype ADDED contact sink of member 2 of type file-sync just sent all changes Main sink of member 2 of type file-sync just sent all changes Received an entry 5 (xmlformat-contact) from member 1 (syncml-obex-client). Changetype ADDED contact sink of member 1 of type syncml-obex-client just sent all changes All clients sent changes or error Conflict for Mapping 0x9f2c258: Entry 1: Member: 2 (file-sync) UID: 5 <?xml version="1.0"?> <contact>

<Name>

<LastName?>Muebauer</LastName?>

</Name> <Revision>

<Content>20100110T200441Z</Content>

</Revision>

</contact>

Entry 2: Member: 1 (syncml-obex-client) UID: 5 <?xml version="1.0"?> <contact>

<Name>

<LastName?>Mbauer</LastName?>

</Name> <Revision>

<Content>20100110T200441Z</Content>

</Revision>

</contact>

Which entry do you want to use? [1-9] To select a side, [A]bort, [D]uplicate: 1 Solving conflict All changes got mapped All conflicts have been reported All changes got multiplied All changes got prepared for write

Synchronization Forecast Summary:

ObjType?: contact

Member 2: Adding(0) Modifying(0) Deleting(0) Member 1: Adding(0) Modifying(1) Deleting(0)

Do you want to continue the synchronization? (N/y): y

OK! Completing synchronization! contact sink of member 2 of type file-sync committed all changes. Main sink of member 2 of type file-sync committed all changes. Main sink of member 1 of type syncml-obex-client committed all changes. ERROR: Unable to commit change. Error 500 EXIT_ERROR: _recv_event: (null) ERROR: Unable to commit change. Error 500 Error for entry 5 (vcard21) and member 1 (syncml-obex-client): Unable to commit change. Error 500 Mapping Error: Unable to commit change. Error 500 ERROR: Fewer sink_engines reported committed all than connected ERROR: At least one object engine failed while writting changes. Aborting ERROR: At least one object engine failed while writting changes. Aborting The sync failed: At least one object engine failed while writting changes. Aborting ERROR: Engine aborting due to an error: At least one object engine failed while writting changes. Aborting EXIT_ERROR: osync_obj_engine_commit_change_callback: Unable to commit change. Error 500 contact sink of member 1 of type syncml-obex-client committed all changes. ERROR: At least one Sink Engine failed while committing ERROR: At least one object engine failed while writting changes. Aborting ERROR: At least one object engine failed while writting changes. Aborting The sync failed: At least one object engine failed while writting changes. Aborting ERROR: Engine aborting due to an error: At least one object engine failed while writting changes. Aborting contact sink of member 2 of type file-sync just disconnected ERROR: Fewer sink_engines disconnected than connected Main sink of member 2 of type file-sync just disconnected contact sink of member 1 of type syncml-obex-client just disconnected ERROR: Command failed. The recipient encountered an unexpected condition which prevented it from fulfilling the request. The transport is not connected and so it cannot be disconnected. EXIT_ERROR: _recv_event: Command failed. The recipient encountered an unexpected condition which prevented it from fulfilling the request. The transport is not connected and so it cannot be disconnected. ERROR: Command failed. The recipient encountered an unexpected condition which prevented it from fulfilling the request. The transport is not connected and so it cannot be disconnected. Main sink of member 1 of type syncml-obex-client had an error: Command failed. The recipient encountered an unexpected condition which prevented it from fulfilling the request. The transport is not connected and so it cannot be disconnected. All clients have disconnected ERROR: error while synchronizing: NEXT ERROR: "Command failed. The recipient encountered an unexpected condition which prevented it from fulfilling the request. The transport is not connected and so it cannot be disconnected."; NEXT ERROR: "At least one object engine failed while writting changes. Aborting"; NEXT ERROR: "At least one Sink Engine failed while committing"; NEXT ERROR: "At least one object engine failed while writting changes. Aborting"; NEXT ERROR: "Fewer sink_engines reported committed all than connected"; ROOT CAUSE: "Unable to commit change. Error 500" EXIT_ERROR: osync_engine_synchronize_and_block: Command failed. The recipient encountered an unexpected condition which prevented it from fulfilling the request. The transport is not connected and so it cannot be disconnected. ERROR: Command failed. The recipient encountered an unexpected condition which prevented it from fulfilling the request. The request was not successful (-1). EXIT_ERROR: _recv_event: Command failed. The recipient encountered an unexpected condition which prevented it from fulfilling the request. The request was not successful (-1). EXIT_ERROR: osynctool_synchronize: Command failed. The recipient encountered an unexpected condition which prevented it from fulfilling the request. The transport is not connected and so it cannot be disconnected. ERROR: Command failed. The recipient encountered an unexpected condition which prevented it from fulfilling the request. The transport is not connected and so it cannot be disconnected.

[freinhard]

traces with OSYNC_TRACE,SYNCML_TRACE and OSYNC_NOPRIVACY

[freinhard]

syncml-ds-tool -b XX:XX:XX --dumpinfo --slow-sync text/x-vcard Contacts --wbxml --identifier "PC Suite" --useStringTable

---

Message: Remote device was successfully connected. Message: All alerts of the remote device were received. Received device information.

---

BEGIN:VCARD VERSION:2.1 REV:20100110T200441Z N:Mbauer;;;; END:VCARD

---

Message: All changes of the remote device were received. Message: Remote device was successfully disconnected. Message: SyncML session finished successfully. Send the output below to the libsyncml developers

======================================== Man: NOKIA Mod: E65 FirmwareVersion?: SoftwareVersion?: 2.0633.65.01 HardwareVersion?:

MaxMsgSize?: 65535 MaxObjSize?: 3000000 Transport used: OBEX client OMA DS mode used: server Identifier (Source): PC Suite Target: (null)

Datastores:

Locations: ./C:Contacts.cdb

Wbxml: Yes SyncML Version: (null) SupportsUTC: Yes SupportsNumberOfChanges?: Yes SupportsLargeObjects?: Yes

libsyncml Version: 0.5.4 ($Revision: 1075 $)

[sim]

 decoration Changed 1 year ago by admin

 bathtub Changed 1 year ago by admin

 solar system Changed 1 year ago by admin

 stair parts Changed 1 year ago by admin

 solar supply Changed 1 year ago by admin

[nightwolf67]

 penis pumps  male enhancement cream  penis supplement