fighting for truth, justice, and a kick-butt lotus notes experience.

    Anyone else having problems with Traveler

     17 Juli 2015 16:15:35
    I would like to ask you:

    Are you having issues with the latest IBM Notes Traveler version, too?

    Two of our customers already updated their Traveler HA systems to and they are having trouble:

    1. Already enrolled devices are getting an new initiale Sync after Update

       As we can see in the Traveler log, some (not all) devices are starting a new initial sync.
       That behaviour starts after the update to

    2. Users with mail files on remote servers are no longer getting new mails.

    After upgrading Traveler from IF7 to at customer side, we are facing problems with mail synch that no longer works reliable and we are seeing a lot of 503 / Time+out+waiting+for+thread errors..

    "07/10 12:07:03.539" "" Worker-0940 "CN=Frank Test /OU=ATHU/O=COMPANY/CÞ" "action=syncAS&cmd=Sync&CollectionId=4&SyncKey=34&Comment=(Timed+out+waiting+for+thread+DS-0a10%5B4%5D%5BA5661DA5C6F37131D7602CB660B2EA8D%5D%5B17778858%5D+to+complete.)" dp 503 20311 "Apple-iPhone5C2/1208.143" ApplC9LJMYU71234 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

    After the update endusers are reporting, that they will not receive any new mails.

    We already checked the connection between the Traveler and Domino Mail server, where all looks fine and we think, that there is something going wrong in the new Traveler release.

    We are able to reproduce the behaviour.

    The customer is running three different Traveler environments:

    Test (Traveler & Domino 9.0.1 FP4 )
    Production ( Traveler & Domino 9.0.1 FP4)
    Production Pilot (Traveler IF7 & Domino 9.0.1 FP2 HF384)

    We configured three different mail profiles for the same user on the same device. Every profile is using a different Traveler environment. The device is connected using internal WiFi.

    Test & Production  --> Issues with mail sync
    Production Pilot --> working

    We open for both issues PMR's, but we are still waiting for an answer from IBM.

    So, if you are planing to upgrade to Traveler - At the moment I can not recommend it!  

    Update 24.09.2015:

    The issue still exists in Traveler :-(
    The customer got a Hotfix this week for and it looks like the Hotfix solves the issue.
    The Hotfix No. is 9017_20150918_1316_Server_Win.