Due to the nature of technical support and troubleshooting on various handheld scanner devices, we do recommend remote control support programs, such as the following:

We recommend the "Pocket Controller" SOTI product as it has the basic functions needed and is typical solutions that do much more, but not typically needed for basic remote control and troubleshooting. Contact SOTI to get the best match for your environment.y under $50. There are other SOTI enterprise

Recommended by some customers for limited screen sharing capabilities with little to no cost

The following are general troubleshooting steps related to the Handheld WMS device operations:

  1. Launch a browser on a handheld device and attempt to access the Internet to check connectivity between the handheld and the wireless network. For example, open the browser and enter the URL: (this is the shorthand URL for the Cadacus manual device downloads).  If the connection is good, Internet access is successful.  

Note:  for Windows-based devices, if the HTML script or certificate errors occur, be sure Internet Explorer is set as the default browser on it, as we have found some are not setup accordingly (a requirement).

  1. For Windows-based devices, if there is no connection, dock the handheld and check Internet connectivity. When a handheld device is docked, the device is using the Internet connection belonging to the docked computer, so if the handheld successfully connects to the Internet while docked, then the connectivity issue can be isolated between the handheld and the access point.

  1. Try stopping and re-starting the CadacusWCF service, then attempt a Cadacus transaction on the handheld device.

  1. If not successful, verify the Handheld application runs successfully by excluding the local wireless network variable again. This can be accomplished by installing the "Cadacus Handheld on Windows" application on the SYSPRO application server (recommended).  The Handheld on Windows application is identical to the application that runs on the actual handheld device, so if it runs successfully on the application server, then the issue can then be isolated to the wireless network.

  1. Verify all handheld devices are experiencing the same issue by attempting to connect a separate handheld device which results in the same error codes.

  1. Continue further testing of the Cadacus Windows Communication Foundation (WCF) service for proper connectivity, for example, by following the instructions on our website here.

  1. Verify the Windows firewall port (1991) is open.  If the Handheld WMS works on the application server but is not able to connect to the server from another device or workstation, verify that the application server's firewall port 1991 is open-- Control Panel-->Windows Firewall-->Inbound Rules-->create new rule--> allow CadacusWCF Service port 1991.

  1. If the handheld devices are intermittently losing wireless connections, check and experiment with the handheld device sleep mode settings as some makers have the sleep mode set to take effect when it may not be necessary or even workable.  Some sleep mode settings might take 30 seconds, or more, to wake up the device.  We recommend turning off all the battery-saving, sleep mode settings.

  1. If the scan guns are experiencing lag (slow response) after a scan, run the Handheld on Windows program on the application server. From the menu, select "Services--> Check Webservices" several times (ignore the first response time returned as it is not a representative sample). Then do the same on a handheld device (also ignoring the first response) and compare the response times returned between the Handheld on Windows program on the application server and the handheld device itself. If the lag occurs only on the handheld device, then the lag issue can be isolated to the wireless network or the handheld device for further troubleshooting.

  1. If the Cadacus WCF Service is connecting to devices properly but the results from the application running on the handheld device are not as expected, we recommend temporarily activating the Cadacus WCF Service application event log for troubleshooting and analysis (see step above).