Information Technology Reference
In-Depth Information
Table24-5 Troubleshooting Suggestions (continued)
Error Message
Possible Reasons
Actions
Syslog Analyzer:
the following error
messages are sent
to the Windows
NT Event Viewer
when using remote
Windows NT
collector:
“Could not start
the Syslog
Collector service
on the
server_name
ERROR 1067: The
process terminated
unexpectedly” and
“SacNTService:
The service cannot
be started without
the properties file
specified, please
specify the
properties file you
want to use.”
Configuration
failure has
occurred.
After the SacNTService is installed on a
remote Windows NT collector, it must be
configured using Control Panel; Services.
Ensure that the Startup Parameters field
contains the location of the
SaenvProperties.ini file (for example, -pr
c:\\temp\\SaenvProperties.ini)
(Remember to use \\ to separate the
directory paths.)
Syslog Analyzer:
new messages not
appearing in
reports after
changing syslog
message file
(defined using:
Admin; Syslog
Analysis; Change
Storage Options).
A new filename
needs to be defined
in configuration
information.
On Windows NT, run the registry editor
Regedit. Then go to:
HKEY_LOCAL_SYSTEM System
CurrentControlSet Services crmlog.
Set Parameters to the name of the file for
logging syslog messages.
On Solaris, modify the /etc/syslog.conf file.
(Refer to the Solaris man pages for more
information.)
Syslog Analyzer:
server runtime
error when
running Tasks
Syslog Analyzer
tasks.
CMLogger is not
running.
Log in to Essential as admin.
1.
Select Admin; System Admin; Start
Processes.
2.
Start the system. If the task still fails,
select Admin; Troubleshooting;
Process Failures to get a list of
Essential back-end processes that have
failed.
3.
Select Admin; Troubleshooting; Self
Test.
4.
Search WWH ::




Custom Search