HCL Notes and Domino 9.0 Social Edition Forum - Traveler: this sync will be stopped to avoid infinite sync loops

This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal

Share ▼
Subscribe ▼

~James Zeknilitlen

Jul 20, 2016, 12:41 PM

2 Posts

Traveler: this sync will be stopped to avoid infinite sync loops

Category: Notes Traveler
Platform: Windows
Release: 9.0
Role: Administrator
Tags:
Replies: 11

For some Domino Traveler users i found the following error message on Domino console, and mobile client stops to synchronize mail:

"Traveler: WARNING <user name> Client has sent 11 effectively empty messages and the server has nothing pending, so this sync will be stopped to avoid infinite sync loops".

So, the only solution i found to make the sync works again, is to re-install the traveler client application.

Any suggestion?
Thanks, Michele

This is the environment: Domino 9.0 with Traveler 9.0.1.12.
Mobile client: Samsung SM-G900F - Android 5.0 or LGE LG-D855 - Android 5.0

~Vera Zekfoogengon

Jul 20, 2016, 2:32 PM

196 Posts

Do the users with the problem share anything in common?

Are those affected by the problem using the same kind of device, or have upper ASCII characters in their names?

~James Zeknilitlen

Jul 21, 2016, 7:56 AM

2 Posts

Traveler users

The users affected by the problem uses different device for example Samsung SM-G900F and LGE LG-D855, both with Android 5.0.

Their name does not contain strange characters but have the middle name.

~Vanessa Optoogenoden

Jul 22, 2016, 8:04 PM

22 Posts

RE:Traveler users

Hi Michele,

I researched our support database for reports with similar messages, but there isn't a specific root issue documented.

We would need matching sync logs from both the client and server ( on finest for user) leading up to when the message first gets displayed.

When this happens, is the users mail file still being monitored? (ie user dump) Have you tried running maintenance
on the user's mail file? Had you tried a reset on the device before removing and reinstalling the client? Typically we don't
recommend running reset unless we know of a specific issue say with the meta data that needs to be fixed. In many cases,
a reset may only provide temporary relief and the issue occurs again especially if it is related to a specific email/calendar/contact
entry.

~Vera Zekfoogengon

Jul 26, 2016, 9:58 PM

196 Posts

A followup question

Do the affected users all have a middle name?

~Martha Nontoosonynds

Jul 29, 2016, 1:29 AM

1 Posts

I have the same problem

Hi Don

From the beginning 2016/7/6 28 user have this problem. I reset device(Tell Traveler Reset * <user name>) and device sync but after a while has same problem. "Traveler: WARNING <user name> Client has sent 11 effectively empty messages and the server has nothing pending, so this sync will be stopped to avoid infinite sync loops"

I dump user file

------------------------------------------------------------------------------------------
LGUID: 33627398 ModTimeInGud: 1469753382 (07/29/2016 08:49:42) ModTimeInDevice: 1469753280 (07/29/2016 08:48:00) ModTimeInBe: 1469753280340 (07/29/2016 08:48:00) FolderGudRecordId: 28451911 Cache1: 2 Cache2: 1 Cache3: 1469753280 (07/29/2016 08:48:00) Type: 5167 (EMail) Folder: 5156 Hashcode: -1341730476
28451908: Android_28e34ecd381317fd timeSyncInDevice: 0 timeSent: 0 DeviceRecordId: null tsTaggedForSlowSync: 0 mChangeData: 0 mChangeMove: 0 mChangeRead: 0 mFolder:28451911 mType:5167 [OOD]
------------------------------------------------------------------------------------------
LGUID: 33627456 ModTimeInGud: 1469753445 (07/29/2016 08:50:45) ModTimeInDevice: 1469753407 (07/29/2016 08:50:07) ModTimeInBe: 1469753407260 (07/29/2016 08:50:07) FolderGudRecordId: 28451912 Cache1: 2 Cache2: 1 Cache3: 1469753406 (07/29/2016 08:50:06) Type: 5167 (EMail) Folder: 5156 Hashcode: 1960686767
28451908: Android_28e34ecd381317fd timeSyncInDevice: 0 timeSent: 0 DeviceRecordId: null tsTaggedForSlowSync: 0 mChangeData: 0 mChangeMove: 0 mChangeRead: 0 mFolder:28451912 mType:5167 [OOD]
------------------------------------------------------------------------------------------

IBM Traveler Version: 9.0.1.11 Build 201605161610_40
Domino Version: Release 9.0.1FP3|January 12, 2015
No middle name
Mobile client: HUAWEIHUAWEITIT-AL00

~Vanessa Optoogenoden

Jul 29, 2016, 5:35 PM

22 Posts

RE: I have same problem

Did you have finest sync logging enabled for this user before seeing these messages?
The user dump by itself will more than likely not contain information about why the server
is logging the message. Please open a PMR so the support team can assist in the collection of logs and analysis of the content.

~Ethan Umfanavitchjip

Aug 1, 2016, 3:09 AM

2 Posts

Re: Traveler: this sync will be stopped to avoid infinite sync loops

I saw this on our server yesterday.

Traveler: WARNING username Client has sent 11 effectively empty messages and the server has nothing pending, so this sync will be stopped to avoid infinite sync loops

The user visited me today saying all mail had stopped, I did a tell traveler reset * username/ou and the device synchronized. Still monitoring things to see if this stops again but the server message has stopped appearing. The only change I did was patch the server to 9.0.1 FP6 over the weekend, that might be unrelated. Traveler version 9.0.1.12 Build 201607061004_20.

Client was latest Verse for android.

David.

~Vanessa Optoogenoden

Aug 3, 2016, 2:31 PM

22 Posts

Re; Traveler: this sync will be stopped to avoid infinite sync loops.

David,

We believe we have identified the issue in processing certain SyncML requests with the the <MoreData/> element while body truncation is enabled.
There is a workaround to avoid the issue. The workaround is to disable the mail body truncation (attachments can still be limited). This will prevent
future occurrences.

LO89840

Local Fix:

1. Delete the mail or move the mail to a non-syncing folder (in
Notes or some other client that isn't the mobile client having
the sync issue) and reset the device (on the server).

2. Change the client settings to not truncate the body of the
mails (attachment settings don't apply) and reset the device (on
the server).

In addition to seeing the "Client has sent 11 effectively empty messages..." message, there will be a 408 returned by the
Traveler server indicating that the session has expired.

In order to be notified in the future a resolution to this issue, IBM recommends customers open a PMR so the issue may
be tracked through the normal support process. Sorry for any inconvenience this may have caused.

~Vanessa Optoogenoden

Aug 5, 2016, 12:10 AM

22 Posts

Re:Traveler: this sync will be stopped to avoid infinite sync loops - LO89840

APAR LO89840 has been opened to track this issue.

~Tip Reresagenetsi

Nov 4, 2016, 6:01 AM

52 Posts

Middle name?

Dear Michele/Jay,

I got the same error for a user and an internet search turned up this forum post.

In my case, the affected user has a middle name.

Why were you asking this?

And is there something I can do to fix this?

Kind regards,

Nad.

~Vera Asajumiterjip

Nov 14, 2016, 2:20 PM

23 Posts

Same issue with Traveler 9.0.1.13

IBM said, that "This fix will be included in IBM Traveler server 9.0.1.13 and all later releases". But I have Traveler 9.0.1.13 and see this warnings on console as well (for only one user)

Share ▼
Subscribe ▼