Crs Supervisor Web Page Cannot Be Viewed From Crs Server; Database Table Fields Used By Wallboard Store Data In Milliseconds; Management Pages Display Error Message When Selected - Cisco Unified Contact Center Express Servicing And Troubleshooting Manual

Chapter 8 Troubleshooting Tips

CRS Supervisor web page cannot be viewed from CRS Server

Symptom
Error Message None.
Possible Cause
Recommended Action

Database table fields used by wallboard store data in milliseconds

Symptom
HH:MM:SS.
Error Message None.
Possible Cause
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:
•
•
•
•
•

Management pages display error message when selected

Symptom
error message when selected.
Error Message
Possible Cause
•
•
•
Recommended Action
The Cisco CRS Supervisor web page cannot be viewed from the Cisco CRS Server.
If the Cisco CRS Supervisor is running on a computer with the language set to Simplified
Chinese, you cannot view the Cisco CRS Supervisor web page from the Cisco CRS Server.
Use a client computer to view the Cisco CRS Supervisor web page.
Some database table fields used by a wallboard store data in milliseconds instead of in
The avgTalkDuration, avgWaitDuration, longestTalkDuration, longestWaitDuration, and
oldestContact database table fields in the RtCSQsSummary and the RtICDStatistics database tables
store date in milliseconds.
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.
The Prompt Management, Grammar Management, or Document Management pages show an
com.cisco.file.FileException: Unable to list files; Repository Data Store not initialized
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.
In the case of high availability, the Repository Datastore component is activated, but the Publisher
activation has not yet completed from the Datacontrol Center page of CRS Administration.
To resolve the problem, do one of the following:
Cisco Customer Response Solutions Servicing and Troubleshooting Guide, Release 5.0(1)
CRS Administration Problems
8-21