Cisco Cisco Unified Queue Manager, Servicing And Troubleshooting Manual

Page: 83 / 148

8-19
Cisco Customer Response Solutions Servicing and Troubleshooting Guide, Release 5.0(1)
Chapter 8 Troubleshooting Tips
CRS Administration Problems
•
Unified Communications Manager users display in random order, page 8-20
• CRS Supervisor web page cannot be viewed from CRS Server, page 8-21
•
Database table fields used by wallboard store data in milliseconds, page 8-21
• Management pages display error message when selected, page 8-21
•
Zip file does not auto unzip on Document Management page, page 8-22
• Invalid files message displays while uploading a zip file of prompts, page 8-22
•
A Component Manager goes into partial service when uploading a zip file, page 8-23
• High call rejection rate under heavy load, page 8-23
The CRS Administration Authentication web page is not available
Symptom
You cannot browse to the CRS Administration URL and a Page Cannot be Displayed error
appears.
Error Message
None.
Possible Cause The system cannot access the CRS Administration web page. A required service may not
be running or required files may be missing.
Make sure the following services are running:
• Check that the CRSJavaAdmin.exe is running (in Windows Task Manager).
•
IIS Admin service
• World Wide Web Publishing service
Recommended Action If these services are running, verify that files exist in the
install_directory\tomcat_appadmin\webapps\appadmin\ directory, where install_directory is the folder
in which the CRS system is installed. (By default, the CRS system is installed in the c:\Program
Files\wfavvid folder.)
If no files exist in this directory, perform the following steps:
Step 1
Stop the Cisco CRS Node Manager service.
Step 2 Delete the appadmin folder from the tomcat_appadmin\webapps folder in the folder in which you
installed the CRS system. (By default, the CRS system is installed in the c:\Program Files\wfavvid
folder.)
Step 3
Start the Cisco CRS Node Manager service.
Step 4 Wait for a few minutes and try to browse to the URL again.