SAP Knowledge Base Article - Preview

2180046 - MobiLink client does not sync after upgrading from 11 to 16

Symptom

  • Synchronization fails after upgrading consolidated and remote from SQL Anywhere 11 to 16
  • dbmlsync log shows the following error with some garbled message with high verbosity (-v+):

I. 2015-05-21 12:43:00. Upload operations on table 'sysdbid_global_database'
I. 2015-05-21 12:43:00. Insert row:
I. 2015-05-21 12:43:00.   <sysdbid_global_database_id>: 111
I. 2015-05-21 12:43:00.   <sysdbid_description>: s on table 'sysdbid_global_database'\x00\x00\x00umn,zugenscript_script,zugenrsv_db_reserved_word,zudply_deploy_update,z
I. 2015-05-21 12:43:00.   <sysdbid_machine_id>: plyblb_deploy_blob,vocabs_vocabulary_domains,valsets_value_sets,team_setup,sysrun_run_command,sysdbi
I. 2015-05-21 12:43:00.   <sysdbid_created_user>: _global_database,sysadh_system_administrator,synormstd_norm_standard,sylog_event_audit,syhelp_local_
I. 2015-05-21 12:43:00.   <sysdbid_created_date>: 0000-01-00 01:41:00.000104
I. 2015-05-21 12:43:00.   <sysdbid_changed_user>: p_menu,stdtrp_standard_trip,smokingu_setup,sdrtrf_sdrt_referral_source,sdrtpr_sdrt_primary_reason,sdrtns_sdr
I. 2015-05-21 12:43:00.   <sysdbid_changed_date>: 0000-01-00 01:35:00.000116
I. 2015-05-21 12:43:00.   <created_global_database_id>: 115
I. 2015-05-21 12:43:00.   <changed_global_database_id>: 101
.
.
.
.
I. 2015-05-21 12:43:01. Table Upload Order: zugentblt_table,zugentblc_table_column,zugenscript_script,zugenrsv_db_reserved_word,zudply_deploy_update,zdplyblb_deploy_blob,....{table list continues}
E. 2015-05-21 12:43:01. Data read failed.  Requested 2 bytes but got 0 bytes.
E. 2015-05-21 12:43:01. Unable to read 0 bytes.
I. 2015-05-21 12:43:01. End synchronizing subscription(s) 'basic'
I. 2015-05-21 12:43:01. Disconnecting from MobiLink server
I. 2015-05-21 12:43:01. Complete log scan required.
I. 2015-05-21 12:43:01. Synchronization completed

  • mlsrv16 log shows the following error with high verbosity (-vx+):

I. 2015-05-21 12:43:01. <1> sending resp: handle=21, id=MLRESP_OK
                       
I. 2015-05-21 12:43:01. <1> sending resp: handle=22, id=MLRESP_OK
                       
E. 2015-05-21 12:43:01. <1> [-10001] Protocol error: 131121
I. 2015-05-21 12:43:01. <1>  failed reading command with id:49 and handler:23
E. 2015-05-21 12:43:01. <1> [-10001] Protocol error: 400
E. 2015-05-21 12:43:01. <1> [-10410] The client failed to send a complete sequence of commands
I. 2015-05-21 12:43:01. <1> Synchronization failed
I. 2015-05-21 12:43:01. <2> got cmd: handle=34, id=MLCMD_HELLO3, len=32
I. 2015-05-21 12:43:01. <2> got cmd: handle=35, id=MLCMD_USER_INFO, len=83


Read more...

Environment

  • Any supported versions of Sybase SQL Anywhere
  • Any supported versions of SAP SQL Anywhere
  • Any supported versions of MobiLink
  • Any supported Windows OS

Product

SAP SQL Anywhere all versions ; SQL Anywhere all versions

Keywords

ASE, anyhwere, synch, sync, ML, problems, synching, error, protocol error, path, EBF, issue , KBA , BC-SYB-SQA , SQL Anywhere (on premise, on demand) , BC-SYB-SQA-ML , SQL Anywhere - MobiLink , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.