SQL Anywhere Mobile - Protocol version mismatch error with EBF 3137

Author

Protocol version mismatch error with EBF 3137

Al Norman

2005-07-07, 8:29 pm

Environment:
Windows CE device with ASA version 9.0.2.3137 (from dbsrv9 -v)
Mobilink Server with ASA version 9.0.2.3137 (by looking at Version property
of dbmlsrv9.exe)
Oracle 9.0.2.6

I've been running all day, working on setting up publications and scripts,
when all of a sudden I started getting an error:
SQLCODE -10004 from MobiLink server (protocol version mismatch). The only
change I made was to stop the ML service and add a -zu+ parameter. Now
nothing works. I've tried removing that option, but it's still broken.
Here's the contents of my ml server log file:

I. 07/07 16:59:13. Adaptive Server Anywhere MobiLink Version 9.0.2.3137
I. 07/07 16:59:13.
I. 07/07 16:59:13. Copyright © 1989-2004 Sybase, Inc.
Portions Copyright © 2002-2004, iAnywhere Solutions, Inc.
I. 07/07 16:59:13. All rights reserved. All unpublished rights reserved.
I. 07/07 16:59:13.
I. 07/07 16:59:13. This software contains confidential and trade secret
information of
I. 07/07 16:59:13. iAnywhere Solutions, Inc.
Use, duplication or disclosure of the software and
documentation
I. 07/07 16:59:13. by the U.S. Government is subject to restrictions set
forth in a license
I. 07/07 16:59:13. agreement between the Government and iAnywhere Solutions,
Inc. or
I. 07/07 16:59:13. other written agreement specifying the Government's
rights to use the
I. 07/07 16:59:13. software and any applicable FAR provisions, for example,
FAR 52.227-19.
I. 07/07 16:59:13.
I. 07/07 16:59:13. iAnywhere Solutions, Inc., One Sybase Drive, Dublin, CA
94568, USA
I. 07/07 16:59:13.
I. 07/07 16:59:13. Networked Seat (per-seat) model. Access to the server is
limited to 1 seat(s).
This server is licensed to:
I. 07/07 16:59:13. Developer Edition
I. 07/07 16:59:13. Restricted Use
I. 07/07 16:59:13. <Main>: MobiLink server started
I. 07/07 16:59:13. <Main>: Option 1: -c
I. 07/07 16:59:13. <Main>: Option 2: dsn=smartbus;uid=sma
rtbus;pwd=********
I. 07/07 16:59:13. <Main>: Option 3: -v+
I. 07/07 16:59:13. <Main>: Option 4: -fr
I. 07/07 16:59:13. <Main>: Verbose logging: show row values
I. 07/07 16:59:13. <Main>: Verbose logging: show script names when invoked
I. 07/07 16:59:13. <Main>: Verbose logging: show script contents when
invoked
I. 07/07 16:59:13. <Main>: Verbose logging: show schema for each table
I. 07/07 16:59:13. <Main>: Verbose logging: show an error when the first
read of a synchronization fails
I. 07/07 16:59:13. <Main>: Verbose logging: show translated SQL for prepared
statements
I. 07/07 16:59:13. <Main>: Verbose logging: show rowcount values
I. 07/07 16:59:13. <Main>: Individual database connections will be closed
after synchronization errors.
I. 07/07 16:59:13. <Main>: BLOB cache size: 524288
I. 07/07 16:59:13. <Main>: Maximum number of BLOB bytes to compare:
4294967295
I. 07/07 16:59:13. <Main>: Maximum number of database connections: 6
I. 07/07 16:59:13. <Main>: Maximum number of deadlock retries: 10
I. 07/07 16:59:13. <Main>: Timeout for inactive database connections: 60
minutes
I. 07/07 16:59:13. <Main>: Maximum delay between retries after deadlock: 30
seconds
I. 07/07 16:59:13. <Main>: Rowset size: 10
I. 07/07 16:59:13. <Main>: Upload cache size: 524288 bytes
I. 07/07 16:59:13. <Main>: Download cache memory size: 1048576 bytes
I. 07/07 16:59:13. <Main>: Download cache directory size: 10485760 bytes
I. 07/07 16:59:13. <Main>: Number of worker threads: 5
I. 07/07 16:59:13. <Main>: Maximum number of threads uploading concurrently:
5
I. 07/07 16:59:13. <Main>: Unknown users will be rejected (when there is no
authenticate_user script).
I. 07/07 16:59:13. <Main>: Example scripts will not be automatically
generated for unknown versions.
I. 07/07 16:59:13. <Main>: Local file for remote synchronization logs:
'dbmlsrv.mle'
I. 07/07 16:59:13. <Main>: Stream specifier 1: TCPIP
I. 07/07 16:59:13. <Main>: ODBC DBMS Name: Oracle
I. 07/07 16:59:13. <Main>: ODBC DBMS Version: 09.02.0000 Oracle 9.2.0.6.0
I. 07/07 16:59:13. <Main>: ODBC DBMS Driver Version: 04.20.0081 (B0067,
U0062)
I. 07/07 16:59:13. <Main>: ODBC Version supported by the driver: 3.52
I. 07/07 16:59:13. <Main>: ODBC isolation set to: Read Committed
I. 07/07 16:59:13. <Main>: Connected
I. 07/07 16:59:14. <Main>: Translated SQL:
SELECT COUNT(*) FROM ml_scripts_modified
I. 07/07 16:59:15. <thread 1.1>: Ready to handle requests
I. 07/07 16:59:15. <thread 1.2>: Ready to handle requests
I. 07/07 16:59:15. <thread 1.3>: Ready to handle requests
I. 07/07 16:59:15. <thread 1.4>: Ready to handle requests
I. 07/07 16:59:15. <thread 1.5>: Ready to handle requests
I. 07/07 17:00:21. <thread 1.5>: Working on a request
I. 07/07 17:00:21. <thread 1.5>: Translated SQL:
SELECT last_modified FROM ml_scripts_modified
I. 07/07 17:00:22. <thread 1.5>: ml_scripts_modified last modified at:
2005-07-07 15:40:19
I. 07/07 17:00:22. <thread 1.5>: Translated SQL:
SELECT version_id FROM ml_script_version WHERE name = ?
I. 07/07 17:00:22. <thread 1.5>: ASA synchronization request from: ml_user
(version: init_mdt)
I. 07/07 17:00:22. <1.5> [ml_user]: ODBC isolation set to: Read Committed
I. 07/07 17:00:22. <1.5> [ml_user]: Translated SQL:
SELECT t1.event, t2.script_language, t2.script FROM
ml_connection_script
t1, ml_script t2 WHERE t1.version_id = ? AND
t1.script_id = t2.script_id
I. 07/07 17:00:22. <1.5> [ml_user]: begin_connection <connection> (no
script)
I. 07/07 17:00:22. <1.5> [ml_user]: COMMIT Transaction: begin_connection
I. 07/07 17:00:22. <1.5> [ml_user]: Translated SQL:
SELECT hashed_password FROM ml_user WHERE name = ?
I. 07/07 17:00:22. <1.5> [ml_user]: Translated SQL:
SELECT user_id FROM ml_user WHERE name = ?
W. 07/07 17:00:22. <1.5> [ml_user]: Warning: [10017] The consolidated and
remote databases have different timestamp precisions. Consolidated database
timestamps are precise to 0 digit(s) in the fractional second while the
remote database timestamps are precise to 6 digit(s)
W. 07/07 17:00:22. <1.5> [ml_user]: Warning: [10018] The timestamp precision
mismatch may be resolved by setting the DEFAULT_TIMESTAMP_IN
CREMENT option
on the remote database to 1000000 and TRUNCATE_TIMESTAMP_V
ALUES to 'On'
W. 07/07 17:00:22. <1.5> [ml_user]: Warning: [10020] The timestamp precision
mismatch may affect upload conflict detection. Use the -zp option to cause
the MobiLink synchronization server to use the lowest timestamp precision
for conflict detection purposes
I. 07/07 17:00:22. <1.5> [ml_user]: Publication #1: pub_init, subscription
id: 4, last download time: 1900-01-01 00:00:00.000000
E. 07/07 17:00:22. <1.5> [ml_user]: Error: [-10004] Protocol version
mismatch
I. 07/07 17:00:22. <1.5> [ml_user]: Synchronization failed

Anyone have a clue? I am using the programmatic interface to do
synchronization (i.e. calling DBSynchronizeLog), which has been working.

BTW we're writing a C++ application ....

al

Graham Hurst

2005-07-08, 8:27 pm

Protocol mismatch errors happen when the ML server doesn't understand
what the ML client is sending it. Typically that happens when the remote
is a newer version than the server, since that isn't supported. It can
also happen if one side is specifying encryption and the other side isn't.

Since we haven't released a version newer thatn 9.0.2.3137, I can't see
how you would have a newer remote version than server version. So I'm
guessing you have encryption enabled on the remote and not on the server
(since the log didn't show encryption was enabled).

If not, then it may be time to contact tech support.

Cheers,

Graham

Sponsored Links