Cisco Unified Contact Center Express Servicing And Troubleshooting Manual page 8

Contents
CRS Real-Time Reporting Problems
CRS Historical Reporting Problems
Cisco Customer Response Solutions Servicing and Troubleshooting Guide, Release 5.0(1)
vi
Changing the time on CRS machines results in agents getting logged off
An error message plays when calling a CTI route point
Changes to applications do not register
Call drops during transfer over gateway
H.323 client DTMF digits not detected
Redirected call is disconnected
The CRS server runs out of disk space
CRS Server runs at 100% capacity or is very slow
Database Subsystem goes into partial service
JTAPI subsystem is in partial service
Unable to connect to JTAPI provider
The Simple Recognition step takes the unsuccessful branch
Calling party and CRS do not have common codec
Prompts with incorrect codec being played out
Prompt Exception in CRS Engine log file
CRS Engine does not start
Application subsystem in partial service and application running for an unexpectedly long time
CRS Server and Active Directory integration results in some services being unregistered
Attempting to run a real-time report causes an error
After installing JRE, the user receives a message from real-time reporting saying to install JRE
Exported PDF report does not print in landscape orientation
User login missing in Windows XP after installing HR client
Client and Server security policies do not match
Charts do not appear properly in MS Excel format
Columns of data missing in report in MS Excel format
Records truncated in report in MS Excel format
Agent names overwritten on charts
RTF Report containing charts has tabular report headings
Scheduler icon does not appear on Terminal Services client
Reports do not execute at scheduled times
Search dialog box and Preview tab appear in English on Windows system with locale set to
German
8-45
Dialog box does not appear as expected when report is exported
Error when choosing an option from the Historical Reporting web page
Truncated report description in Historical Reports client
Scheduled Historical Reports do not run
The SQL Command Failed dialog box appears when you try to generate a historical report
Some information appears in English on a German system
8-33
8-34
8-34
8-34
8-35
8-35
8-36
8-37
8-37
8-38
8-38
8-39
8-39
8-40
8-40
8-41
8-43
8-43
8-43
8-44
8-44
8-46
8-32
8-33
8-38
8-42
8-42
8-43
8-44
8-44
8-45
8-45
8-46
8-47
8-39
8-40
8-41
8-46