Apple troubleshooting

This section contains troubleshooting tips for Apple device users.

For information on known bugs and other limitations related to Apple iOS, as well as how they may impact HCL Traveler, see Known bugs with Apple devices and HCL Traveler.

Troubleshooting performance problems

Performance settings are available to improve mail responsiveness. For more information, see How do I improve mail performance?.

Troubleshooting syncing and connection problems

If you are experiencing sync problems on your Apple device, first determine if the HCL Traveler server is running and that your device can open a data connection to the server. Using the Safari browser on your device, open the URL https://<server>/traveler. (This URL may be slightly different depending on how your administrator has set up your HCL Traveler server. See your administrator for exact details.) If your device successfully connects to the HCL Traveler server, you are prompted for your user ID and password. A web page displays the user status.

If you cannot connect to this page or get another error message, then either the HCL Traveler server is not running or there is a network connection problem between your device and the server. You can also try turning the device off and back on if you are experiencing sync problems.

If you can connect to this page, you may also see additional diagnostic information, such as a message indicating that you may not have the appropriate access list set on your mail file to allow operation of HCL Traveler, the HCL Traveler server cannot connect to your mail server, or that your mail file is currently over quota. This page can provide you with much more diagnostic information than is available on your mobile device.

In some cases you may see an error page indicating other encountered conditions. Contact your company administrator(s) for assistance.

Bookmark this page and add it to your Apple device home screen so that you can easily access this page again later.

Password lockout

The password policy of your company may require that you change your HCL Traveler login password periodically. When you change your password using the password services of your company, you must also remember to change the password on any mobile devices that you own that access the HCL Traveler service. If you forget to do this, then often the mobile device continues to connect to HCL Traveler server or to the service being used as the remote access point using the old password. Many times these systems are set up to lock out the user account after a number of failed password attempts. Since the syncing of the Apple iOS device is largely done in the background on the device, the device continues to try and log in. This can result in your account being locked out on the server.

Changing your HCL Traveler login password

When it is time to change your backend or HTTP password, follow these steps with your mobile device.

Note: If you have more than one device, follow these steps for each device but make sure that you perform step 1 on all of the devices before performing steps 2-4. Otherwise, you lock yourself out on the second device.

On your Apple device, enable airplane mode so that all WiFi and phone data connections are turned off. Select Settings > Airplane Mode > ON.
On your computer, change your HCL Traveler login password per your password change procedures.
On your Apple device, set the password in your HCL Traveler account to be your new HCL Traveler login password. Be careful typing this passsword in, as you do not get a chance to confirm it. On iOS 11 and higher, select Settings > Passwords and Accounts > HCL Traveler acct > Account > Password. In older versions, select Settings > Mail, Contacts, Calendars > HCL Traveler > Account Info > Password.
On your Apple device, disable airplane mode. Select Settings > Airplane Mode > OFF. Re-enable WiFi if necessary.

Troubleshooting password lockout

You may forget about your device when you change your backend system password. As a result, you cannot tell that something is wrong until much later. There are different symptoms for this problem on Apple devices. You may get a pop-up message warning on the device that says your user ID or password is invalid or you may get a message that says the device cannot connect to the server when you open your mail. If your company implements a password lockout policy where your account is locked out of the network after a relatively small number of failed attempts (for example, five), then it is likely that you are locked out of your account.

You can verify this by opening a Web browser on your computer and connecting to https://<server>/traveler (this URL may be slightly different depending on how your administrator has set up your HCL Traveler server. See your administrator for exact details). Enter your HCL Traveler user ID and password when prompted. If a page tells you that your account has been locked, then follow these steps:

On your Apple device, enable airplane mode so that all WiFi and phone data connections are turned off. Select Settings > Airplane Mode > ON.
On your Apple device, set the password in your HCL Traveler account to be your new HCL Traveler login password. Be careful typing this password in, as you do not get a chance to confirm it. On iOS 11 and higher, select Settings > Passwords and Accounts > HCL Traveler acct > Account > Password. In older versions, select Settings > Mail, Contacts, Calendars > HCL Traveler > Account Info > Password.
Contact your administrator, or use your automated services to unlock your account.
On your Apple device, disable airplane mode. Select Settings > Airplane Mode > OFF. Re-enable WiFi if necessary.

Your device automatically connects to the HCL Traveler server and starts to receive mail again.

Troubleshooting Push

If your HCL Traveler administrator is required to reset your account on the HCL Traveler server, then all mail, calendar, and contacts automatically resync with the Apple device. However, if you notice that mail is syncing with the device only when you open a mail folder, then turn push off and on again. Do this by selecting Settings > Mail, Contacts, Calendar > Fetch New Data, setting Push to OFF and then setting it back to ON again.

Problem reporting

All log and trace information for Apple devices using HCL Traveler is available on the HCL Traveler server. To report a problem from the device, use the browser on the device to log in to the HCL Traveler user home page. Select the option to report a problem, and then notify your HCL Traveler administrator.

While there is an option for a file upload on this dialog, you cannot actually upload a file using an Apple device. This ability is intended for PC or other device type users to upload screen captures, mail attachments, or any other descriptive document that might help in solving their problem. However, it is important to note that when filing the problem report the server still collects information and alerts the administrator. As a result, even though Apple users cannot attach files it is still a useful procedure to submit a problem report in this manner.

Error messages for HCL Traveler and Apple devices

The following table contains a list of known error messages you might encounter while using Traveler with an Apple device. Each message contains the application associated with the message, and the likely cause.

Table 1. Apple device error messages
Application/Function	Error message	Cause
Manual Account Setup	New Passcode Required The account `<account name>` starts receiving new data again when a new Passcode has been set. Press Continue to change your Passcode now. Close/Continue	The device passcode is either not enabled or is enabled but insufficient to satisfy the security policy.
Profile Installation	Install Profile IMPORTANT: The authenticity of `<account name>` cannot be verified. Installing this profile changes the settings on your Apple iOS device. Install Now/Cancel	Traveler dynamically generates the Apple Profile, which includes user and server-specific information. As such, it is unsigned. As it always is unsigned, choose Install Now.
Profile Installation	User name or Password are incorrect Without them, no information is downloaded when the installation finishes. Try Again/Ignore	An HTTP 401 response received for invalid user and/or password.
Profile Installation	An error occurred while contacting server Without verifying the account, no information is downloaded when the installation finishes. OK	Possible causes: A connection with the server for an HTTP OPTIONS request could not be made (server is down). The HTTP OPTIONS method is not allowed. You can only disable OPTIONS from the Internet Site Documents. Change the Internet Site Document to allow OPTIONS.
Profile Installation	An error occurred while contacting server `Error Domain=DAErrorDomain Code=0 Operation could not be completed. (DAErrorDomain error 0.)` OK	Possible causes: The HTTP OPTIONS response has non-OPTIONS data in it. Often, this is caused by a proxy not allowing the OPTIONS request to flow all the way to Traveler. Instead, it returns a different web page (normally a login form) instead. The Host in the Apple profile has a server name or address that cannot be resolved. Make sure that the address in the resulting profile is accessible from the device's network.
Profile Installation	An error occurred while contacting server `Domain=kCFErrorDomainCFNetwork Code=303 UserInfo=0x4220400 Operation could not be completed. (kCFErrorDomainCFNetwork error 303.)` OK	The HTTP OPTIONS response was an HTTP 500 (Internal error).
Profile Installation	Could not connect Connection to the server for account `<account name>` could not be established. This may be due to an authentication error. Cancel/Ignore	The HTTP OPTIONS response was an HTTP 449 (Provision required)
Profile Installation	Could not contact server <server name> is not responding. The account information cannot be verified to ensure a correct installation. Try Again/Ignore	The HTTP OPTIONS response was not received (within 30 seconds).
Profile Installation	Policy Requirement The account `<account name>` requires encryption which is not supported on this Apple iOS device. OK	The device encryption requirement is enabled in the Traveler default settings or a policy, and the device does not support encryption.
Profile Installation Manual Account Setup Sync	Unable to Verify Certificate The certificate from `<server name>` for account `<account name>` could not be verified. Accept/Cancel	HTTP server is using a self-signed or not trusted signed SSL certificate for HTTPS.
Safari	Accept Website Certificate The certificate for this website is invalid. Tap Accept to connect to this website anyway. Accept/Cancel	HTTP server is using a self-signed or not trusted signed SSL certificate for HTTPS.
Sync	Password Incorrect Enter the password for `<account name>` Password Cancel/OK	HTTP 401 response received. Possible causes: The user and password were not successfully verified during Profile Installation or Manual Account Setup. The password has changed on the HTTP server and must be updated.
Sync - Mail	Cannot Get Mail The connection to the server failed. OK	A connection could not be established with the server. If the connection is established but the device times out waiting for a response, no message is shown and the request is retried.
Sync - Mail	Cannot Send Mail Check the settings for the outgoing servers in Settings > Mail, Contacts, and Calendars. OK	A connection could not be established with the server to send a message, or there is a problem with the email address as specified.
Sync - Mail	Unable to Move Message The message could not be moved to the mailbox Trash. OK	A connection could not be established with the server to delete a message. Message deletion is performed as a move to Trash.
Sync - Mail	Unable to Move Message The message could not be moved to the mailbox <folder name>. OK	A connection could not be established with the server to move a message to another folder.

Troubleshooting meeting notice routing problems

Invitations and other meeting notices will be routed via the HCL Traveler server's mail.box when the meeting chair creates or updates the meeting from an Apple iOS or iPadOS Calendar application on a device syncing with Microsoft Exchange ActiveSync 16.0 or 16.1. This is the default behavior for HCL Traveler version 11.0 and later. Failure to have routing and connection documents configured on the HCL Traveler server to/from the mail servers can prevent meeting notices from being received by the chair and/or invitees of the meeting.

To avoid routing these notices through the HCL Traveler server, the notes.ini setting NTS_AS_SEND_NOTICES_FROM_MAIL_SERVER can be set to True to route the notices via the user's mail server mail.box. See Notes.ini settings for additional details.

Indications that the Traveler server may not be configured correctly to route notices include one of more of the following Traveler log messages:

FINEST threadid username DominoCnS.createOrUpdateMeetingFromVEVENT

Error 4809: Error sending notices from createEntry. We will update instead.

The following 2 messages may indicate the issue but only if one or both are occurring on all chair meeting changes from device:

WARNING username Error processing iCalendar create or update

SEVERE username An error occurred while attempting to update your database with data 
from the device (ERR_ITEM_REFUSED_BY_BACKEND)

Additional Domino console.log debug messages using notes.ini settings (CSDebugApi=1, DEBUG_CS_LEVEL=129, CSReportErrors=1) may show the following messages:

ERROR | Release dominoversion | csnotice.cpp(693) : The remote server is not a known TCP/IP host. (0x1C63)

Error connecting to server mailservername: The remote server is not a known TCP/IP host.

A Domino trace command to the target mail server run from the Traveler server's Domino console may provide more specific information about the configuration problem. For multi-domain environments, the field FromDomain=traveler server domain may be added to the EAS 16.x generated notices which will cause attendee replies to be routed back though the Traveler domain to the chair user. An indicator that the mail server(s) or Traveler server(s) cannot route notice replies to Traveler built notices is that attendees receive delivery failure messages for the notice replies. In this case, the mail servers may not have connection documents etc. to the Traveler servers or vice versa.