The behavior you describe is a feature that is intended to deal with cases of lost connectivity at specific critical points in the synchronization process. You simply need to allow the next sync to clear this disagreement.
There are some known cases where this state cannot be resolved.
- If you are replacing a remote or consolidated from a backup, you need to ensure that the backup brings the remote and/or consolidated to a consistent point - for example, you cannot have a remote that has synchronized at a point in time after the consolidated backup restore point.
- You must ensure that no two remotes have the same remote id.
If you are seeing a persistent case of this warning which is not explained by the items above, you may be encountering a known issue in pre-v16 software that impacts UltraLite clients only. A workaround is to delay any new synchronization after encountering a connection error at the client by a timeframe at least as long as the timeout period for the MobiLink server.
We can determine if the problem you are encounter is potential related to that know issue with -vpe logging level in MobiLink that shows a working remote transitioning to a persistent [10012].
We have addressed this in v16 software. There were two recent changes which are also recommended so using 16.0.0.2178 or later would be recommended if moving to v16.