Kofax Communication Server 9.1 - Manual (Page 96)

Environment Guide Version 3.00.04
96 © Copyright Kofax, Inc. All information is subject to change without notice.
CHANNEL Number of the logical channel that caused the error in HEX-format. If no channel number
appears, the error was generated from a module which is used from all channels.
MODULE Name of software module that caused the error (e.g. TAM, TOS, KK99 …). If “?” is used
as module name, it is not specified
TEXT The complete error description
Error Classes
The 6 different levels are described in the table below:
Level Short
description Severity Description Examples
1 trace Information Describes situation that is caused be
user activities or previous errors. operator node reboot
operator system reboot
auto reboot
DISK-reassign block
shutdown requested
2 warning warning Complete System is available now, but
with reduced security or for restricted
time. Disks deactivated in tandem server.
Status box defective
License will expire within x days
3 line out of
order error Any module detected an error. Any
channel stopped working due to wrong
configuration, insufficient license and line
errors. telex/fax line out of order
UAS: script not loaded
license expired
4 HW/SW error
corrected error Errors that should not occur but could be
corrected (e.g. by reloading an interface) user module timeout
node n error reboot
notification not generated
program crc error
several messages indicating
"inconsistent data repaired"
5 partial stop error An unexpected error that could not be
corrected. Parts of the system are no
longer available node stopped, link error
node n channels stopped (too many
error reboots)
6 system stop error The whole TCOSS process has been
stopped. sync stop
About Data Loss
TCOSS behaves like a database server and it is designed to work transactional. This means that all
confirmed data is guaranteed to be stored permanently.
Unexpected software or hardware errors (non detected RAM errors) are the exceptions. In case of a fault
tolerant system, the following hardware errors can be handled without data loss:
Failure in the disk of either the primary or secondary master.
Fatal hardware error in either the primary or secondary master (e.g. power supply, Power On Self Test
finds a RAM error...).
8.1.5 Supervisor Advises in Case of Errors
In case an error occurs or users tell that there is something wrong with the KCS system the supervisor
should perform the following tasks:
1) Do not switch off the KCS system.
2) Check the LEDs of your KCS TCOSS Server system.
3) In case the red and the green LED of the TCOSS Server are ON make sure that no further send
commands are entered and that the system can execute existing ones (capacity in use goes under
80% again).