5 Troubleshooting

5.9Device Server: Configuration of devices failed

If the Device Server is installed on a server that has multiple NICs or IPs, the configuration of devices may fail.

This is because the Device Server uses the IP returned by Java, which may be problematic if the IP returned to the Device Server is unavailable (because of network layout) from the devices point of view.

A solution is to configure the property deviceserver.serverAddress in the config.ini file. This forces the Device Server to use the given IP when configuring devices. Refer to section 2.3.3.

5.10Device Server: Error when upgrading existing device server installation

The following error might appear when upgrading an existing Device Server installation:

"Error in action StopWindowsService"

The following must be completed before running the installer again:

1.Kill the installer process with the following command: taskkill /F /IM scDeviceServer.exe

2.Stop the SafeCom Device Server Service with the following command: net stop scDeviceServer

3.Start the SafeCom Device Server again with the following command: net start scDeviceServer

4.Re-run the SafeCom Device Server installer.

5.11SafeCom reader does not work

If the SafeCom reader does not work the below settings must be checked and set by a Sharp Technician

Sim55-3 SW 5

Bit 1 2 3 4 5 6 7 8

Data 1 1 1 0 0 0 0 1

D60709-22

60

Page 60
Image 60
Nuance comm D60709-22 manual Device Server Configuration of devices failed, SafeCom reader does not work