Cisco Cisco Customer Response Solution Downloads Troubleshooting Guide
8-24
Cisco Unified Contact Center Express Servicing and Troubleshooting Guide, Release 7.0(1)
Chapter 8 Troubleshooting Tips
Cisco Unified CCX Administration Problems
Cisco Unified CCX Supervisor web page cannot be viewed from Cisco Unified
CCX Server
CCX Server
Symptom
The Cisco Unified CCX Supervisor web page cannot be viewed from the Cisco Unified CCX
Server.
Error Message
None
.
Possible Cause
If the Cisco Unified CCX Supervisor is running on a computer with the language set to
Simplified Chinese, you cannot view the Cisco Unified CCX Supervisor web page from the Cisco
Unified CCX Server.
Unified CCX Server.
Recommended Action
Use a client computer to view the Cisco Unified CCX Supervisor web page.
Database table fields used by wallboard store data in milliseconds
Symptom
Some database table fields used by a wallboard store data in milliseconds instead of in
HH:MM:SS.
Error Message
None
.
Possible Cause
The avgTalkDuration, avgWaitDuration, longestTalkDuration, longestWaitDuration, and
oldestContact database table fields in the RtCSQsSummary and the RtICDStatistics database tables store
date in milliseconds.
date in milliseconds.
If you want to include information described by these fields on your wallboard, use the following fields,
which store the same information but use the HH:MM:SS format:
which store the same information but use the HH:MM:SS format:
•
Instead of avgTalkDuration, use convAvgTalkDuration.
•
Instead of avgWaitDuration, use convAvgWaitDuration.
•
Instead of longestTalkDuration, use convLongestTalkDuration.
•
Instead of longestWaitDuration, use convLongestWaitDuration.
•
Instead of oldestContact, use convOldestContact.
Management pages display error message when selected
Symptom
The Prompt Management, Grammar Management, or Document Management pages show an
error message when selected.
Error Message
com.cisco.file.FileException: Unable to list files; Repository Data Store not initialized
Possible Cause
This error occurs when there is no master selected for the Repository datastore
component. This can happen due to one of the following reasons:
•
Repository datastore component is not activated at all in the cluster.
•
Repository datastore component activated node is not up or SQL Services are not running on this
node.
node.