|
|
#1
2006-09-28, 22:41
|
|||
|
|||
Can't sync using 2.9.9.1
I've used all the 2.9.x.x betas with no problem. The last one won't allow me to sync. I've removed it and reinstalled with the same problem. I reverted back to the stable version and it works fine. I have the log file and will paste it below, in case this helps.
<meta http-equiv="content-type" content="text/html;charset=UTF-8"> <style type="text/css" media="screen"><!-- .block { color: #0000FF; font-weight: bold; } .attribute { color: #009999; } .error { color: red; font-weight: bold; } .hotalone { color: #000000; font-weight: bold; } .hot { font-weight: bold; } .script { color: #996633; } .filter { color: #997F66; } .match { color: #A95E38; } .dbapi { color: #CC3366; } .plugin { color: #9151A3; } .incoming { color: #196D00; } .outgoing { color: #002C84; } .conflict { color: #990000; } .remote { color: #709900; } .proto { color: #777100; } .rest { color: #AAAAAA; } .exotic { color: #FF9900; } pre { font-size: 90%; } --></style> </head><body> <li><span class="block">[2006-09-28 15:18:05] 'AppRun' - PalmOS Client App, Version 2.9.9.1<span class="attribute"></span></span></li><ul> </ul><li><span class="block">[2006-09-28 15:18:05] End of 'AppRun'</span></li> <li>AUTOSYNC: Checked Level 0 at 2006-09-28 15:18:06 - is active, whynot=0x0000, next check at 2006-09-28 17:00:00</li> <li>AUTOSYNC: Chosen Level 0, new mode=none, whynot=0x0000, next check (including regular batt/mem checks) at 2006-09-28 15:19:06</li> <li>AUTOSYNC: Checked Level 1 at 2006-09-28 15:18:06 - cannot be active, whynot=0x0001, next check at <never></li> <li>AUTOSYNC: Checked Level 2 at 2006-09-28 15:18:06 - cannot be active, whynot=0x0001, next check at <never></li> <li>AUTOSYNC: Checked Level 0 at 2006-09-28 15:19:51 - is active, whynot=0x0000, next check at 2006-09-28 17:00:00</li> <li>AUTOSYNC: Chosen Level 0, new mode=none, whynot=0x0000, next check (including regular batt/mem checks) at 2006-09-28 15:20:51</li> <li>AUTOSYNC: Checked Level 1 at 2006-09-28 15:19:51 - cannot be active, whynot=0x0001, next check at <never></li> <li>AUTOSYNC: Checked Level 2 at 2006-09-28 15:19:51 - cannot be active, whynot=0x0001, next check at <never></li> <li><span class="block">[2006-09-28 15:19:52] 'DoSyncSession' - Run a sync session<span class="attribute">, AutoSyncSession=no</span></span></li><ul> <li>TSyncSession::TSyncSession: Session ID assigned</li> <li>TSyncSession::TSyncSession: Profiling initialized</li> <li><span class="hotalone">NetLibOpen returns palmerr=0, neterr=0</span></li> <li>doSync, just before starting session: device is mobile</li> <li>tcpOpenConnection: opened new socket=0x00000001</li> <li>tcpOpenConnection: connected socket</li> <li>==== exchangeXPTMessages: Starting to prepare sending request</li> <li><=== smlLockReadBuffer returned Answersize=1559, err=0x0000</li> <li>sending with docname = 'cal'</li> <li>==== exchangeXPTMessages: Request sent, now waiting for answer</li> <li>received docname = 'cal'</li> <li><span class="hotalone">===> Content-Type = 'application/vnd.syncml+wbxml; charset="utf-8"'</span></li> <li>AnswerDataBufSize = 40000</li> <li>commInfo->cbLength (expected number of bytes)= 0</li> <li>Reading data (max 40000 bytes)</li> <li>Received 0 data bytes, expecting 0 more)</li> <li>===> Totally received 0 bytes</li> <li><span class="error">Actual data seems to be 'undefined', but content type said 'application/vnd.syncml+wbxml; charset="utf-8"'</span></li> <li>closing connection because of: Session done or restarted</li> <li>tcpCloseConnection: closed socket</li> <li>tcpOpenConnection: opened new socket=0x00000001</li> <li>tcpOpenConnection: connected socket</li> <li>==== exchangeXPTMessages: Starting to prepare sending request</li> <li><=== smlLockReadBuffer returned Answersize=1559, err=0x0000</li> <li>sending with docname = 'cal'</li> <li>==== exchangeXPTMessages: Request sent, now waiting for answer</li> <li>received docname = 'cal'</li> <li><span class="hotalone">===> Content-Type = 'application/vnd.syncml+wbxml; charset="utf-8"'</span></li> <li>AnswerDataBufSize = 40000</li> <li>commInfo->cbLength (expected number of bytes)= 0</li> <li>Reading data (max 40000 bytes)</li> <li>Received 0 data bytes, expecting 0 more)</li> <li>===> TotDBLK 
|
|
#4
2006-09-29, 04:08
|
||||
|
||||
Re: Can't sync using 2.9.9.1
Quote:
For the meantime, we have removed 2.9.9.1 from the downloads and made 2.9.8.11 available again, until we find out what's wrong with 2.9.9.1.
__________________
Lukas Zeller, plan44.ch
|
|
#6
2006-09-29, 12:13
|
||||
|
||||
Re: Can't sync using 2.9.9.1
In the meantime, I think we have found the problem:
The server you are trying to sync with seems not fully SyncML compliant: Our client tries to connect with SyncML DS 1.2 first. The server apparently does only understand SyncML 1.1. According to the standard, it should return an error code 513 to tell the client it does not support 1.2. But it just sends an empty response. Now in 2.9.9.1 we added extra checks to tell the user "No SyncML response" when a server does not respond with proper SyncML after some attempts. This is useful if you have a typo in the URL, as it gives a better hint what could be wrong than the ominous "invalid data". However, this new check caused the communication pattern to change slightly, which has apparently made not only the first attempt, but all retries fail. In 2.9.9.2 (will be made available later today), we added a workaround to make the client behave exactly like 2.9.8.11 from the server's point of view. This should make it work again. Let me know if this helps. I'd also be interested to know which server you are using.
__________________
Lukas Zeller, plan44.ch
|
|
#9
2006-09-29, 22:52
|
|||
|
|||
|
Re: Can't sync using 2.9.9.1
It is Oracle's Calendar Application Server (the web component of Oracle Calendar) that provides the syncML server. We are running version 9.0.4.2.44.3095 (the latest for the 9.0.x version of the software).
|
 |
| Thread Tools | |
| Display Modes | |
|
|
Re: Can't sync using 2.9.9.1
Linear Mode
