Typical HotSync Errors and Possible Solutions

Id16 CategoryPalmPilot
TopicSynchronizing with the Desktop Last Updated2007-11-15 10:10:00
TitleTypical HotSync Errors and Possible Solutions

HotSync Errors & Possible Solutions


Synchronization software of any type is prone to error. This is due to the nature of synchronization: comparing two separate data sources and determining if the data has changed, stayed the same, or been deleted. This process is complicated even further when synchronizing between two totally different platforms. The way that each platform internally disguishes between what would appear to us to be identical values is quite complex and different (ie: Palm-based handhelds look at a number one way, and a desktop PC looks at that same number in quite a different way). To help reduce the number of errors there are checks and balances put in place. When those don't work, an error occurs.


There are a variety of errors that can occur during a normal HotSync operation. Below are some possible solutions to those errors found in the HotSync error log. Due to a number of factors this is by no means a comprehensive list, but is intended to assist in solving the most common problems. If something isn't working quite right, or data appears to be missing, please check the error log and compare any errors you might find to this list.


Please submit a trouble ticket if you have encountered an error that is not in this list, or if the suggested solution did not work for you.


To view the HotSync error log, click on the red & blue circle icon in the system tray near the time. A menu will popup; choose "View Log" and select the username of the handheld that had the error(s). It is also worth mentioning that sometimes an error won't be reported after the HotSync completes, so checking the error log periodically is considered good practice.


CAUTION: A backup of ALL files that are modified is strongly recommended.


Errors & Solutions

Error: HanDBase error syncing 'TableName': 06/16/06 17:06:55
- SyncExchange failed to execute properly on this database
- Access/HanDBase Merge Failed.
- Error was [Microsoft][ODBC Microsoft Access Driver] The changes you requested to the table were not successful because they would create duplicate values in the index, primary key, or relationship. Change the data in the field or fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entries and try again.

Reason: The handheld will accept the user to input duplicate account names and serial numbers. This error occurs because the desktop database has restrictions that does not allow for duplicate accounts. It can also occur if you have blank account names or serial numbers.

Solution: Remove all accounts with blank account names and serial numbers, or rename the accounts to a unique name/number.


Error: HanDBase error syncing 'TableName': 06/16/06 17:07:49
- SyncExchange failed to execute properly on this database
- Please map columns for export.

Reason: The mapping information required for synchronizing that particular table is missing or corrupt. Mapping information is used to relate the desktop data source to the handheld.

Solution: Remap the synchronization conduit. Search the knowledge base for "Remapping the HotSync Conduit" and follow the instructions for the software product you are having problems with.


We are located at 4500 29th Street, Vernon, BC, Canada | Call us at (250) 503-0893 |
Terms of Use | Privacy Policy | Careers | Our Facility | Copyright © 2006-2024 MTS Maintenance Training Systems, Inc.