Filter
Top Products
Thin Web Server Troubleshooting
Troubleshooting
Symptom
Possible
Problem
Possible
Cause
Action Prevention
1. Thin Web server (TWS)
does not turn ON.
. . – Check if you have the correct power supply.
– Make sure the plug is connected properly to the supply
outlet.
2. Thin Web Server keeps
rebooting.
NOTE: You should hear a
series of beep sounds to
indicate the TWS is scanning.
When it completes the process
you will hear a ring sound
similar to a cell phone ring.
Corrupted
usercfg.bin
– Interrupted
configuration
upload.
– TSSP and TWS
versions
mismatch.
a. Connect a PS2 keyboard to the TWS.
b. At the next reboot, press the u key intermittently.
c. When you hear a ring sound, this will indicate that the
usercfg.bin file of the TWS has been erased.
d. You should then reset the TWS mnually from here.
e. Once it reboots, rerun your TSSP, check all your settings
and download again.
f. Reset the TWS after download.
g. Repeat steps b – f if necessary until symptom is resolved.
NOTE: If sympton persists after repeating this procedure
several times, the TWS may be damaged. Contact ASI for
service.
– Make sure that the version of
the TSSP and TWS firmware
are the same.
– Unload old version of the
TSSP you’re your computer
first, then install the new
version before using it with
the TWS.
– Make sure to allow the
system to complete the
down-load process before
doing any tasks.
3. Corrupted 72E IP address
list after downloading 72E
list at TSSP.
Corrupted
_72Ebin
file.
Interrupted
configuration
upload.
a. Connect a PS2 keyboard to the TWS.
b. At the next reboot, press the e key intermittently.
c. When you hear a ring sound, this will indicate that the
_72Ebin. file of the TWS has been erased.
d. You should then reset the TWS mnually from here.
e. Once it reboots, rerun your TSSP, check all _72E record
settings and download again to the TWS.
f. Reset the TWS after download.
g. Repeat steps b – f if necessary until symptom is resolved.
NOTE: If sympton persists after repeating this procedure
several times, the TWS may be damaged. Contact ASI for
service.
Make sure to allow the system
to complete the down-load
process before doing any tasks.
4. No response from TWS
after power is applied.
Normally you should hear a
beep sound to indicate that
the system is scanning for
ASCO device.
TWS is not
rebooting..
– Hard disk
damaged in
TWS from
mishandling.
– Disk file
corruption from
incomplete file
transfer /
upward.
– Power fluctuation.
– Incorrect supply applied to TWS.
Call ASI for assistance.