Kofax Communication Server 9.2.0 - Manual (Page 96)

Environment Guide Version 9.02.00
96 © Copyright Kofax, Inc. All information is subject to change without notice.
4) If the KCS system is still accessible you should check all system error messages (ATE???? Files in
system folder) to locate the cause of the error.
5) In case you cannot access the KCS system start the event viewer of the NT administrative tools and
check the application event log.
6) Try to solve the problem according to the error message description.
7) If you cannot solve the problem yourself report the error message to your KCS engineer.
8.1.6 Replacement of Interfaces
Interfaces may be replaced exclusively by trained Kofax technicians.
Line Servers can be switched off for maintenance and will reboot automatically after power on.
8.2 KCS Performance Counters
Many KCS applications provide special performance counters that can be checked by applications like the
Windows Performance Monitor.
8.2.1 Background
The dynamically created KCS counters are put during runtime to the counter initialization file (if they are not
already there). If the file has changed, Windows API functions will be called that equal the load counter and
unload counter command- line tools (“lodctr”, “unlodctr”), and thus the new counter names are put to the
registry. Additionally the memory structure is prepared to receive the counter data and to provide them to
the counter data collecting applications (e.g. Perfmon).
8.2.2 Windows Server 64-Bit Version
If you use Performance Counters on 64-bit versions of Windows Server, you will have to start the service
“Performance Counter DLL Host” and set it to start automatically.
If this service is not started, you cannot view the performance counters with the x64 version of Perfmon,
and when trying to view them the Windows system will deactivate them also for the x32 version.
8.2.3 Counter Initialization File
The counter initialization file is put to the (hidden) “AppData” section of “All Users”, on an English Windows
2003 system this is:
C:\Documents and Settings\All Users\Application Data\TOPCALL\TcLib\TcLibPerf.ini
As the counters are created dynamically during runtime by the KCS applications, the content of the file
differs for each KCS installation.
Example of the counter initialization file for a TC/LINK-FI installation (including enabled performance
counters for TCSRV – “BOOTP”):
// Automatically created performance counter initialization file
[info]
drivername=TcLib