Filter
Top Products
System Event Analyzer
2.3 SEA Known Issues
Rev. 9/8/06
Web-Based Enterprise Services Release Notes 2–5
2.3.1.1 System Error Log Initialization while Director is
Running Causes Errors
If the system error log is re-initialized while the Director is running, events may be missed or
processed incorrectly. To avoid this problem, either reinitialize the system error log before the
Director is started or stop the Director before modifying the system error log.
2.3.1.2 Backward Compatibility
Connections between systems that are running different versions of WEBES may produce
unpredictable results. This can happen if, for example, you add a remote node to your list of
nodes in the SEA Web interface, and that remote node is running a different version of
WEBES than the node to which your browser is connected.
Running a local copy of WEBES for analysis only on that local system does not present a
problem. Likewise, connecting directly to a remote system via the SEA Web Interface URL
(for example, without having WEBES installed on your local system) is not a problem.
To avoid a compatibility issue, make sure that the exact same version of WEBES is installed
on all systems that connect to one another, as within a given site or enterprise. In any clustered
environment, it is especially important to have the same version installed on every node.
Backward compatibility will be introduced in a future WEBES release.
2.3.1.3 Serial Number Prevents Rules from Working
The system serial number on certain GS80, GS160, and GS320 systems was not set correctly
at the factory, and SEA rules only function if the serial number is set correctly.
See the pre-installation procedures for OpenVMS in the WEBES Installation Guide for details.
2.3.1.4 Fields Contain “Unavailable”
This note applies to DS10/DS10L, DS20/DS20E, ES40, and TS202c products.
When a valid configuration tree event is accessible, information appears in the Part Number,
Serial Number, and FW Rev Level fields. If a valid configuration tree event could not be
accessed, these fields are reported as “Unavailable.”
2.3.1.5 File Not Found Error In DESTA Log File
The following error message may appear in the DESTA log file when using the Microsoft®
JVM in Internet Explorer: