Server limitations and restrictions

A mobile device user cannot complete registration if the user home mail server is down.

During the registration of a mobile device with HCL Traveler, the HCL Traveler server reads the user home mail server and mail path name from the Domino® directory. It then attempts to contact this mail server to determine if there are any replica mail databases configured for the user. If this home mail server is down during the registration attempt, registration may fail until this server is brought back online or the home mail server entry for this user is changed to a different mail server in the Domino® directory.

Once registration is complete and the HCL Traveler server learns the locations of the mail replicas, then HCL Traveler can redirect push and sync operations to other replicas if the home server is down.

Problems with migrating security data from an enterprise database.

When you configure a stand alone server to use an Enterprise database, the server will migrate existing user and security information to the Enterprise Database. However, if you are moving from an enterprise database to another database, enterprise or standalone, no user or security data is migrated.

Unable to configure HCL Traveler servers with IPv6 addresses.

At this time, IPv6 is not supported by the HCL Traveler server. Support of IPv6 will be evaluated for a future release.

After installing Traveler 9.0.1.15 on an IBM i system configured for HA, the startup of the server fails during the DB schema upgrade to version 20160812.

The DB2 on IBM i server is returning a warning (inquiry message) because of possible data loss, requesting that the client Cancel or Ignore the requested operation. Because this request over JDBC requires an interactive response (typing 'I' to ignore), the server returns an Error Code: -952 with SQLState: 57014 and Reason code 10.

For more information on this problem, and instructions for solving it, refer to Troubleshooting the installation of HCL Traveler on IBM i.

Installer User Interface Mode Not Supported
The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier.

The valid UI modes identifiers are GUI, Console, and Silent.

Though Console is listed as a valid UI mode, it is not supported by the Traveler installer. GUI and silent modes are supported.

Items marked as Private or with $Reader fields that do not contain the HCL Traveler server cannot be synced to the device. This includes mail, calendar, to do, journal and contacts items.

Any document marked Private can only be viewed by the user. Prior to HCL Traveler 9.0.1.18, the Traveler server runs as the server ID and is unable to access private documents.

Starting with HCL Traveler 9.0.1.18, the Run as User feature is enabled by default and the Traveler server can now access and sync private documents.

HCL Traveler authentication does not work correctly when the Domino server is configured to use Security Assertion Markup Language (SAML).

The means by which the SAML identity provider passes the authentication assertion to Domino is currently unsupported in the HCL Traveler environment.

Syncing large items from device to server may be rejected by HTTP's size or timeout limits.

If the device tries to sync a large (many MB) item in a single HTTP request to the server, the server's HTTP limits may reject the request because it took too long to be made or was over the allowed request size limit. For example, trying to send a large mail with attachments from an Exchange ActiveSync device may fail as the protocol does not break up the request into multiple requests. The HTTP limits are in the server document:

Server Document > Internet Protocols > HTTP > Timeouts

Request timeout

Input timeout

Server Document > Internet Protocols > HTTP > Protocol Limits

Maximum size of request content

Server Document > Internet Protocols > Domino Web Engine > POST Data

Maximum POST data (in kilobytes)

HTTP 415 errors

When a request is received, HTTP headers indicate the type of content in the request and if that content has been encoded (for example, compressed). Based on those settings, HCL Traveler will try to interpret the data. If it is unable to interpret the data (for example, the data is not marked as compressed even though it actually is), HCL Traveler will return the HTTP 415 error code for unsupported media type. Most often, this is caused by a proxy or firewall changing the HTTP headers without changing the HTTP body of the request or changing the HTTP body of the request without changing the HTTP headers.

The Remove documents not modified in the last (days) mail file replication setting (known as the cutoff interval) causes the "added to folder" date to be removed from emails that have been in a folder longer than the cutoff interval. The cutoff interval is 90 days, by default.

When Domino sends a request for all email that was added to a mail file within the device's filter window, it returns only those emails that have an "added to folder" date. Therefore, if the device’s filter window is set to 6 months or 1 year, and the cutoff interval is 90, only 3 months of emails are synced to the device.

The "added to folder" date is removed to save space and is done regardless if the Remove documents not modified in the last (days) setting is selected. The date cannot be restored. Extending the cutoff interval only delays the deletion of the "added to folder" date.

This is a temporary condition. Once Traveler has synced the emails onto the device, they are not removed until they age out – until the day they become a day older than the filter window – regardless of the cutoff interval. For example, if your filter window is 6 months, you may start with only 3 months of data, but 3 months later you’ll have 6 months of data on the device.

One potential workaround, although not recommended, is to set the filter window to Unlimited, causing Traveler to sync all emails in the mail file to the device regardless of date, so the cutoff interval does not apply. After the unlimited sync completes, if you change the filter window back down to 6 months or 1 year, Traveler will delete the emails that are outside the new window from the device. This approach is not recommended, because the unlimited sync can take a long time and consume a huge amount of resources, on both the device and the Traveler server.

Follow-up and Junk folders do not sync to the Mobile device.

These folders in HCL Domino® are views and not real folders. Therefore when monitoring folder activity, HCL Traveler does not receive notifications related to these folders.

Execution Security Alert pop-up when opening a mail folder using a Notes® client.

If you create a mail folder on a mobile device that supports mail folder operations using the HCL Traveler client, the folder will be created in your mail database using the HCL Traveler server. Since folders are design elements and must be digitally signed, the folder will have the signature of the HCL Traveler server that created it. By default, your Notes® client will warn you when it detects a signature it has not seen before and will ask permission to allow the action requested by the folder. If you see this warning, select Start trusting the signer to execute this action so that you will not see this prompt again for this action.

Mail attachments are not always included on reply and forward.

If you are replying to or forwarding a mail message on the mobile device that has had its attachments removed because of HCL Traveler truncation options, then you must first retrieve the complete email message and reply to or forward it from the device. This same restriction applies to a large amount of email body text that may have been truncated. In order to resend the entire message from the device, it must first be retrieved using the Download Message option.

Mail documents only appear in one folder.

The HCL Notes® Client allows a single mail document to be in multiple folders or views, but the mail application on the device only allows a single mail document in a single folder. Therefore, the device will only show the mail document in the most recent folder. Sent and Drafts are special in that they are always the "most recent" if the document appears in either one of them.

Folders created on the mobile device do not appear on the Domino® server

If you create a folder on the mobile device, it does not appear on the Domino® server until after the mail database is closed and reopened.

The "Continue Search on Server..." feature does not work.

This makes an Exchange ActiveSync search request to the server for mail with the criteria the user defines. HCL Traveler currently treats all searches as name look-ups and, as a result, does not return anything the device expects.

Sending encrypted mails from a device to Group recipients is not supported.

The sender will receive a notification mail that the message was not sent. The mail will be saved to the Drafts folder.

Mail attachments and in-line images with the same file name might not sync to the mobile device.

If a mail contains multiple attachments or in-line images with the same file name and file extension (such as image.png), these will usually be stored internally in the mail with unique names or identifiers. However, in the event that they are stored with the same names or identifiers, then the user might only see one of these attachments sync to the mobile device. To prevent this problem, users should assign unique file names to attachments and in-line images before attaching them to new mails.

File attachments that are zero bytes in size do not sync to the mobile device.

HCL Traveler ignores file attachments which do not have any content. While it is possible to attach a file without any content to a mail message using the HCL Notes client, these attachments are ignored by the HCL Traveler server and will not be synced to the mobile device.

Calendar filtering does not apply to individual instances of recurring meetings and appointments.

If a recurring meeting includes some instances that match the criteria of the calendar filter and some that do not, all of the meeting instances are synced to the device.

You cannot change repeat settings for a calendar entry after the repeating entry is created.

Notes® does not allow you to change the repeat setting for a calendar entry after it has been created. For example, you cannot change a weekly repeating entry to a daily repeating entry or change a non-repeating entry to a repeating entry.

Not all instances of a repeating meeting display.

If the user creates an infinite event from the device, the Traveler server truncates the event to either 10 instances if there is a yearly repeat rule, or 250 instances otherwise.

Calendar entries past the year 2067, on both the device and server, are not synchronized.

Multiple instances of a repeating calendar event in Notes® that occur within the same day are not supported.

If a repeating calendar event contains multiple instances for the same day and in the same time zone that the event occurs, only one of the instances for that day is sent to the mobile device. HCL Traveler does not support multiple instances of a repeating calendar event on the same day, with respect to the time zone of the device.

Limitations with attachments and calendar events.

You cannot add or remove attachments in calendar events.

Delegate and Propose new time are not supported.

Delegate and Propose new time are not supported. Delegate and Propose new time actions from devices are not supported. .

An invitee's status incorrectly displays as Not responded on the device, but displays correctly in the Notes client

Rescheduling part of a repeating meeting may cause the rescheduled instances to show as Not responded for invitees, even if they have responded to the reschedule. This is caused by selecting a different instance and responding to the series after responding to the reschedule, as the series response does not contain enough information for HCL Traveler to determine the status. Invitees can respond to the reschedule again in order to correct this behavior.

Also, Windows Phone/Tablet, BlackBerry, and iOS devices do not support Delegated as a status, so if an invitee delegates a meeting, only Android devices will show the correct status, others will display the Not responded status.

Meeting notices deleted from a mobile device by a meeting participant still appear in the participant's All Meetings view.

When a calendar event is deleted from the device, the Domino® server removes the meeting notice from the calendar view; however, the meeting notice still appears in the All Meetings view.

Changes made to Domino® federated calendar entries are not synced to the server.

If you configure your HCL Notes® Calendar to display multiple calendar sources and for viewing even when the Notes® client is offline, the calendar will sync to a HCL Traveler device calendar. However, you should not modify these calendar events on the device. If you modify or delete one of these events on the device, the original event will sync back from the server and overwrite the changed event on the device.

Start date is missing from To-do entry

Both Start and Due Date are required fields for tasks. If you have a start date but no Due Date, the start date will be lost.

Start date is the due date

The due date is a required field for tasks. If you have a start date but no due date, the start date is set as the due date. If you do not specify both Start and Due date, the due date is set as Today.

Unable to change the repeat rule for a To-do item after it is created

HCL Notes® does not allow you to change the repeat rule for a task after it has been created. For example, you cannot change from a weekly to a daily repeat, or between non-repeating and repeating.

Dates appear with **** or 9999 as the year in HCL Notes/iNotes.

Domino 9.0 Interim Fix 2 or greater is required for out of office usage in HCL Traveler. Without this interim fix, certain actions when setting out of office will cause the leaving and returning dates to appear incorrect in HCL Notes and iNotes. To return from this state, disable and re-enable out of office from Notes/iNotes.

Out of office appears to be off in HCL Notes/iNotes, but on in HCL Traveler.

The out of office away period can be accidentally extended if the return date is modified before the disabling of out of office has fully taken effect. In order to guarantee that out of office is fully disabled, wait for the out of office summary mail to arrive in the user's inbox before making changes to the out of office leaving or returning date/times.

Additionally, out of office may remain temporarily enabled if it was disabled from Notes/iNotes on a computer with a system clock that is ahead of the mail server's system clock. Out of office will be disabled once the time on the mail server has reached the time that it was disabled from Notes/iNotes.

The leaving and/or returning dates on the device appear to be today and/or tomorrow instead of the set date.

Using HCL Notes or enabling out of office will allow the dates to sync to the device again.

No support for journal syncing.

HCL Traveler does not currently support the syncing of a Journal to a device.

When using the web based administration feature and the Microsoft™ Internet Explorer browser, data is not displayed in views.

Make sure you are using a fully qualified internet address to access the HCL Traveler server. For example, https://traveler1.company.com/LotusTraveler.nsf. If you are using only a hostname without any domain qualifiers, Internet Explorer will disable cookie support for the site. Cookies are required for the web based administration feature to work properly.

When using the web administration Approved Applications view import feature in Microsoft Internet Explorer, a message appears after file is selected stating access is denied.