Cisco Cisco Unified Queue Manager, Servicing And Troubleshooting Manual

Page: 112 / 148

8-48
Cisco Customer Response Solutions Servicing and Troubleshooting Guide, Release 5.0(1)
Chapter 8 Troubleshooting Tips
CRS Historical Reporting Problems
Step 2
Create a DSN to the db_cra database on the CRS server to which the client computer is attempting to
connect. Make sure the client computer and the CRS server have the same Administrator password.
While pointing the ODBC data source to the CRS server, use
<crsServerNameOrIP>\CRSSQL where
crsServerNameOrIP is the named instance. For example, if your CRS server name is CiscoCRSserver1,
in the Server input box, type CiscoCRSserver1\CRSSQL . CRS uses NT authentication, so choose the
Windows NT authentication radio button.
Step 3 If the DSN cannot be created, verify that network connectivity exists between the CRS Historical
Reports client computer and the CRS server.
Step 4
If you are able to connect successfully using the DSN, update the hrcConfig.ini file on the client
computer with the appropriate network library.
Export file name does not appear in Export dialog box
Symptom A default export file name does not appear in the Export dialog box.
Error Message
None.
Possible Cause
If you click the Export Report tool in the Report Viewer on a Cisco CRS Historical
Reports client computer on which the language is set to Simplified Chinese, the Export dialog box
will not contain a default export file name.
Recommended Action
The name of the report is shown on the header of the report in the Report Viewer.
In the Export dialog box, specify a name for the exported report using the report name; for example, you
can name your PDF report
<ReportName>_<startdatetime>_<enddatetime> .pdf.
Cannot point to local applications from the Database Server Configuration page
Symptom With a Historical Reports Database Server installed, the user cannot point to the CRS local
database from the Database Server Configuration page.
Error Message
None.
Possible Cause
Once a Historical Reports Database Server (remote database) is configured from Cisco
CRS, the user cannot point back to CRS.
Recommended Action
None. This is working as designed. To go back to a single-box solution (and lose
the Historical Reports Database Server configuration in CRS), uninstall Cisco CRS and reinstall it (and
accept the dropping of the CRS databases when prompted).