On Sun, 2010-05-30 at 18:46 +0100, Anssi Saari wrote:
Patrick Ohly <patrick.ohly(a)intel.com> writes:
> Can you also provide the second oldest log of laptop and phone?
The real problem is in that log. The phone fails to delete an event or
[2010-05-28 17:36:20.366] WARNING: RECEIVED NON-OK STATUS 412 for command 'Delete'
(outgoing MsgID=2, CmdID=12)
[2010-05-28 17:36:20.367] Status: 412: originator exception
+–[2010-05-28 17:36:20.367] 'SessionAbort' - Aborting Session, Status=412,
ProblemSource=REMOTE [--][++] [->end] [->enclosing]
[2010-05-28 17:36:20.367] WARNING: Aborting Session with Reason Status 412 (REMOTE
The Synthesis engine treats this as a fatal remote error and stops the
session. In the next sync, the phone tries to resume the session, but
because of the fatal error, the Synthesis engine didn't save any suspend
state and thus refuses to resume:
[2010-05-30 14:49:15.790] Alerted (code=225) for two-way Normal Sync
[2010-05-30 14:49:15.791] Created command 'Alert' (outgoing)
[2010-05-30 14:49:15.791] ALERTED from client for normal Sync
[2010-05-30 14:49:15.775] (Saved) fResumeAlertCode = 0 (valid for >DS 1.2 only)
[2010-05-30 14:49:15.775] Cannot resume, suggesting a normal sync
It is unclear from the logs why the phone failed to delete something.
The standard mentions one case for this:
In synchronization protocol cases where the client sends a Map
command to the server, the server MUST always specify the client
identifier for any data items to be deleted. Otherwise, the
(412) Incomplete command exception condition is created and no
data items will be deleted by the client.
But I have no idea whether this applies here. Hmm, it seems it does:
–[2010-05-28 17:36:18.387] 'issue' - issuing command,
Cmd=Delete [--][++] [->end] [->enclosing]
* [2010-05-28 17:36:18.387] Item remoteID='', localID='',
* [2010-05-28 17:36:18.388] Delete: issued as (outgoing MsgID=2,
CmdID=12), now queueing for status
* [2010-05-28 17:36:18.388] Outgoing Message size is now 1006
There really is no remoteID here. I'm unsure how that can happen. Lukas,
do you have any idea?
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.