Hotsync Crashes Syncing Datebook

Symptoms

• The HotSync Manager crashes at the "Synchronizing Date Book" stage. Windows gives a message: This program has performed an illegal operation and will be shut down.
• "HOTSYNC caused an invalid page fault in module DATCN20.DLL at 014f:67ef6228 "
• Inability to delete data from the datebook in Palmdesk 3.0. Every attempt to delete things older than... results in a crash of Palmdesk 3.0, sometimes including Kernel32. Pimlico's dbscan reports no faulty entries in the datebook database on the Palm.
• Unable to hotsync the Datebook data after a hard-reset. View Log shows error message Some Palm organizer records were not copied to the Desktop. Your computer may be full or you may have reached the maximum allowed records on the desktop. To correct this situation, delete some records and HotSync again. But you have plenty of RAM in both the PC and Palm.

Solution

Sounds like your desktop datebook.dat file is corrupted.

If you are not using at least version 4 of the Palm Desktop Software, then upgrade. Version 4 automatically fixes this datebook corruption when it reads in the datebook.dat file.

If, for some reason, you are unable to upgrade to version 4, you can try using the datebook repair tool created by Tobias Oetiker http://oetiker.ch/dtbrc.cgi. It may solve your corruption problem, which would then permit you to hotsync ok. If it does work, you'll need to Hotsync with desktop overwrites handheld. Oh, and be sure to give appropriate thanks to Tobias for the fine tool.

If the above fails, you may need to consider abandoning the desktop version of the corrupt datebook file. Obtain dbscan, install it on your Palm, then run it to ensure that the datebook on your Palm is corruption free. Then perform a hotsync back with the datebook conduit set to handheld overwrites desktop. This should put the clean copy from your Palm back on the desktop.

Back to FAQ's

copyright 2007-2017 Scott W. Leighton