Cisco Systems 5.0(1) Historical Reporting Client window shows nothing in user drop-down menu, Historical Reporting Client stops working; attempt to log in again results in error messages

8-51
Cisco Customer Response Solutions Servicing and Troubleshooting Guide, Release 5.0(1)
Chapter 8 Troubleshooting Tips
CRS Historical Reporting Problems
Step 5 ClickAdvanced.
Step 6 In the Do not use proxy server for addresses beginning with field, enter the IP address of the Cisco
CRS server to which the Historical Reports client system logs in.
Step 7 Click OK as needed to save your changes.
Historical Reporting Client window shows nothing in user drop-down menu
Symptom When selecting Tools > Historical Reporting from the Cisco CRS Administration menu,
nothing appears in the user drop-down menu.
Error Message None.
Possible Cause Privileges have not been assigned to the Cisco Unified Communications Manager user.
Assign privileges to the Cisco Unified Communications Manager user who needs historical reporting
privileges.
Step 1 Log in to the Historical Reporting Client with the user name of the Cisco Unified Communications
Manager user. A dialog box with a message asking if you want to set the privileges for that user in CRS
Administration appears.
Step 2 Click Yes. The Historical Reporting Privileges page appears.
Step 3 Assign historical reporting privileges to the user. The proper logLevel (3) is required.
Note The User Maintenance and Historical Users pages use the same underlying directory API.
Historical Reporting Client stops working; attempt to log in again results in
error messages
Symptom Although no changes were made to the server or network, the CRS Historical Reporting Client
suddenly stops working. When attempting to log in again, the user receives a series of error messages.
Error Message A series of messages appear.
Possible Cause The client authentication request timed out.
Complete the following steps:
Step 1 On the CRS Server, check that your web server and servlet service is running. On the client, check you
browser Internet options for the connection setting.
Step 2 Make sure you are able to connect to the CRS Administration web page from the client machine. Refresh
the page to be sure it is not cached.