HP Web-Based Enterprise Services 4.5 manual Enabling Text Entry in Other Logs Pane

Page 48

System Event Analyzer

2.3 SEA Known Issues

2.3.3.1“overwrite file if exists” Option in SEA WUI is not Working while Creating New Binary Error Log

When you click on the "New Binary Error Log Creation" icon in the SEA WUI tool bar, add a new file in the “Add File to Input List” tab, create a new binary with the same name as created in the first attempt, and select the option “overwrite file if exists”, a dialog appears as “Output file exists and the overwrite option was not selected. The original file was not overwritten” is displayed.

Workaround

To avoid this problem, manually delete the existing file before re-creating it, or choose a different file name.

2.3.3.2 Enabling Text Entry in Other Logs Pane

When enabled, the text entry field in the Add Logs screen allows users to add log files by entering the path and filename for an event log located anywhere in the file system. In order to enter a file name into the text entry field, the log file must have a .sys, .evt, .zpd, or .errlog extension.

The text field can only be enabled for users you specify in the CA.WUI.OLText key. It cannot be enabled for all users unless you list each user individually.

The list of usernames assigned to the CA.WUI.OLText key corresponds to the user profile entered by the user at the SEA logon screen. SEA profiles and usernames are not related to the id a user enters to log onto a machine, and they are not authenticated by SEA during the logon process. It is therefore the responsibility of those with knowledge text entry enabled user profiles to protect them from unauthorized use (i.e., not allowing open access to event logs anywhere on the system).

For more information, see Section 7.7.3 in the System Event Analyzer User Guide.

2.3.3.3Node Name Change Causes Connection or Notification

Failure

If the network name of a system changes, the change must be reflected in the web interface. After a node's network name changes, the old network name remains in the web interface and the connection to the node is lost. This occurs even if the name change occurs on the localhost. Thus, for name changes on any node, click on the node's group icon in the navigation tree and delete the old node name. Then add the node again using the new name. In addition, remove the line beginning WCCProxy.owner from the file, {installed

directory}/svctools/specific/wccproxy/config/WCCPROXY.REG so that whenever WEBES is

upgraded or re-installed in the future, it will not attempt to use the old hostname. Instead, it will replace the line with the correct current hostname.

Rev. 9/8/06

Image 48
Contents Web-Based Enterprise Services Release Notes Software VersionIi Web-Based Enterprise Services Release Notes Web-Based Enterprise Services Release Notes Page Contents Contents System Event AnalyzerComputer Crash Analysis Tool Further Information Overall Webes Release Notes Summary Hardware RequirementsOverall Webes Release Notes Summary Operating System Requirements Overall Webes Release Notes Operating System RequirementsTest Environment Overall Webes Release Notes Test EnvironmentWindows New in this Release Overall Webes Release Notes 1.5 New in this ReleaseRedHat Linux not Patched OpenVMSOverall Webes Release Notes New in this Release Integrity ServersMiscellaneous Virtual Library System VLSOverall Webes Release Notes 1.5 New in this Release Webes Known Issues General Webes IssuesInstalling Webes on Unsupported Platforms Overall Webes Release Notes Webes Known IssuesError During Reading of Obligation Information Webes Installation Issue on ISEE-OSEM HostIntermittent Socket Errors Webes Configuration Information Not Restored Webes Output Log Files Grow Without BoundWorkaround Webes Temporary Files Use Disk Space Backward CompatibilityWorkarounds Director Process Stopping When Out of Memory Upgrade Requires Reinitialized LogDirector Process Not Responding Errors When the Director or WCCProxy is Restarted Too Soon Service Cockpit CompatibilityWebes Uninstall Affects Isee Client WCCProxy Upgrading Versions Older Than Two ReleasesErrors From desta siclqsap on Commands Changing Time Zone Causes Incorrect Report TimeWindows Webes Issues ClassNotFoundExceptions in Director LogWebes Installation Appears to Hang Installation Prompts When File Fails to DeleteWebes Configuration is Not Migrated for Windows Itanium AdditionCcat Not Available on Windows Itanium Installation Internal Error Uninstall of Previous Webes May HangDesta msg -chgport Command Path Update Required on Terminal Server InstallationWindows Itanium Webes Removal Leaves Files Behind Linux Webes Issues Segmentation Fault Error MessageDirector May Require Restart OpenVMS Webes Issues Set ODS-5 Attributes Before Issuing Webes CLI CommandsJfex Errors Cannot Get Local Host NameNew OpenVMS Patch Removal Feature Continuous CPU Usage After Daylight Savings Time ChangeUpgrade Requires Same Node as Install Alternate Boot Start and Stop MethodsCannot Get Smtp Notification on OpenVMS Run the following commands to stop the Smtp debug logging Further Information Overall Webes Release Notes Further InformationOverall Webes Release Notes 1.7 Further Information System Event Analyzer Supported Products System Event Analyzer SummarySystem Event Analyzer Supported Products KZPSC/KZPAC/KZPBA/KZPCM/KZPSA/KZPCC/KSPEASEA Known Issues General SEA IssuesSystem Event Analyzer SEA Known Issues File Not Found Error In Desta Log File Serial Number Prevents Rules from WorkingFields Contain Unavailable Duplicate Callouts with both DECevent and Webes Installed Transferring Files with FTPInsert the following code at the beginning of the file SEA Command Line Interface Issues SEA Problem Reports Not Received by OsemCa Command Changed to wsea Entering CommandsWindows interprets it as With either of the following paths SEA Web Interface Issues $ wsea n analyze svctoolscommoncommon.ca.examples*.zpdEnabling Text Entry in Other Logs Pane Node Name Change Causes Connection or Notification FailureHigh Volume of Events Hangs Interface Null-Pointer ErrorsNull-Pointer Errors from Large Log Files Cannot Activate a Running NodeJavaScript Errors JavaScript Error When Viewing Director SettingsTime-out Issue Multiple Sessions using Mozilla and NetscapeServices Fail to Start TipRun the following commands for all platforms LinuxMultiple Java Installs May Affect Web Interface Windows SEA Issues Old SEA Example File Names Migrated But InaccessibleSEA EVA Collections Too Big for Isee to Send to HP Execute the following command Windows Event Log May Not Grow to Configured Size Incomplete Uninstall of Older VersionXP Internet Explorer Does Not Have Java Test Command Generates Error Webes Directory Tree Missing or Access DeniedWebes Commands Not Recognized Hewlett-Packard Service Tools Entry on Start Menu is EmptyNapp Error Description Newly Added EVA Not Listed in SEA Web InterfaceHP-UX SEA Issues Resuming from Standby Loses Network ResourcesNo Binary Event Log Linux SEA Issues 6.1 C/C++ Runtime Libraries Version 6.1.1 or Later RequiredAdding Managed Entities Corrupts Director OpenVMS SEA Issues Insufficient Privilege or File Protection Violation Webes Commands Return Error Activating Image Slow Response Generating Other Logs ListExclude Node Names from Filespecs CAAgent Processes Created But Not DisappearingSystem Event Analyzer Further Information System Event Analyzer 2.4 Further Information Page Computer Crash Analysis Tool Ccat Known Issues General Ccat IssuesComputer Crash Analysis Tool Summary Windows Ccat Issues CLI Commands Not RecognizedComputer Crash Analysis Tool Ccat Known Issues Ccat IVP File Not FoundOpenVMS Ccat Issues Inability To Execute CLI CommandsComputer Crash Analysis Tool Further Information Computer Crash Analysis Tool 3.4 Further Information