Alarms, Logs, and Reports
This section includes troubleshooting topics about alarms, logs, and reports.
You cannot download
Your system is
configured for SSL and you are using a Microsoft Internet Explorer version
earlier than version 9. Internet Explorer before version 9 requires a specific
header forcing it to cache downloaded files. It then deletes or fails to
properly cache the files that you are attempting to save.
Contact the Cisco
TAC and set up a remote support account for the TAC to use to resolve the
problem. Refer to "Setting Up a Remote Support Account" in the
Meetings Server Administration Guide for more information.
Cannot Download Reports Using Microsoft Internet Explorer
You cannot download reports when using Internet Explorer as your browser. You receive errors such as "Internet Explorer cannot download Report from server. Internet Explorer was not able to open this Internet site. The requested site is either unavailable or cannot be found. Please try again later" or "File couldn't be downloaded."
Internet Explorer has the setting "Do not save encrypted pages to disk" enabled.
Change your Internet Explorer security settings: Select and deselect the "Do not save encrypted pages to disk" check box. Then select OK.
A Cisco WebEx Meetings Server
administrator cannot capture logs after a failed update of the system. If you
wish to capture system logs, then check the system status. If the system and
all the virtual machines are up and running, then you can proceed with log
capture. If one or more virtual machines are down, then log capture will fail.
Cisco WebEx Meetings Server is not
in a healthy state and some components are not running. The system must be
healthy and running to generate system logs.
Retry the system update after
reverting snapshots or contact the Cisco TAC if the update problem persists.
Log Capture Size Problems
The log capture size can become too large.
The log capture size can become too large, especially when obtaining logs from the archives. When obtaining logs from an archive, the log capture service gets the logs for an entire day even if you have selected only part of the day. The system was designed this way because unzipping the files can be a time-consuming process and can impact the performance of your system.
Your log capture size can be minimized by selecting only the activities that you are trying to troubleshoot. The log capture size can also be minimized by performing a log capture as soon as you run into any issue, so that the log capture service does not have to go into the archives to obtain the logs.