Cisco Cisco Unified Contact Center Enterprise 9.0(1) Guia Da Instalação
Tomcat log files are located at: icm\tomcat\logs. Additional Web Administration log files are
located at: icm\tomcat\webapp\uiroot\WEB-INF\logs. There are both error and trace log files.
located at: icm\tomcat\webapp\uiroot\WEB-INF\logs. There are both error and trace log files.
As necessary, to troubleshoot Tomcat issues, turn up logging by modifying the value for the
APIServer.TraceFilter.sysTraceFilter.verbosity property in this file:
icm\tomcat\webapps\uiroot\WEB-INF\properties\common\apiserver\logManager\APIServer.properties.
The default, value is VERBOSITY_NONE (logging is off). To turn logging up, change the
value the LOCAL_DUMP then restart the Tomcat service.
APIServer.TraceFilter.sysTraceFilter.verbosity property in this file:
icm\tomcat\webapps\uiroot\WEB-INF\properties\common\apiserver\logManager\APIServer.properties.
The default, value is VERBOSITY_NONE (logging is off). To turn logging up, change the
value the LOCAL_DUMP then restart the Tomcat service.
Workaround
Condition
Symptom
Check the Windows Services panel and Tomcat log files
for errors.
for errors.
Tomcat service does not start.
Run the Service Account Manager tool from Start >
Programs > IPCC Administration to diagnose and fix
service account issues.
Programs > IPCC Administration to diagnose and fix
service account issues.
Verify icm\bin is specified as the path to the service
executable.
executable.
Tomcat service path is
incorrect.
incorrect.
Tomcat starts up but cannot
load sadlib.dll
load sadlib.dll
Be sure that TLS 1.0 is enabled on the Advanced tab of
the Tools > Internet Options dialog box of Internet
Explorer.
the Tools > Internet Options dialog box of Internet
Explorer.
TLS 1.0 is not enabled or there
could be a service account
issue.
could be a service account
issue.
A page not found message
appears.
appears.
Run the Service Account Manager tool from Start >
Programs > IPCC Administration to diagnose and fix
any service account issues.
Programs > IPCC Administration to diagnose and fix
any service account issues.
Self-correcting; Pages will render more quickly on
subsequent access.
subsequent access.
Usually occurs the first time
Tomcat must render a page.
Tomcat must render a page.
Pages served via Tomcat
render slowly.
render slowly.
Microsoft Internet Information Service (IIS) is used as the front-end to Tomcat. It uses Apache
ISAPI dll to connect to Tomcat icm\tomcat\bin\i386\isapi_redirector2.dll. If you suspect issues
related to IIS, ensure that:
ISAPI dll to connect to Tomcat icm\tomcat\bin\i386\isapi_redirector2.dll. If you suspect issues
related to IIS, ensure that:
•
The IIS Virtual Directory points to the directory: icm\tomcat\bin\i386
•
IIS manages the SSL layer. SSL is enabled by default during Unified SCCE installation with
a self-signed certificate. Both “Require Secure channel (SSL)” and “Require 128-bit
encryption” must be set.
a self-signed certificate. Both “Require Secure channel (SSL)” and “Require 128-bit
encryption” must be set.
•
In IIS 6, Web Services Extensions lists jakarta as Allowed.
IPCC Web Administration Access Errors
This section offers workarounds for issues that can occur accessing the IPCC Web Administration
Tool.
Tool.
Installation and Configuration Guide Cisco Unified System Contact Center Enterprise 7.5(1)
121
Chapter 17: Unified SCCE Troubleshooting
IPCC Web Administration Access Errors