Mobilink V9.0.2.2451 Error when device tries to sync

[Former Member]

The external device gets this error:

"unable to determine the starting log offset for publication with pub_id = 7 in consolidation database progress = 0011207824, log sent = 0011212507"

"unable to get the last synchronization status"

I turned on detail tracing on Mobilink and here is what it produced.

. 10/25 12:13:34. <thread 1.5>: Translated SQL: SELECT last_modified FROM ml_scripts_modified I. 10/25 12:13:34. <thread 1.5>: ml_scripts_modified last modified at: 2018-10-25 09:55:41.000000 I. 10/25 12:13:35. <thread 1.5>: Translated SQL: SELECT version_id FROM ml_script_version WHERE name = ? I. 10/25 12:13:35. <thread 1.5>: ASA synchronization request from: 285SVSD (version: SVS-D) I. 10/25 12:13:35. <1.5> [285SVSD]: Translated SQL: set temporary option chained = 'ON' I. 10/25 12:13:35. <1.5> [285SVSD]: ODBC isolation set to: Read Committed I. 10/25 12:13:35. <1.5> [285SVSD]: 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. 10/25 12:13:35. <1.5> [285SVSD]: begin_connection <connection> (no script) I. 10/25 12:13:35. <1.5> [285SVSD]: COMMIT Transaction: begin_connection I. 10/25 12:13:35. <1.5> [285SVSD]: Translated SQL: SELECT hashed_password FROM ml_user WHERE name = ? I. 10/25 12:13:35. <1.5> [285SVSD]: Translated SQL: call "svs-d_ml_auth_with_parms"(?,?,?,?,?); E. 10/25 12:13:35. <1.5> [285SVSD]: Error: [-10052] The authenticate_parameters script returned 4000 I. 10/25 12:13:35. <1.5> [285SVSD]: ROLLBACK Transaction: authenticate_user I. 10/25 12:13:35. <1.5> [285SVSD]: Publication #1: 7-Dollar, subscription id: 4, last download time: 2018-10-23 13:49:22.500000 I. 10/25 12:13:35. <1.5> [285SVSD]: Translated SQL: SELECT progress FROM ml_subscription WHERE user_id = ? AND subscription_id = ? I. 10/25 12:13:35. <1.5> [285SVSD]: Progress offsets for the publications that are explicitly involved in the current synchronization I. 10/25 12:13:35. <1.5> [285SVSD]: Subscription id 4: consolidated progress 0 and remote progress 11207824 I. 10/25 12:13:35. <1.5> [285SVSD]: end_connection <connection> delete from ml_subscription s from ml_user u where s.user_id = u.user_id and u."name" = 'svs-d_default_mobilink_user';delete from ml_user where "name" = 'svs-d_default_mobilink_user'; I. 10/25 12:13:35. <1.5> [285SVSD]: Translated SQL: delete from ml_subscription s from ml_user u where s.user_id = u.user_id and u."name" = 'svs-d_default_mobilink_user';delete from ml_user where "name" = 'svs-d_default_mobilink_user'; I. 10/25 12:13:35. <1.5> [285SVSD]: COMMIT Transaction: end_connection I. 10/25 12:13:35. <1.5> [285SVSD]: Disconnected from consolidated database I. 10/25 12:13:35. <1.5> [285SVSD]: Synchronization failed

I am trying to help a company get back to operation after a power outage and disk corruption. The consolidated database is restored and operational. I used extract utility to recreate the remote database.

Everything looks to be working correctly except when external PDA devices come into the Remote database to place a order. This is not working.

I have tracing on the ODBC connection which is being used and it is working. No issues that I can see.

I am not even sure what this message means. Does it mean the Consolidated DB and the Remote DB are out of sync? I have used extract utility and that should have put this remote publisher database at the same data point as the consolidated.

Any ideas or help here?

[chris_keating]

Are these the exact errors (i.e., there has been no translation) that you are getting. I cannot find these specific errors in the error documentation nor in googling the error. I do not have access to the v9 source (it was end of life many years ago). The only error in the MobILink log is:

E. 10/25 12:13:35. <1.5> [285SVSD]: Error: [-10052] The authenticate_parameters script returned 4000 

which is an error that you will need to diagnose since it is in a sync script (which is user-defined).

My guess is that the recovery was not complete and that the server has not been restored without some data loss (specifically the MobiLink system tables). I suspect that the client has been sync successfully prior to the corruption and that the consolidated database was restored to a point prior to that sync.