Truncated Report Description In Historical Reports Client; Scheduled Historical Reports Do Not Run; The Sql Command Failed Dialog Box Appears When You Try To Generate A Historical Report - Cisco Unified Contact Center Express Servicing And Troubleshooting Manual

CRS Historical Reporting Problems

Truncated report description in Historical Reports client

Symptom
truncated in the Historical Reports client user interface.
Error Message None.
Possible Cause
Recommended Action
to view the complete localized text.

Scheduled Historical Reports do not run

Symptom
Error Message None.
Possible Cause
Complete the following steps:
Check whether the schedules are listed in the Historical Reports client. To do this, launch the Historical
Step 1
Reports client, and go to Settings > Scheduler. In the Scheduled Reports dialog box verify that the
"Daily" recurring schedules are listed.
Step 2 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
Step 3
Internet Options > Connections > LAN settings. Check to be sure the Use a proxy server check box
is selected. If so, click Advanced and add the CRS server to the list of exceptions.
The SQL Command Failed dialog box appears when you try to generate a
historical report
Symptom
when you try to generate a historical report. This dialog box specifies an error number, n.
Error Message
Possible Cause
Recommended Action
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.
Cisco Customer Response Solutions Servicing and Troubleshooting Guide, Release 5.0(1)
8-46
Historical Report(s) in a localized version, such as Spanish, has the report description
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
Historical Reports scheduled through the Historical Reports client do not run.
The problem could be caused by an issue in the Historical Reports client schedule settings
or in the Historical Reports Scheduler connectivity.
The CRS Historical reports client computer displays the SQL Command Failed dialog box
Error:
<number>
This error can occur in a variety of situations.
On the computer on which you received the SQL Command Failed dialog box, open
Chapter 8 Troubleshooting Tips