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?

asked 19 Aug '14, 07:21

Tom%20Mangano's gravatar image

Tom Mangano
632182436
accept rate: 6%

edited 19 Aug '14, 07:24


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.)

permanent link

answered 19 Aug '14, 08:03

Volker%20Barth's gravatar image

Volker Barth
30.6k305455662
accept rate: 32%

edited 19 Aug '14, 08:20

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×295

question asked: 19 Aug '14, 07:21

question was seen: 267 times

last updated: 19 Aug '14, 08:20