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

HCL Traveler 11.0.1 released with support for Cross Domain ID-Vault

 31 März 2020 18:38:49
HCL Traveler 11.0.1 is a feature release that includes new features and bug fixes for the Traveler server.

Traveler 11.0.1 can be used to install a new Traveler environment or update an existing Traveler environment running Domino 9.0.1.x, Domino 10.0.x, or Domino 11.0.x without requiring a Domino upgrade
.

(Although it is always recommended to keep Domino at the latest level.)


Database Schema


Traveler 11.0.1 does include a database schema update.


New Features

Support for Microsoft SQL Server 2017
Traveler 11.0.1.0 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 10.0.1.2.  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.
More details can be found here: https://help.hcltechsw.com/traveler/11.0.0/Plan_Domino_domains.html

Fix List


TRAV-4441 Traveler server shows thousands of errors are logged in the Domino console

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-4383 Server crashes since upgrading to Traveler 11.0

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-4348 APNS push notifications working only for HCL Verse for iOS

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-4331 Traveler server reporting red status due to native memory usage on Microsoft Windows Servers

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-4314 Add Outlook (IMSMO) client safety that sets push flags if SyncML gets to 50 messages

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-4307 After an upgrade to Traveler 11.0.0.0, when running with the Derby database, some devices were missing contacts/calendar/email

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

 TRAV-4239 Mail sent appears to sender to be 1 hour off

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-3733 Update APNS p12 files that expire in June 2020

Traveler 11.0.1.0 includes updated APNS Certificates that replace the certificates shipped with Traveler 10.0.1.2.  These new certificates expire February 13, 2021.

TRAV-2984 Traveler reports red status due to severe message flood from EventContainer.maintainSeqNumbers

Reduced the log level of a frequent error caused by processing events with corrupted sequence numbers.


Details:
https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0076377


Kommentare

1Sarah  19.01.2021 18:55:59  Error on your website

It looks like you've misspelled the word "hier" on your website. I thought you would like to know :). Silly mistakes can ruin your site's credibility. I've used a tool called SpellScan.com in the past to keep mistakes off of my website.

-Sarah

2Jarred  19.01.2021 18:56:45  Error on your website

It looks like you've misspelled the word "coppe" on your website. I thought you would like to know :). Silly mistakes can ruin your site's credibility. I've used a tool called SpellScan.com in the past to keep mistakes off of my website.

-Jarred

3Randy  20.04.2021 13:53:43  Error on your website

It looks like you've misspelled the word "hier" on your website. I thought you would like to know :). Silly mistakes can ruin your site's credibility. I've used a tool called SpellScan.com in the past to keep mistakes off of my website.

-Randy

  •  
  • Hinweis zum Datenschutz und Datennutzung:
    Bitte lesen Sie unseren Hinweis zum Datenschutz bevor Sie hier einen Kommentar erstellen.
    Zur Erstellung eines Kommentar werden folgende Daten benötigt:
    - Name
    - Mailadresse
    Der Name kann auch ein Nickname/Pseudonym sein und wird hier auf diesem Blog zu Ihrem Kommentar angezeigt. Die Email-Adresse dient im Fall einer inhaltlichen Unklarheit Ihres Kommentars für persönliche Rückfragen durch mich, Detlev Pöttgen.
    Sowohl Ihr Name als auch Ihre Mailadresse werden nicht für andere Zwecke (Stichwort: Werbung) verwendet und auch nicht an Dritte übermittelt.
    Ihr Kommentar inkl. Ihrer übermittelten Kontaktdaten kann jederzeit auf Ihren Wunsch hin wieder gelöscht werden. Senden Sie in diesem Fall bitte eine Mail an blog(a)poettgen(punkt)eu

  • Note on data protection and data usage:
    Please read our Notes on Data Protection before posting a comment here.
    The following data is required to create a comment:
    - Name
    - Mail address
    The name can also be a nickname/pseudonym and will be displayed here on this blog with your comment. The email address will be used for personal questions by me, Detlev Pöttgen, in the event that the content of your comment is unclear.
    Neither your name nor your e-mail address will be used for any other purposes (like advertising) and will not be passed on to third parties.
    Your comment including your transmitted contact data can be deleted at any time on your request. In this case please send an email to blog(a)poettgen(dot)eu

Archive