Cisco Cisco IP Contact Center Release 4.6.2 Troubleshooting Guide
Troubleshooting Guide for Cisco Unified Contact Center Management Portal Release 8.0(1)
7
Portal Application Primary, although errors in reporting show as Report
Server.
Server.
Note The SQL Profiler only shows SQL that has executed. Broken/malformed
SQL might never be executed and therefore might not show up in the
profiler.
profiler.
Logs
AppServer Log
On the Web Application Server, navigate to the location where the
Application Server Component was installed. By default, this is
C:\Program Files\Management Portal\Application Server. Open the
latest log file contained within the Logs folder.
Application Server Component was installed. By default, this is
C:\Program Files\Management Portal\Application Server. Open the
latest log file contained within the Logs folder.
Search for ‘Exception:’ and examine the details.
IIS Log Files
Web log files are found at
C:\\WINDOWS\system32\LogFiles\W3SVC1\ex<YYMMDD>.log.
These contain details of all web server transactions, and refer to standard
HTTP status codes.
C:\\WINDOWS\system32\LogFiles\W3SVC1\ex<YYMMDD>.log.
These contain details of all web server transactions, and refer to standard
HTTP status codes.
A full list of HTTP status codes can be found at
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html. Some routine
codes include:
200 - OK
401 - Failed Authorization
404 - Page Not Found
500 - Internal Server Error
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html. Some routine
codes include:
200 - OK
401 - Failed Authorization
404 - Page Not Found
500 - Internal Server Error
Configuring the Web Log
The logging output level for the Web Log is configured in the file
web.config in the location where the Web Server component was installed.
By default, this is C:\Program Files\Management Portal\Web.
web.config in the location where the Web Server component was installed.
By default, this is C:\Program Files\Management Portal\Web.
<system.diagnostics>
<switches>
<!-- 0 - none, 1 = error, 2 = warning, 3 = info, 4 =
verbose -->
<!-- 0 - none, 1 = error, 2 = warning, 3 = info, 4 =
verbose -->
<add name="LogLevelSwitch" value="2"></add>
</switches>
<assert assertuienabled="false"></assert>
<assert assertuienabled="false"></assert>
</system.diagnostics>
Note Verbose level tracing should not be used in a live system except for very
short periods in extreme situations.
Audit Reporting
Audit trails for individual items and audit reports for an overview of
provisioning are available from the Unified CCMP user interface. More
provisioning are available from the Unified CCMP user interface. More