|
One of my co-workers posted a question last week. No log operation at offset on Aug 15. Re-capping his post, "On occasion, users can't sync because of log file off-set mismatches." Every Monday we TRUNCATE our log file in the consolidated database. Could truncating the consolidated log cause the problem? |
|
If that is the question of your co-worker, and if this is a MobiLink client issue, then I would dare to say a truncated log at the consolidated cannot cause this problem. This is simply because the synchronization process does not rely on the transaction log on the consolidated side but relies on the scripts you write for upload and download events. (In contrast, the synchronization process does fully rely on the transaction log on the remote side, unless you use only scripted upload or download-only publications. Therefore I would suspect that a log file is missing or broken on the remote side, just as Jeff has pointed to in that other FAQ.) |
