Cisco Cisco IP Contact Center Release 4.6.1 Installation Guide
11-21
WebView Installation and Administration Guide for Cisco Enterprise & Hosted Editions, Release 7.0(0)
Chapter 11 Troubleshooting Tips
Reports and Templates
Graphical Reports Do Not Work Correctly
There are two possible reasons for this. The reasons and the solutions are applicable to Job Scheduler as
well as graphical reports.
well as graphical reports.
To view graphical reports and to use the WebView Job Scheduler, you must enable all ActiveX
Controls and plug-ins in the browser's Security Settings.
Controls and plug-ins in the browser's Security Settings.
See
for the procedure to enable ActiveX Controls.
Header Truncated in French Reports
If your WebView is localized for the French language, and if the header of reports is truncated or cut off,
select a smaller text size in the browser (View > Text Size).
select a smaller text size in the browser (View > Text Size).
Historical Reports Do Not Work Correctly
This section presents several issues you might encounter with historical reports.
Historical Reports Fail
The following are reasons this can occur.
Is RAM too low?
Large reports might fail if the memory (RAM) allocated to the Java Virtual Machine is set too low in the
New Atlanta ServletExec. The default setting is sufficient for normal reporting usage. If the setting is
too low, there can be an out-of-memory error in the browser and errors in the ServletExec logs.
New Atlanta ServletExec. The default setting is sufficient for normal reporting usage. If the setting is
too low, there can be an out-of-memory error in the browser and errors in the ServletExec logs.
By default, the minimum setting allocated is 32MB (32768 KB). The maximum is 256MB.
You can verify and change the settings by opening the ServletExec Administration page from the server.
This is located at
This is located at
http://localhost/servlet/admin
.
Is TEMPDB large enough?
If large historical reports do not return data, the
tempdb
database might not be sufficiently large to
handle the demand imposed by the queries.
Tempdb
is a system database that SQL Server uses to store temporary tables and temporary stored
procedures. It is created when SQL Server is installed. By default, it is set to an initial size of 50 MB.
with a maximum of 2 GB, and Autogrow is turned on.
with a maximum of 2 GB, and Autogrow is turned on.
If your contact center operations require that you run monthly and yearly historical reports for many
items, you might consider increasing the initial size of tempdb.
items, you might consider increasing the initial size of tempdb.
Refer to the ICM Administration Guide for Cisco ICM Enterprise Edition for information on using the
ICMDBA tool to change the size of the
ICMDBA tool to change the size of the
tempdb
.