Troubleshooting Guide

Quality Management Troubleshooting Guide
10 September 2009
Logs and Debugging
Applications and services use logging to report status and problems. Each application
and service creates two files:
Log files (files with the *.log file extension) contain status messages and, if
problems occur, warning and other error messages. All messages in log files
are identified by an error code. See the Quality Management Error Code
Dictionary for more information on error codes.
Debugging files (files with the *.dbg file extension) are empty when debugging
is not enabled. When debugging is enabled (the default setting), the files
contain diagnostic information that can help resolve issues.
Log and debugging files are located in the …\Cisco\WFO_QM\log folder on the client
or server computer.
The default configuration settings limit each log and debugging file to a maximum of
10 MB and 20 rolling files for QM services and 5 MB and 5 rolling files for
applications. For example, when a service’s log or debug file reaches 10 MB, it is
closed and renamed, and a new file is started.
C++ configuration files (files with the *.cfg extension) produce logs using this
numbering scheme:
<name>0001.log is created and filled.
<name>0002.log is created when the first file is full.
<name>0001.log is cleared and reused when the second file is full.
<name>0002.log is cleared and reused when the first file is full.
And so on.
Java configuration files (files with the *.properties extension) produce logs using this
numbering scheme:
<name>.log is always the file currently being filled.
<name>.log.1 is the most recent filled file.
Debugging logs follow these same numbering schemes, but use the *.dbg file
extension.
Setting the Default Debugger
When Microsoft SQL Server 2005 is installed on the Database Services server,
Microsoft Visual Studio is also installed and configured as the default debugger on
that server. It is recommended that you reset Dr. Watson for Windows as your default
debugger.