Table of Contents
Advertisement
Chapter 8
Troubleshooting Tips
The CRS server runs out of disk space
Possible symptoms are:
•
•
•
Error Message SQL error 5048.
Possible Cause
Recommended Action
Step 1
To manually shrink a CRS database log file, open a command window on the CRS server and type the
following commands:
osql -Usa -Ppassword -ddb_cra, where password is the password for the sa log in to the CRS database.
USE database_name, where database_name is db_cra.
GO
DBCC SHRINKFILE (database_name_log.mdf), where database_name is db_cra.
GO
Alternatively, you can shrink the log files by running the batch file runTruncateHistDBLogs.bat,
Step 2
installed under the wfavvid directory. Depending on the arguments, it shrinks the log files of db_cra or
tempdb.
Examples:
•
•
•
•
Additional information can be found about truncating logs in the Managing Historical Reporting
Databases section of the Cisco CRS Administration Guide.
This troubleshooting tip also applies to the CRS Database Problems section and the CRS Historical
Note
Reporting Problems section.
CRS Server runs at 100% capacity or is very slow
Symptom
Error Message None.
One of the following configurations might be causing this problem:
An out of memory error occurs on the CRS server.
Accessing purging or synchronization pages on the Administration UI returns an error.
Running historical reports returns SQL error 5048.
The CRS database log files, the tempdb database, or the tempdb log files have grown
large.
There are two possible actions you can take:
Truncate the log files for db_cra to 10MB:
runTruncatedHistDBLogs "sa" "sa_password" "db_cra_all" 10
Truncate the tempdb transaction log:
runTruncateHistDBLogs "sa" "sa_password" "tempdb"
The CRS server CPU works at or close to 100 percent capacity. DTMF digits are delayed.
Cisco Customer Response Solutions Servicing and Troubleshooting Guide, Release 5.0(1)
CRS Engine Problems
8-35
Advertisement
Table of Contents
Troubleshooting
