Closed as program error.
1. WP Syncs with Wait (effectively, push) with sync key 1. 2. WP Syncs without a Wait with sync key 1 (changes may or may not be included from the device). 3. Server responds with sync key 2 (changes may or may not be included from the server). 4. Before the device syncs again, the server detects another change that needs to be pushed. The server finds the Sync with Wait from #1 and tries to use it be putting in the data and sync key 2 (as the request was sync key 1). When the message is tried to be sent, it is rejected because the client really abandoned it when it did #2. 5. WP Syncs with sync key 2. As this is the next, correct sync key, the server commits any previous changes (#3 or #4) as Exchange ActiveSync does not have an explicit acknowledgement of previous server changes being received by the device, so the sync key is an implied acknowledgment. However, the changes in #4 were not actually received by the device, so the device data is now out of sync with regards to the changes in #4. These changes could be adds, updates, or deletes and for any data type (mail, calendar or contacts).
Turn the application off in the sync settings on the device and then turn it back on.
Customer reported that some folder move actions were not synced correctly between Windows Phone device and the Domino server copy of their mail.
The Notes Traveler server was updated to resolve this problem.
This fix will be included in 126.96.36.199 and any future releases. See this technote for the latest Notes Traveler maintenance release information: http://www.ibm.com/support/docview.wss?uid=swg24019529
Reported component name
LOTUS NOTES TRA
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
LOTUS NOTES TRA
Fixed component ID
Applicable component levels