Table 11–1 Troubleshooting (Continued)
Symptom
ConsoleWorks
ConsoleWorks
takes a long time
to start.
ConsoleWorks
requires an
inordinate
amount of time to
access data.
ConsoleWorks
does not start.
11-4
SMC Installation and User's Guide
Possible Cause
ConsoleWorks has
unused consoles.
A large number of
events has accrued.
DEFAULT.CONFIG
has become too
large.
ConsoleWorks is
using an increasing
amount of physical
memory.
Proxy server is being
used to access local
files.
The SMC system
has hung. (The
pointer does not
move when the
mouse moves, or
windows cannot be
selected.)
ConsoleWorks
services are not
running.
Suggested Solution
Delete consoles that will never be
used (Section 8.4.2).
Acknowledge (Section 8.5.5) or
expunge (Section 8.5.6) events.
Delete the file and copy
8_CONSOLE_DEFAULT.CONFIG
(systems with a terminal server) or
SERIAL_COM1_
DEFAULT.CONFIG (no terminal
server) to DEFAULT.CONFIG.
Expunge events, and export and
import the database (Section 8.5.6)
Change Internet Explorer settings
(Section 11.4).
Reboot the SMC system.
Start ConsoleWorks services
(Section 11.5).