Windows error reporting, 3 windows error reporting – Kofax Communication Server 9.2.0 User Manual
Page 101
Environment Guide
Version 9.02.00
© Copyright Kofax, Inc. All information is subject to change without notice.
101
14) Event-log
15) Version and date of tclib32.dll in c:\topcall\shared
16) Counter initialization file
17) Trace files - location c:\tcoss\trace; from all KCS
applications and from Perfmon (“TCLIBPERFx.trc”)
18) Registry export from:
HKLM\SYSTEM\CurrentControlSet\Services\TcLib\Performance
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib
HKLM\SOFTWARE\TOPCALL
8.3 Windows Error Reporting
Some KCS link and server components are server applications that function without user interaction. Even
when an application terminates unexpectedly, it must restart without any user interaction. On the other
hand, there should be as much information as possible for a subsequent investigation of the problem.
Therefore, Kofax Communication Server setup modifies the standard Windows error handling configuration
in the following way:
Behavior for abnormal termination of the operating system:
Registry value
Description
Operating system
HKLM\System\CurrentControlSet\Control\
CrashControl\AutoReboot = 1
Automatic reboot
without user
interaction
All
HKLM\System\CurrentControlSet\Control\
CrashControl\CrashDumpEnabled = 1
Write crash dump
All
HKLM\System\CurrentControlSet\Control\
CrashControl\LogEvent = 1
Write event log entry
All
HKLM\System\CurrentControlSet\Control\
CrashControl\Overwrite = 1
Overwrite crash dump
file
All
Behavior for abnormal termination of a process:
Registry value
Description
Operating system
HKLM\Software\Microsoft\Windows\
Windows Error Reporting\DontShowUI =1
Disable visual
notifications
Windows 2008
HKLM\System\CurrentControlSet\Control\
Windows\ErrorMode = 0
Disable visual
notifications
All
HKLM\Software\Microsoft\DrWatson\
VisualNotification = 0
Disable DrWatson
dialog window
All
Optional dump file configuration:
Both types of dump files hold valuable information about fatal application failures. They are mainly
investigated by developers.
Windows 2003:
Setup asks whether DrWatson log files shall be activated. This is done via the operating system command
“drwtsn32.exe –i”
Windows 2008:
Setup asks whether Windows Error Reporting shall be configured to create User Mode dump files.