1847358 - Locking on the mlserver when synchronizing data to the device - SUP

Synchronization taking a long time and seeing the following errors:

SUP server log:

2013-04-08 11:36:23.792 WARN    Mobilink     Thread-227 [com.sybase.ml.sup.Logger] [10050] ODBC: [Sybase][ODBC Driver][SQL Anywhere]User 'DBA' has the row in 'ml_database' locked (ODBC State = 40001, Native error code = -210)
2013-04-08 11:36:23.794 ERROR   Mobilink     Thread-227 [com.sybase.ml.sup.Logger] [-10343] The remote database identified by remote ID '59d43d70-a022-11e2-8000-a4d1d23d9d99' is already synchronizing or the database connection is unusable: unable to access the lock for that remote ID

2013-04-10 15:51:55.146 WARN    Mobilink     Thread-224 [com.sybase.ml.sup.Logger] [10012] The consolidated and remote databases disagree on when the last synchronization took place, the progress offsets are 11 in the consolidated database and 9 in the remote database.  The remote is being asked to send a new upload that starts at the last known synchronization point

mlsrv_err.log:

W. 2013-04-15 10:55:40. <6> [10050] ODBC: [Sybase][ODBC Driver][SQL Anywhere]User 'DBA' has the row in 'ml_database' locked (ODBC State = 40001, Native error code = -210)

• Windows 2008 R2
• SUP 2.1.3, build 2.1.3.358

lock, sa_conn_info, db_lock, mobilink, CPU, data synch,data sync, payload, domain_log, ml_database, locked, 40001, , KBA , MOB-SUP-RT , SUP Runtime , Problem