Index
IN-2
Cisco Customer Response Solutions Servicing and Troubleshooting Guide, Release 5.0(1)
CRS Administration problems
A component manager goes into partial service when
uploading a file 8-23
Authentication web page is not available 8-19
CRS Supervisor web page cannot be viewed from CRS
Server 8-21
Database table fields used by wallboard store data in
milliseconds 8-21
High call rejection rate under heavy load 8-23
Invalid files message displays while uploading a zip
file of prompts 8-22
Management pages display error message when
selected 8-21
Refreshing subflow script does not update parent
scripts 8-20
Unified Communications Manager users display in
random order 8-20
Uploading license file can result in warning
message 8-20
User cannot log in to the CRS web page 8-20
Zip file does not auto unzip on Document Management
page 8-22
CRS Admin Utility problems 8-23
The cluster is not in synchronization 8-24
The CRS Admin Utility exits or does not come up after
login 8-24
The CRS Admin Utility fails due to data
corruption 8-24
The CRS Admin Utility will not run on a none
bootstrap node 8-25
The CRS Admin Utility will not run since the Node
Manager hung 8-25
CRS Database problems 8-25
Cannot activiate DB components on HA node 8-26
Cannot configure Application or System parameters
from their pages in CRS Administration 8-26
CRS Databases are not purged as expected 8-26
E-mail notification of database purging activities is
not sent 8-27
Historical database db_cra is full due to high
availability 8-27
HR client login error 8-26
Syslog or SNMP trap notification of database purging
activities is not sent 8-28
CRS Editor problems
Accept step error during active debug 8-28
Change a string variable to an integer 8-28
Error occurs with Reactive Debugging Tool 8-29
CRS Engine problems
An error message plays when calling a CTI route
point 8-33
Application subsystem in partial service and
application running for an unexpectedly long
time 8-39
Application subsystem is in partial service 8-31
Attempting to start the Cisco CRS Node Manager
service causes an error 1067 8-31
Attempting to start the Cisco CRS Node Manager
service causes an error 1069 8-31
Call drops during transfer over gateway 8-34
Calling party and CRS do not have common
codec 8-38
Changes to applications do not register 8-33
Changing time on CRS machines results in agents
getting logged off 8-32
CRS Engine does not start 8-39
CRS Engine does not start and an RMI port in use error
appears 8-30
CRS Engine is running but calls are not
answered 8-32
CRS Server and Active Directory integration results in
some services being unregistered 8-40
CRS Server runs at 100% capacity 8-35
CRS Server runs out of disk space 8-35
Database subsystem goes into partial service 8-36
H.323 client DTMF digits not detected 8-34
JTAPI subsystem is in partial service 8-37
Prompt exception in CRS Engine log file 8-39
Prompts with incorrect codec being played out 8-38
Redirected call is disconnected 8-34
The Simple Recognition step takes the unsuccessful
branch 8-38
Unable to connect to JTAPI provider 8-37
Voice Browser step throws an exception 8-30