Orphaned Devices on Traveler HA SQL

Hi all,

Had a recent issue with a customer using Traveler 9.0.1.4 on Domino 9.0.1.4 where one user had three devices listed all with the same device ID (so essentially the same device). All devices were inactive and we wanted to clear them up. So, I issued the usual console commands:

1. Tell Traveler Delete * <username>
2. Tell Traveler Security Delete * <username>

but Traveler kept saying that no devices were found for the user. Issuing Tell Traveler User <username> confirmed that there were indeed no devices associated with the user. However, in the back-end SQL database i.e. https://lotustraveler.nsf the devices were still showing !

Read Full Post

Traveler 9/Apple issue – “mails from other people appear to come from me”

An issue was reported by multiple users on a customer site recently.   Since a Traveler 9.0.1 upgrade :- mails coming into user’s inbox that are from external Internet senders are showing up in the “who” column as being from the recipient’s name rather than the sender. This is only for some mails though, not all.

The first steps taken were checking the SMTP headers to see had the message been modified by the mail gateway (McAfee).  Everything looked normal.  Checked the Domino logs, nothing unusual there.

Eventually we figured out, the common linkage was that the messages effected were last modified by the Traveler server.  The issue affected Traveler 9 users (who are all Apple iPhone/iPad users on this site) setting follow up flags from their devices.  Once a follow up flag is set on an external sender mail, then the “Who” column displays the person who received the mail rather than the sender in the Notes client (It remains fine on the iPhone/iPad however).

After opening a PMR with IBM, they  didn’t offer an immediate solution but started using the term “principal” field and have escalated to development (at the time of this writing we are still waiting to hear back) we managed to search online ourselves and find this –

http://www-01.ibm.com/support/docview.wss?uid=swg1LO77840

I have to say the title “SET AS FOLLOW UP MAY SET PRINCIPAL TO RECIPIENT” isn’t intatuively understood, but when we read :-

“If user flags a mail for follow up on a Mobile device and the message does not have the standard Principal field, Notes Traveler will mistakenly set the user as principal instead of the sender. This problem is only seen with the 9.0.1 Gold release.”

We understood the issue was exactly the same as ours, though it wasn’t exactly easy to find.  The issue is fixed in 9.0.1 IFI 1.  We’ve installed 9.0.1 IFI2 and the issue was resolved. Implementing the fix does not change back mails that were previously “changed” by the Traveler server.

Quite a simple fix, but even IBM’s own support couldn’t tell us the documented fix!

Another example of the good practice of ensuring that your Traveler server has the latest fix packs and interim fixes applied.

Hope this helps someone else out!  Let us know if it does.

Cormac McCarthy – Domino People Ltd

FLASH: Some users stop receiving updates after upgrade to Notes Traveler 8.5.3 UP2 IF3 (2013.07.23)

IBM have sent out an update today, about 8.5.3 UP2 IF3 where users stop receiving mail.

In short the fix is to upgrade to 8.5.3 UP2 IF4.

The details are documented here

Cormac McCarthy – Domino People Ltd

 

New Traveler 9 Console Commands

There’s a couple of new commands available when you issue a “tell traveler” from the Domino console in Traveler 9, that I haven’t seen documented elsewhere, namely:

tell traveler cleanup and tell traveler netaddr

 “tell traveler cleanup” is designed to force the removal of users that haven’t connected since the allocated cleanup period, [based on what is in the Server Document for the Traveler server, “IBM Traveler” Tab,  “User Cleanup Timeout” field (default is 30 days)].  Note that this should happen automatically with the server in the background.

From running “tell traveler cleanup help” we can see the usage information as follows:

Usage: tell traveler Cleanup <option>

Where <option> includes:

  •   Users – Remove all devices where the last sync time is older than the user cleanup timeout.
  •   Bind – Clean up BIND table entries for unknown server

Running the command without a switch runs both Users and Bind command.

“tell traveler netaddr” tells you which network interfaces are available to Traveler and also. as importantly, which network interface it is  actually using.  I’d imagine this would be a great resource during a migration to new hardware/OS.

From running “tell traveler netaddr” we see the usage information as follows:

(ip address being used is pixelated obviously!)

Let us know if you’ve found this useful or if you’d like any advice on a Traveler 9 deployment!

Cormac McCarthy – Domino People Ltd

Traveler capacity planning and NOTES.INI settings.

IBM have recently published a series of new articles on the Domino Wiki site.  Two articles that really caught my eye were on:-

Capacity Planning on Traveler – haven’t seen as detailed and specific guide as this before

and

Traveler notes.ini settings – it’s great that Traveler customisations are now published and this is a brilliant reference to bookmark.

(Note:  that we already published an example of how to manually change these settings via NTSConfig.xml here – but having these available via notes.ini settings is obviously more straight forward!)

Cormac McCarthy – Domino People Ltd

Traveler – Update on known device limitations

IBM have updated their documentation on known device limitations for Traveler.  Although issues/limitations are decreasing all the time,  if you deploy Traveler, this is a great reference to have and familiarise yourself with:

Please let us know if you experience any issues or limitations that haven’t been documented!

Cormac McCarthy – Domino People Ltd

SSL breaks after upgrading to Traveler 8.5.3 UP 1

On a production upgrade of Traveler to 8.5.3 U.P. 1 yesterday we came across a problem.

The upgrade itself completed without issue but mobile clients couldn’t connect to the server automatically after the server was back up and running.

We could see the following in the log :-

“HTTP Server: SSL Error: Keyring file not found, key ring file [keyfile.kyr], [Default Server]”

So we did some digging.  Before the upgrade the “SSL key file name” field (Server Document -> Ports > Internet Ports- >  SSL key file name) was something other than default (say mobile.kyr for argument’s sake).

After the upgrade this field changed back to the default “keyfile.kyr” automatically!  It is quite an easy fix (either renaming the the .kyr file on the OS and restarting HTTP or renaming the field in the server document and restarting HTTP fixes the problem).

We’ve done a few tests and it doesn’t appear to be reproducible on demand, however it is worth noting in case the same thing happens to you!

Cormac McCarthy – Domino People Ltd.

Traveler 8.5.3.2 Interim Fix 1 released

Overview

Lotus Traveler 8.5.3.2 IF 1 is an Interim Fix release that contains APAR fixes for the Lotus Traveler server and clients. The information below outlines the changes included.

Fix List

See Lotus Traveler APAR Listing

Feature List – new in 8.5.3.2 IF 1

Please ensure to read the detailed instructions.

You can download the fix here. (requires a IBM ID).

Lotus Domino R8.5.3 Interim Fix for Traveler (Win 64bit)

If you are running Lotus Traveler on Domino 8.5.3 FP1 (Windows 64 bit), there’s a new interim fix available that may avoid serious issues (such as server crashes).

Details are available at this IBM tech note – http://www-01.ibm.com/support/docview.wss?uid=swg21591859

(please note to download the fix requires an IBM log in)