|Nothing happens after configuring your Android device. ||Pull down the notification bar at the top to see the download progress.|
|Download progress of LotusInstaller.apk is stuck at "Waiting for data connection" or "connecting".||The default Android browser does not support downloading from a site with a self signed SSL certificate. Connect to your server using HTTP or use a different application to download the installer. |
|Verifying installation||To ensure that you properly install and register the Lotus Notes Traveler Client:
The Lotus Notes Traveler client installation continues. However, if the above message is seen, you may want to close other running applications, or perform a soft reset in order to free up resources.
- Choose the correct APK file for your device
- Android = LotusTraveler.apk
- The IBM® Lotus Notes Traveler client installation checks the device for both required memory and available slots to run. If either of these resources are insufficient, the message "IBM Lotus Notes Traveler client installation has detected insufficient device resources to run this product" displays. The installation log also displays an entry stating "Install is checking your device resources for IBM Lotus Notes Traveler".
- Verify that the server name field does not include http://, https://, port number, or servlet.
- Check client log for additional information.
|Verifying connections||To verify your connection to the server:
- Validate Lotus Notes Traveler server access using firewall or proxy
- Use Check Server tool and browser to further diagnose connection issues
- Check sync protocol.
|Verifying authentication||To verify your authentication with the server:
- Check for correct ACL access to the server
- Check for firewalls that may block access to the server
|Verifying configuration||To verify your configuration with the server:
- Check server ports
- Check sync protocol, for example HTTP or HTTPS.
- Check the AutoSync flag
|Verifying contention||To check other issues between the device and the server:
- Verify that other applications are not starving the Traveler process; shut down non-critical applications.
- Verify that the device is not low on power; plug the device in and shut down non-critical applications.
- Verify that the device is not running out of storage; adjust the Mail/Calendar and Other Applications filters.
- Verify that the device can connect to the internet.
|Verifying security||Security policies are an option that is enabled by the Lotus Notes Traveler administrator. To verify that a device is compliant with a mobile device security policy, see How do I view the security status of my Android device?.|
|Error Number||Error Message||Notes®||Steps to Resolve Error|
|1||The sync data received was not valid.||This is a general error that is reported back by the Sync client when it encounters and error during the processing of the SyncML package provided by the server. In most cases the sync that is in progress aborts.||The user can perform a replace data for all PIM types that they are currently syncing.|
|3||Communications problems with the server||This error is returned if the “InternetOpen” API fails. ||Step 1 - Try to access the server using a web browser on different device or system that has full connectivity.|
Step 2 - try to access the server using the Internet application on the device. If the server seems to be online, make sure you can login using the same userid/password that is on the device. Finally, if that works try to soft reset the device.
|4||The server name does not have a valid form||This error is returned if the server name, provided by the user, contains invalid characters.||Check the server name in the Account settings dialog of the Traveler application. Ensure that the server name is properly formed. Try to access that server using some other means.|
|6||The server name cannot be resolved||This error is returned if the client receives an ERROR_INTERNET_NAME_NOT_RESOLVED status code from the “InternetConnectThread” API.||Same steps for error 4|
|8||Lotus Traveler server is not available||This is the default error return code used by the configuration component for a failed HTTP GET or POST. ||Same steps for error 3|
|9||Sync completed with errors||This is a general error returned by the sync client when a sync failed for one of many possible reasons||Same steps for error 1|
|10||Server is busy||The server returned a status of SML_STATUS_IN_PROGRESS (101) so the client aborted the sync||The user can perform a manual sync if they are concerned that something is wrong. This error should resolve automatically, assuming the server is still operational.|
|11||Record not found during modify/remove||Sync client could not locate the record referenced by the server in a sync operation such as modify or delete.||As in the steps described for error 10 the user can always perform a manual sync. This error is produced for information purposes but the system is basically working fine.|
|13||Out of memory||The client attempted to allocate a block of memory on the device and it failed||Check the available memory on the device and take appropriate action to free up some storage space.|
|16||The sync was canceled by the user|
|17||Invalid user ID or password||The client attempted to perform an HTTP post to the server. The server responded with an authentication error.||Perform steps listed for error 3|
|18||The server reported that access is forbidden for your user ID (403)||The user ID specified is locked out by the server admin.||The server administrator needs to unlock that user.|
|20||The server made an unrecognizable request||The XML provided by the server during a sync operation was deemed to be incorrect. The sync client is sending this error message out for information purposes. This error does not cause the sync to abort.||Perform steps listed for error 1|
|21||Invalid parameter||The sync client was unable to obtain required information from the configuration utility.||Revalidate the user name, password, server name, and http protocol. Ensure that Traveler has the correct information stored.|
|22||Buffer too small||The message provided to the device client by the server exceeds preset maximum message size||In theory this should never happen. If it does it is a defect that must be investigated by the development team. As a workaround the user could follow the steps described for error 1|
|23||Invalid data received from the server during sync||There is a mismatch in the version of SyncML supported by the server and client.||In theory this should never happen. If it does it is a defect that must be investigated by the development team. There are no workarounds for this one.|
|25||Sync failed to initialize||The sync client detected missing functionality that is required for the level of SyncML being used by the server.||Same as error 23|
|26||Sync failed to initialize||Same as error 25||Same as error 25|
|29||Connection error with server %s port %d||The sync client lost its connection to the server.||Same as error 3|
|30||The sync was canceled because of a 500 error||The server rejected a command sent by the client.||Same as error 22|
|31||Sync completed with errors||The client received a record which for some reason the device was not able to add. The failure is not captured by any of the other mechanisms currently defined. Therefore, using SMLERROR_COMMAND_FAILED is insufficient to avoid the server sending it back.||Same as error 22|
|32||Out of memory||Same as error 13 ||Same as error 13|
|33||The Lotus Traveler mailbox could not be found||The Lotus Mail application is either corrupted or does not exist on the device||If the Lotus Mail application does not exist contact IBM Support for a special program that can recreate it on the device.|
|34||An error occurred when attempting to sync data to the storage card||The Android client was instructed to store something on the storage card but the storage card did not have sufficient space to accommodate the request.||Try to free up some space on the storage card. Also, the user should turn off any email settings that direct output to the storage card.|
|35||The Lotus Traveler server is not available. It may not be started or is currently busy (503)||The Android client attempted to connect to the server but could not.||Same as error 3|
|37||The server reported that it encountered an internal error (500)||The client attempted to communicate with the server but the server returned a status 500 which indicates an internal error on the server.||Same as error 10|
|38||The sync ended abnormally. HTTP Status code %d.||The client received an HTTP status error of 415 from the server. This indicates unsupported media and is typically returned when the client compresses the XML package and the server has a problem decoding it. ||Turn off zlib compression on the server.|
|39||Settings update failed to be uploaded to the server. It is reattempted on the next sync||The client attempted to send it's latest configuration settings to the server but was not able to do so.||Same as error 3|
|40||Battery level is too low, so automated features are disabled||The battery power on the device has fallen to low levels.||Charge the device back up.|
|41||Settings update failed to be downloaded from the server. It is reattempted next sync||The server attempted to inform the client about new device settings but there was a connectivity problem preventing the client from obtaining the information updates from the server.||Same as error 3|
|42||Sync has been disabled by your administrator because of a device security policy violation||A security violation has been detected by the Traveler client. The violation action for the security policy in violation was set to disable syncs.||View the current security state of the Traveler client and take the necessary steps required to have security compliance as specified by the server admin.|
|43||Device Security Violation(s)||A security violation has been detected by the Traveler client.||Same as error 42|
|44||The server reported that access is forbidden for your user ID (403)||Same as error 18||Same as error 18|
|45||The server reported an error. View the log for details||General error for various errors reported to the client by the server.||Same as error 3|
|59||The change log service is not running.||For some reason the change log service is not running.||Exit and restart Traveler.|