HCL Traveler V11.0.1 Fix List

At the end of March, Traveler V11.0.1 was released, which includes several new features and fixes for known issues. This list will tell you if the update is right or necessary for you.

New Features:

  • Support for Microsoft SQL Server 2017
    Traveler has been validated with Microsoft SQL Server 2017 as the Traveler server database when running in high availability mode.
  • Updated APNS Certificates
    Traveler 11.0.1 includes updated APNS Certificates that replace the certificates shipped with Traveler These new certificates expire February 13, 2021.
  • Support for cross-domain ID vault
    When working with encrypted mail, Traveler now supports retrieval of a user’s Notes ID file from an ID vault that is in a different Domino domain than the Traveler server. See Supporting multiple HCL Domino domains for more information.

Fix List:

Customer Problem #
TRAV-4441Traveler server shows thousands of errors are logged in the Domino console Details: When Traveler encounters problems accessing the UnreadTable for a user or users, a large number of severe errors are logged to the console.  This fix reduces the severe logging for UnreadTable access errors.
TRAV-4383Server crashes since upgrading to Traveler 11.0 Details: After upgrading to Traveler 11.0, servers started crashing with LSXBE: ****** Out of Backend Memory ******* errors in the console. Fix addresses memory leak associated with these crashes.
TRAV-4348APNS push notifications working only for HCL Verse for iOS Details: Starting with Traveler 11.0.0, applications other than Verse for iOS that use APNS notifications (Verse for Citrix, To Do, MaaS360 and Third Party registered applications such as Virtual Solutions SecurePIM client) were having those notifications rejected by the Apple APNS servers with the rejection reason of “DeviceTokenNotForTopic”. This fix corrects the topic to be correct for all applications using APNS notifications.
TRAV-4331Traveler server reporting red status due to native memory usage on Microsoft Windows Servers Details: The Traveler server method of calculating native (C) memory usage in the Windows environment was incorrectly leading to Traveler reporting a red status for native memory usage.  Traveler has changed to use the Traveler process memory instead of total system virtual memory for C memory usage calculations on Windows servers.
TRAV-4314Add Outlook (IMSMO) client safety that sets push flags if SyncML gets to 50 messages Details: To protect itself from stack overflow issues, the IMSMO client will stop the sync after 50 SyncML messages to then start a new sync. There are some cases where the client does not start a new sync but does connect to push on the server. The push flags are already cleared based on the sync (as they should be), so the client does not sync again until some other data is changed such as receiving a new email. This changes the server to set the push flags for the IMSMO client if the sync reaches the 50th SyncML message so that if the client does not sync again but does connect to push, push will cause the needed sync to be started.
TRAV-4307After an upgrade to Traveler, when running with the Derby database, some devices were missing contacts/calendar/email Details: When running Traveler server with the Derby database, a re-sync of a user’s device with a large number of customer folders may take too long for the folder sync request.  This can prevent the user’s calendar, mail, and contacts from syncing to the device. A database indexing hint was added to reduce sync times. This problem can occur in versions including and prior to Traveler
 TRAV-4239Mail sent appears to sender to be 1 hour off Details: Changed the way the Traveler server checks for daylight savings time support on startup in order to prevent a problem with the Casablanca and El Aaiun time zones logging severe errors about a mismatch in DST support.
 TRAV-3733Update APNS p12 files that expire in June 2020 Details: Traveler includes updated APNS Certificates that replace the certificates shipped with Traveler  These new certificates expire February 13, 2021.
Traveler reports red status due to severe message flood from EventContainer.maintainSeqNumbers Details: Reduced the log level of a frequent error caused by processing events with corrupted sequence numbers.

Leave a comment