Cisco Cisco Customer Response Solution Downloads Guide De Dépannage

Historical Report(s) in a localized version, such as Spanish, has the report description 

truncated in the Historical Reports client user interface.

None

.

The report description seems to appear incomplete in the description box of the Historical 

Reports client user interface.

Click the description box of the Historical Reports client user interface, and scroll 

to view the complete localized text.

Historical Reports scheduled through the Historical Reports client do not run.

None

.

The problem could be caused by an issue in the Historical Reports client schedule settings 

or in the Historical Reports Scheduler connectivity.

Complete the following steps:

Check whether the schedules are listed in the Historical Reports client. To do this, launch the Historical 
Reports client, and go to Settings > Scheduler. In the Scheduled Reports dialog box verify that the 
"Daily" recurring schedules are listed. 

By default, the "daily" schedule ends after running one occurrence. To keep them running forever, select 
"No end date" in the Schedule Configuration dialog box.

Check the proxy server configuration in the web browser. Open the Internet Explorer browser and go to 
Internet Options > Connections > LAN settings. Ensure that the Use a proxy server check box is 
selected. If so, click Advanced and add the Cisco Unified CCX server to the list of exceptions.

The Cisco Unified CCX Historical reports client computer displays the SQL Command Failed 

dialog box when you try to generate a historical report. This dialog box specifies an error number, n.

This error can occur in a variety of situations.

On the computer on which you received the SQL Command Failed dialog box, open 

the most recent Historical Reports log file. Search for the error number. The cause of the error will 
appear near the error number. You can use this information to resolve the problem.