Home :: 750 :: 700p :: 700w :: 680 :: 650 :: 600 :: General :: Palm Software
Categories :: PageIndex :: Changes :: Comments :: Click to edit
Categories :: PageIndex :: Changes :: Comments :: Click to edit
Most recent edit on 2007-08-19 23:31:30 by WikiEgadgetguy
Additions:
Deletions:
Edited on 2007-08-19 23:30:07 by WikiEgadgetguy
Additions:
Deletions:
Make sure the hotsync program is running and "Local USB" is checked
Unplug the USB cable and plug it into a different port [if available.] If there's not one, or that doesn't work, reboot. If it's still a 'no go', unplug the cable,uninstall the desktop and then reinstall it. plug the cable in and into the treo when the install asks you to plug in the treo.
Sometimes the problem is simply a dirty contact. clean the bottom connector with a new toothbrush dipped very lightly in rubbing alcohol.
Lastly, try uninstalling the USB host, then reboot and it should refresh it.
Edited on 2007-08-19 23:24:20 by WikiEgadgetguy
No differences.
Edited on 2007-08-19 23:23:53 by WikiEgadgetguy
Additions:
Edited on 2007-08-19 23:23:06 by WikiEgadgetguy
Additions:
CategoryUserguide - CategoryTreo600 - CategoryTreo650 - CategoryTreo700p - CategoryTreo680 - CategoryTreo755p
Edited on 2007-08-19 23:08:20 by WikiEgadgetguy
Additions:
Deletions:
1. Have you ever gotten an evil startup message from HotSync.exe after installing some extraneous desktop software conduits? (Some possible culprits for this are ThoughtMgr, HanDBase, and Agendus Desktop.) The message Hotsync delivers, before it crashes is "Ordinal 157 could not be located in UserData.dll."
2. Another more common, but still ambiguous error is “Some handheld records were not copied to your PC. 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 perform a HotSync operation again.” There are 2 potential causes of this less-than-friendly error.
Edited on 2007-01-08 15:16:31 by WikiDmcduck
Additions:
2. Another more common, but still ambiguous error is “Some handheld records were not copied to your PC. 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 perform a HotSync operation again.” There are 2 potential causes of this less-than-friendly error.
Deletions:
~1. Have you ever gotten an evil startup message from HotSync.exe after installing some extraneous desktop software conduits? (Some possible culprits for this are ThoughtMgr, HanDBase, and Agendus Desktop.) The message Hotsync delivers, before it crashes is "Ordinal 157 could not be located in UserData.dll."
Additions:
3. Another more common, but still ambiguous error is "Some handheld records were not copied to your PC."
Deletions:
3. Another more common, but still ambiguous error is “Some handheld records were not copied to your PC.
Edited on 2007-08-19 23:30:07 by WikiEgadgetguy
Additions:
1. The most common problems hotsyncing are connection related. Try one of these solutions:
- Check the connection setting on the Treo. make sure it's set to cradle/cable and that it is set to Connect to: PC - Via: cradle/cable.
- Make sure the hotsync program is running and "Local USB" is checked
- Unplug the USB cable and plug it into a different port [if available.] If there's not one, or that doesn't work, reboot. If it's still a 'no go', unplug the cable, uninstall the desktop, and then reinstall it. Plug the cable in and into the Treo when the install asks you to plug in the treo.
- Sometimes the problem is simply a dirty contact. clean the bottom connector with a new toothbrush dipped very lightly in rubbing alcohol.
- Try uninstalling the USB host, then reboot and it should refresh it.
Deletions:
1. The most common problems hotsyncing are connection related. Try this
Check the connection setting on the Treo. make sure it's set to cradle/cable and that it is set to Connect to: PC - Via: cradle/cable.Make sure the hotsync program is running and "Local USB" is checked
Unplug the USB cable and plug it into a different port [if available.] If there's not one, or that doesn't work, reboot. If it's still a 'no go', unplug the cable,uninstall the desktop and then reinstall it. plug the cable in and into the treo when the install asks you to plug in the treo.
Sometimes the problem is simply a dirty contact. clean the bottom connector with a new toothbrush dipped very lightly in rubbing alcohol.
Lastly, try uninstalling the USB host, then reboot and it should refresh it.
Edited on 2007-08-19 23:24:20 by WikiEgadgetguy
No differences.
Edited on 2007-08-19 23:23:53 by WikiEgadgetguy
Additions:
Edited on 2007-08-19 23:23:06 by WikiEgadgetguy
Additions:
CategoryUserguide - CategoryTreo600 - CategoryTreo650 - CategoryTreo700p - CategoryTreo680 - CategoryTreo755p
Edited on 2007-08-19 23:08:20 by WikiEgadgetguy
Additions:
1. The most common problems hotsyncing are connection related. Try this
Check the connection setting on the Treo. make sure it's set to cradle/cable and that it is set to Connect to: PC - Via: cradle/cable.
Make sure the hotsync program is running and "Local USB" is checked
Unplug the USB cable and plug it into a different port [if available.] If there's not one, or that doesn't work, reboot. If it's still a 'no go', unplug the cable,uninstall the desktop and then reinstall it. plug the cable in and into the treo when the install asks you to plug in the treo.
Sometimes the problem is simply a dirty contact. clean the bottom connector with a new toothbrush dipped very lightly in rubbing alcohol.
Lastly, try uninstalling the USB host, then reboot and it should refresh it.
Make sure the hotsync program is running and "Local USB" is checked
Unplug the USB cable and plug it into a different port [if available.] If there's not one, or that doesn't work, reboot. If it's still a 'no go', unplug the cable,uninstall the desktop and then reinstall it. plug the cable in and into the treo when the install asks you to plug in the treo.
Sometimes the problem is simply a dirty contact. clean the bottom connector with a new toothbrush dipped very lightly in rubbing alcohol.
Lastly, try uninstalling the USB host, then reboot and it should refresh it.
2. Have you ever gotten an evil startup message from HotSync.exe after installing some extraneous desktop software conduits?
(Some possible culprits for this are ThoughtMgr, HanDBase, and Agendus Desktop.) The message Hotsync delivers, before it crashes is "Ordinal 157 could not be located in UserData.dll."3. Another more common, but still ambiguous error is “Some handheld records were not copied to your PC.
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 perform a HotSync operation again.” There are 2 potential causes of this less-than-friendly error.Deletions:
1. Have you ever gotten an evil startup message from HotSync.exe after installing some extraneous desktop software conduits? (Some possible culprits for this are ThoughtMgr, HanDBase, and Agendus Desktop.) The message Hotsync delivers, before it crashes is "Ordinal 157 could not be located in UserData.dll."
2. Another more common, but still ambiguous error is “Some handheld records were not copied to your PC. 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 perform a HotSync operation again.” There are 2 potential causes of this less-than-friendly error.
Edited on 2007-01-08 15:16:31 by WikiDmcduck
Additions:
2. Another more common, but still ambiguous error is “Some handheld records were not copied to your PC. 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 perform a HotSync operation again.” There are 2 potential causes of this less-than-friendly error.
The first is corrupt records. You can run a 3rd-party application called dbScan on your phone, which will detect and repair any corrupted PIM data, then do a second HotSync. A second option is to run the repair utility in the Palm desktop, located under Tools > Options, then select the Tools tab. There is a button there that will detect and repair corrupted PIM data records.
Deletions:
2. Another more common, but still ambiguous error is “Some handheld records were not copied to your PC. 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 perform a HotSync operation again.”
There are 2 potential causes of this less-than-friendly error. The first is corrupt records. You can run a 3rd-party application called dbScan on your phone, which will detect and repair any corrupted PIM data, then do a second HotSync. A second option is to run the repair utility in the Palm desktop, located under Tools > Options, then select the Tools tab. There is a button there that will detect and repair corrupted PIM data records.
Edited on 2007-01-08 15:15:53 by WikiDmcduck
Additions:
~There are 2 potential causes of this less-than-friendly error. The first is corrupt records. You can run a 3rd-party application called dbScan on your phone, which will detect and repair any corrupted PIM data, then do a second HotSync. A second option is to run the repair utility in the Palm desktop, located under Tools > Options, then select the Tools tab. There is a button there that will detect and repair corrupted PIM data records.
Deletions:
~There are 2 potential causes of this rather ambiguous error. The first is corrupt records. You can run a 3rd-party application called dbScan on your phone, which will detect and repair any corrupted PIM data, then do a second HotSync. A second option is to run the repair utility in the Palm desktop, located under Tools > Options, then select the Tools tab.
Edited on 2007-01-08 15:14:17 by WikiDmcduck
Additions:
1. Have you ever gotten an evil startup message from HotSync.exe after installing some extraneous desktop software conduits? (Some possible culprits for this are ThoughtMgr, HanDBase, and Agendus Desktop.) The message Hotsync delivers, before it crashes is "Ordinal 157 could not be located in UserData.dll."
2. Another more common, but still ambiguous error is “Some handheld records were not copied to your PC. 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 perform a HotSync operation again.”Deletions:
2. Another more common, but still ambiguous error is “Some handheld records were not copied to your PC. 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 perform a HotSync operation again.”
There are 2 potential causes of this less-than-friendly error. The first is corrupt records. You can run a 3rd-party application called dbScan on your phone, which will detect and repair any corrupted PIM data, then do a second HotSync. A second option is to run the repair utility in the Palm desktop, located under Tools > Options, then select the Tools tab. There is a button there that will detect and repair corrupted PIM data records.
Edited on 2007-01-08 15:15:53 by WikiDmcduck
Additions:
~There are 2 potential causes of this less-than-friendly error. The first is corrupt records. You can run a 3rd-party application called dbScan on your phone, which will detect and repair any corrupted PIM data, then do a second HotSync. A second option is to run the repair utility in the Palm desktop, located under Tools > Options, then select the Tools tab. There is a button there that will detect and repair corrupted PIM data records.
Deletions:
~There are 2 potential causes of this rather ambiguous error. The first is corrupt records. You can run a 3rd-party application called dbScan on your phone, which will detect and repair any corrupted PIM data, then do a second HotSync. A second option is to run the repair utility in the Palm desktop, located under Tools > Options, then select the Tools tab.
Edited on 2007-01-08 15:14:17 by WikiDmcduck
Additions:
1. Have you ever gotten an evil startup message from HotSync.exe after installing some extraneous desktop software conduits? (Some possible culprits for this are ThoughtMgr, HanDBase, and Agendus Desktop.) The message Hotsync delivers, before it crashes is "Ordinal 157 could not be located in UserData.dll."
Deletions:
~1. Have you ever gotten an evil startup message from HotSync.exe after installing some extraneous desktop software conduits? (Some possible culprits for this are ThoughtMgr, HanDBase, and Agendus Desktop.) The message Hotsync delivers, before it crashes is "Ordinal 157 could not be located in UserData.dll."
2. Another more common, but still ambiguous error is “Some handheld records were not copied to your PC. 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 perform a HotSync operation again.”
Edited on 2007-01-08 15:13:41 by WikiDmcduck
Additions:
~To fix this problem, pull the correct file from a system backup, or else reinstall the Hotsync software (Palm Desktop).
2. Another more common, but still ambiguous error is “Some handheld records were not copied to your PC. 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 perform a HotSync operation again.”
There are 2 potential causes of this rather ambiguous error. The first is corrupt records. You can run a 3rd-party application called dbScan on your phone, which will detect and repair any corrupted PIM data, then do a second HotSync. A second option is to run the repair utility in the Palm desktop, located under Tools > Options, then select the Tools tab.
The second cause is duplicate records. You can use the Palm Add-In to find and remove duplicates. This is located under Tools > AddIns > Delete Duplicates.
Deletions:
~To fix this problem, pull the correct file from a system backup, or else reinstall the Hotsync software to fix this.
Edited on 2006-11-27 21:05:11 by WikiDmcduck
No differences.
Edited on 2006-11-27 21:05:00 by WikiDmcduck
Additions:
~1. Have you ever gotten an evil startup message from HotSync.exe after installing some extraneous desktop software conduits? (Some possible culprits for this are ThoughtMgr, HanDBase, and Agendus Desktop.) The message Hotsync delivers, before it crashes is "Ordinal 157 could not be located in UserData.dll."
Deletions:
~Have you ever gotten an evil startup message from HotSync.exe after installing some extraneous desktop software conduits? (Some possible culprits for this are ThoughtMgr, HanDBase, and Agendus Desktop.) The message Hotsync delivers, before it crashes is "Ordinal 157 could not be located in UserData.dll."
Edited on 2006-11-27 21:04:46 by WikiDmcduck
No differences.
Edited on 2006-11-27 21:04:31 by WikiDmcduck
Additions:
~Have you ever gotten an evil startup message from HotSync.exe after installing some extraneous desktop software conduits? (Some possible culprits for this are ThoughtMgr, HanDBase, and Agendus Desktop.) The message Hotsync delivers, before it crashes is "Ordinal 157 could not be located in UserData.dll."
Deletions:
~1. Have you ever gotten an evil startup message from HotSync.exe after installing some extraneous desktop software conduits? (Some possible culprits for this are ThoughtMgr, HanDBase, and Agendus Desktop.) The message Hotsync delivers, before it crashes is "Ordinal 157 could not be located in UserData.dll."
Oldest known version of this page was edited on 2006-11-27 21:03:58 by WikiDmcduck []
Edited on 2007-01-08 15:13:41 by WikiDmcduck
Additions:
~To fix this problem, pull the correct file from a system backup, or else reinstall the Hotsync software (Palm Desktop).
2. Another more common, but still ambiguous error is “Some handheld records were not copied to your PC. 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 perform a HotSync operation again.”
There are 2 potential causes of this rather ambiguous error. The first is corrupt records. You can run a 3rd-party application called dbScan on your phone, which will detect and repair any corrupted PIM data, then do a second HotSync. A second option is to run the repair utility in the Palm desktop, located under Tools > Options, then select the Tools tab.
The second cause is duplicate records. You can use the Palm Add-In to find and remove duplicates. This is located under Tools > AddIns > Delete Duplicates.
Deletions:
~To fix this problem, pull the correct file from a system backup, or else reinstall the Hotsync software to fix this.
Edited on 2006-11-27 21:05:11 by WikiDmcduck
No differences.
Edited on 2006-11-27 21:05:00 by WikiDmcduck
Additions:
~1. Have you ever gotten an evil startup message from HotSync.exe after installing some extraneous desktop software conduits? (Some possible culprits for this are ThoughtMgr, HanDBase, and Agendus Desktop.) The message Hotsync delivers, before it crashes is "Ordinal 157 could not be located in UserData.dll."
Deletions:
~Have you ever gotten an evil startup message from HotSync.exe after installing some extraneous desktop software conduits? (Some possible culprits for this are ThoughtMgr, HanDBase, and Agendus Desktop.) The message Hotsync delivers, before it crashes is "Ordinal 157 could not be located in UserData.dll."
Edited on 2006-11-27 21:04:46 by WikiDmcduck
No differences.
Edited on 2006-11-27 21:04:31 by WikiDmcduck
Additions:
~Have you ever gotten an evil startup message from HotSync.exe after installing some extraneous desktop software conduits? (Some possible culprits for this are ThoughtMgr, HanDBase, and Agendus Desktop.) The message Hotsync delivers, before it crashes is "Ordinal 157 could not be located in UserData.dll."
Deletions:
~1. Have you ever gotten an evil startup message from HotSync.exe after installing some extraneous desktop software conduits? (Some possible culprits for this are ThoughtMgr, HanDBase, and Agendus Desktop.) The message Hotsync delivers, before it crashes is "Ordinal 157 could not be located in UserData.dll."
Oldest known version of this page was edited on 2006-11-27 21:03:58 by WikiDmcduck []
Page view:
~1. Have you ever gotten an evil startup message from HotSync.exe after installing some extraneous desktop software conduits? (Some possible culprits for this are ThoughtMgr, HanDBase, and Agendus Desktop.) The message Hotsync delivers, before it crashes is "Ordinal 157 could not be located in UserData.dll."It turns out that the good version of c:\Program Files\PalmOne\UserData.dll (file date 6/9/2004 / size 139,264) was replaced by an older version.
To fix this problem, pull the correct file from a system backup, or else reinstall the Hotsync software to fix this.
Page was generated in 0.0724 seconds