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

IBM Traveler 9.0.1.19 available

 September 6 2017 06:37:33 PM
Today IBM released a new Traveler version called 9.0.1.19 (Build: 9.0.1.19 201708291200_20).

Image:IBM Traveler 9.0.1.19 available

9.0.1.19 brings this new changes:
 
 
  • Support for MS SQL Server 2016 Enterprise Edition.
  • Updated APNS Certificates with expiration 8/1/2018.
  • Improvements for the Run as User Feature.

Fixlist:
APAR # Abstract
LO92524 Sync performance impacted if syncing a large repeating calendar event.
LO92525 Reply notice sent from an FYI recipient for a calendar event when processed on a mobile device.
LO92557 Cancelled event may appear ghosted after the cancel on the iOS Native Calendar application.
LO92638 Add invitee from native iOS Calendar application and the recipient may be added twice to the meeting.
LO92645 Error reading some policy documents when Run as User feature is enabled.
LO92713 User unable to sync when sync request is internally routed from an older server to a 9.0.1.18 or later server.
LO92728 DB Connection exception during migration from Derby to an Enterprise database.
LO92783 Android user incorrectly denied access if specific set of administration settings are enabled.
LO92829 Handle comma character in display name for mail sent from an Outlook client.
LO92881 High CPU may be seen on the database server for one particular SQL query.
LO92897 Update APNS Certificates, new expiration is 8/1/2018.







Note: IBM Traveler 9.0.1.19 does not include a database schema update.

You can download the update as usual on IBM FixCentral.

An IBM Traveler 9.0.1.19 full installation package, which will be available by September 18, 2017, can be used to upgrade any previous Traveler server or to install a new environment.


Kommentare

1Torben Volkmann  09/08/2017 12:49:51 PM  IBM Traveler 9.0.1.19 available

There is a little typo.

LO92897 is vaild until 2018

2Detlev Poettgen  09/08/2017 1:54:45 PM  IBM Traveler 9.0.1.19 available

Thx Torben,

fixed the typo

  •  
  • 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