Most Common Issues with Handheld Contact
Posted by Craig S, Last modified by Craig S on 05 June 2023 04:05 PM

Below are the links to the most common questions/issues with Handheld Contact.

 

 Desktop/Server (console) application:

  1. Error message when syncing: "Communication with sync engine failed! The syncing process has been aborted! HHC Service is not running or doesn’t have the required permissions". Click here for solution.
  2. Message Queuing Service is not installed.  The error message is "Unhandled Exception occurred: Message Queuing is not installed or running on this PC".  Click here for solution.
  3. Logon Error when attempting to sync.  Error is "The user: {ACT NAME} failed to log on to the ACT! database: {DATABASE NAME}".  Click here for solution
  4. Cannot get beyond "ACT! Administrator" screen on set up. Click here for solution
  5. Upgrading the desktop software.  Click here for solution.

 

iPhone/iPad:

  1. Getting caller iD on device by exporting Contacts. Click here for solution.
  2. Importing Contacts into Handheld Contact. Click her for solution.
  3. Handheld Contact on the iPhone/iPad unexpectedly closes.  Click here for solution
  4. Close Handheld Contact and restart it properly.  Click here for solutuon.
  5. The Contacts, Task List and Calendar icons are not available on the device.  Click here for solution.
  6. Syncing with both iPhone and iPad.  Click here for solution.
  7. Upgrading the device software.  Click here for solution.

 

Android:

  1. Getting caller iD on device by exporting Contacts.  Click here for solution.
  2. Importing Contacts into Handheld Contact. Click her for solution.
  3. Notifications and alarms working on device.  Click here for solution.
  4. Error message when syncing states "Unable to resolve host “sync.wires-end.net”: No address associated with hostname".  Click here for solution.
  5. Error message on device states "Syncing finished with error: java.io.IOException: Received authentication challenge is null".  Click here for solution.
  6. Upgrading the device software.  Click here for solution.