The remote database may have been restored from backup, or perhaps remote ID '%1' is being used by different remote databases.
Set ml_subscription.progress to zero to re-enable synchronizations for this remote database
Probable cause
Before doing synchronization, the MobiLink server compares the sequence number sent by the client with that stored in the
consolidated database to see if they match. If a remote database is restored from a backup or the last synchronization was
interrupted, the sequence number may be less than that in the consolidated. Please set ml_subscription.progress to zero to
re-enable synchronizations for this remote database.