Title Page Web-Based Enterprise Services Release Notes This document provides an overview and describes known issues for this release of HP Web-Based Enterprise Services (WEBES) on Windows® 2000, Windows 2003 and Windows XP, HP-UX, Linux, and HP OpenVMS systems. To access the latest revision of this document containing updated information, please visit the WEBES Web site: http://www.hp.com/services/webes Rev. 9/8/06 WEBES 4.5 is not supported on OpenVMS Alpha systems and OpenVMS Integrity Servers.
Copyright Statement September 2006 © 2006 Hewlett-Packard Company Microsoft, Windows, and Windows NT are US registered trademarks of Microsoft Corporation. Intel is a US registered trademark of Intel Corporation. UNIX is a registered trademark of The Open Group. Java is a US trademark of Sun Microsystems, Inc. Confidential computer software. Valid license from Hewlett-Packard required for possession, use or copying. Consistent with FAR 12.211 and 12.
Change Summary Change Summary The following table summarizes the changes to this document: Revision Description 25/08/06–A Initial 4.5 copy Rev.
Contents Title Page i Copyright Statement ii Change Summary iii 1 Overall WEBES Release Notes 1.1 1.2 1.3 1.4 1.5 1.6 1–1 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2 Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 1.6.2.7 WCCProxy Incompatibility Issue on Windows XP WOW-Configuration Machines . 1–19 1.6.2.8 Installation “Internal Error”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–19 1.6.2.9 Uninstall of Previous WEBES May Hang. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–19 1.6.2.10 desta msg -chgport Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–20 1.6.2.
Contents 2.3.3.8 JavaScript Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14 2.3.3.9 JavaScript Error When Viewing Director Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14 2.3.3.10 Time-out Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14 2.3.3.11 Multiple Sessions using Mozilla and Netscape 7. . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Overall WEBES Release Notes This chapter contains information that applies to the entire WEBES suite. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . page 1–2 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . page 1–2 Operating System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . page 1–3 Test Environment . .
Overall WEBES Release Notes 1.1 Summary 1.1 Summary Web-Based Enterprise Services (WEBES) is a suite of system diagnostic tools.
Overall WEBES Release Notes 1.3 Operating System Requirements See the next section "1.3 Operating System Requirements" for the operating systems that WEBES can be installed upon. Although WEBES can be installed on any of these hardware and operating system combinations, SEA only supports event bit-to-text translation and event analysis on a certain set of HP products. See Section “2.2 Supported Products for the list of products that SEA supports. 1.
Overall WEBES Release Notes 1.4 Test Environment • Windows XP Professional 64 bit Itanium Edition Although WEBES is not yet supported on this operating system, the Itanium kit may install and operate correctly but the Pentium kit can not be installed. • Windows Vista, 32-bit Beta Edition (formerly known as “Longhorn”) • Any Editions for the x64 platform See section 1.6.1.1 Installing WEBES on Unsupported Platforms for related error messages if you install WEBES on non-supported platforms.
Overall WEBES Release Notes 1.5 New in this Release • HP PA-RISC 9000/889 MHz CPU 899 MHz RAM 2 GB HP-UX 11.00 Not patched RedHat Linux (not Patched) • • • • • Intel Pentium IV, CPU 2.79 GHz, RAM 512 MB (RHEL AS 4.0) Intel Pentium IV, CPU 2.79 GHz, RAM 512 MB (RHEL ES 4.0) Intel Pentium IV, CPU 2.79 GHz, RAM 512 MB (RH ES/AS 3.0) Intel Pentium IV, CPU 2.79 GHz, RAM 512 MB (RH 7.3) Intel Pentium III, CPU 733 MHz, RAM 128 MB (RH 8.0) OpenVMS • AlphaServer 1200 AlphaServer 2100 AlphaServer 4x00 OpenVMS 7.
Overall WEBES Release Notes 1.5 New in this Release • Enhanced CSR (Customer Self Repair) procedure information and added SML links. • Added a note in the FRU field to indicate if part needs to be RoHs (Reduction of Hazardous Substances). • Enhanced disk drive check condition rules. Based on analysis of field data, the error threshold levels for numerous ASC/ASCQ values have been adjusted to predict drive failures more effectively. • Updated analysis rules for supported server and storage products.
Overall WEBES Release Notes 1.5 New in this Release Note The preliminary implementation of HP ISEE Virtual Library System (VLS) Support is disabled in WEBES 4.5 by default. A message will display if you try to configure support of VLS devices. The Beta program will validate the preliminary implementation prior to official release. After Beta, ISEE VLS support will be available to all VLS customers with products under warranty or an appropriate support contract.
Overall WEBES Release Notes 1.6 WEBES Known Issues WBEM Server Web-Based Enterprise Management is a standard method of communicating management data and operations. WBEM provides an integration point through which management and event sources are accessed. By providing a uniform model, it complements and extends existing management protocols and instrumentation such as Simple Network Management Protocol (SNMP) and Desktop Management Interface (DMI). As of the WEBES 4.
Overall WEBES Release Notes 1.6 WEBES Known Issues If you install WEBES Windows Pentium kit on Windows Itanium or WEBES Windows Itanium kit on Windows Pentium, it will prompt the same error messages as mentioned in section 1.6.1.1 Installing WEBES on Unsupported Platforms above (as applicable). Hence, please ensure that you obtain the right kit before installing WEBES. 1.6.1.
Overall WEBES Release Notes 1.6 WEBES Known Issues Socket close problem: :40790387440747720 EXCEPTION java.net.SocketException: Socket closed EXCEPTION java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method) 1.6.1.5 WEBES Configuration Information Not Restored In some cases, WEBES configuration information such as contact names, email addresses, notification enablements, and managed entity XML data may not be restored on an upgrade to WEBES, either through: 1.
Overall WEBES Release Notes 1.6 WEBES Known Issues Workaround If you run out of disk space, check the WEBES output log files. If the logging level has not been increased from WARNING to INFO or DEBUG, follow these steps: 1. Stop the Director and WCCProxy (see SEA User’s Guide section 2.3, “Processes”). 2. If the reason for the problem is not evident from the log files and you cannot resolve it, zip and send all the files in the specific/webes/logs and specific/wccproxy/logs directories to WEBES support. 3.
Overall WEBES Release Notes 1.6 WEBES Known Issues 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 CLI or web URL (for example, without having WEBES installed on your local system) is okay. To avoid a compatibility issue, make sure that the exact same version of WEBES is installed on all systems that will connect to one another, as within a given site or enterprise.
Overall WEBES Release Notes 1.6 WEBES Known Issues 1.6.1.12 Errors When the Director or WCCProxy is Restarted Too Soon This release note applies to both the desta Director and WCCproxy services. After the command to stop one of these services completes, such as desta stop or net stop desta_service, the operating system sometimes requires a few more seconds to stop all WEBES related processes and release their resources (such as sockets).
Overall WEBES Release Notes 1.6 WEBES Known Issues 1.6.1.16 Changing Time Zone Causes Incorrect Report Time Note When the Director is running, System time zone changes are not reflected in the “Report Time” field of WEBES problem reports. You have to restart the Director again so that System time zone changes are reflected in the “Report Time” field of WEBES problem reports. 1.6.1.
Overall WEBES Release Notes 1.6 WEBES Known Issues notification.Type=SMTP LOG ISEE ACHS QSAP 5. Look for the following lines and replace them with the appropriate information, or add the lines if they do not exist: (case-sensitive) If enabling QSAP/OSEM/CSG/PRS: desta.QSAP=mymachine.company.com {the machine running OSEM or PRS} desta.QSAPport=2069 {the port number OSEM/PRS is listening on, 209 by default} If enabling ACHS/SICL/DSNLink: CA.ACHSProfile=/usr/opt/hp/svctools/specific/desta/config/profile.
Overall WEBES Release Notes 1.6 WEBES Known Issues Workaround Stop the Director (net stop desta_service), delete the file {installed directory}\svctools\specific\desta\config\Configuration.dat, then restart the Director (net start desta_service). 1.6.2.2 WEBES Installation Appears to Hang When installing WEBES, certain pop-up dialog windows that prompt for user information may not appear in front of other existing windows. This may give the appearance that the WEBES installation has hung.
Overall WEBES Release Notes 1.6 WEBES Known Issues Have you performed the above steps and are you ready to continue with the installation now? (Answering No will abort the WEBES setup program) [Yes] [No] After you stop the service and any other applications that have the WEBES files open, and delete the offending WEBES file shown in the popup window, you can answer Yes to the popup window prompt, and the WEBES installation should continue successfully.
Overall WEBES Release Notes 1.6 WEBES Known Issues For more information on the CLI commands, See section ‘Managed Entities (SMA, EVA, WBEM Server and VLS) Commands’ of WEBES User Guide. For more information on the Web-based management interface, See section ‘Managed Entities’ of WEBES User Guide. • Any changes that users have made to the User Settings or the Director Settings in the Web interface may have to be changed again after WEBES has been upgraded or installed.
Overall WEBES Release Notes 1.6 WEBES Known Issues 1.6.2.7 WCCProxy Incompatibility Issue on Windows XP WOW-Configuration Machines On Windows XP systems that have the Netherlands WOW image installed, WEBES is not installed correctly and will not operate properly. This information is valid for the WOW v8 image that contained WEBES v4.4.1. No later WOW image has been tested by the WEBES team. Workaround As a workaround to this problem, perform the following steps to return WEBES to a working state.
Overall WEBES Release Notes 1.6 WEBES Known Issues using CPU time, click on the java.exe process and then click End Process. Killing this process may enable the rest of the uninstallation to continue. 1.6.2.10 desta msg -chgport Command The CLI command desta msg -chgport hangs the Director process. Workaround Enter Ctrl-C to restore the command prompt, then enter net stop desta_service to kill the Director process. Enter net start desta_service to restart the Director. 1.6.2.
Overall WEBES Release Notes 1.6 WEBES Known Issues Workaround • Define system PATH variable with some value (not null) before installing. • Manually add WCCProxy path to PATH after installation. 1.6.2.14 Windows Itanium Installation may interrupt if PATH variable is 256 characters or longer In case of Windows Itatium, if the system PATH variable is 256 characters or longer then during the WCCProxy installation an error dialog box pops up “Failed to get PATH”.
Overall WEBES Release Notes 1.6 WEBES Known Issues You can safely ignore this message. There is no impact to WEBES or WCCProxy installation or operation. 1.6.4 OpenVMS WEBES Issues These issues apply to WEBES on OpenVMS: 1.6.4.1 Set ODS-5 Attributes Before Issuing WEBES CLI Commands The following applies only if your system disk or the disk to which you have installed WEBES is an ODS-5 disk.
Overall WEBES Release Notes 1.6 WEBES Known Issues 1.6.4.2 JFEX Errors The following JFEX errors occur when the correct quota minimums are not set. On a cluster, the correct minimums must be set for all nodes in the cluster. Be sure to apply prerequisite minimums to all applicable nodes when installing WEBES. See the WEBES Installation Guide for details. Example errors: $ desta status The Director is running $ wsea tra md_gc_init: could not allocate heap of size, file USER2$:[JFEX.JFEX_VM.SRC.SYS.
Note This information also appears in the MultiNet v4.4 Installation and Administrator Guide. For more details on configuring MultiNet, see the MultiNet documentation. 1. Start the configuration program with the following command: $ MULTINET CONFIGURE /INTERFACE NET-CONFIG> 2. Enable the MultiNet UCX driver interface with the following command: NET-CONFIG> SET LOAD-UCX-DRIVER TRUE 3. Exit the configuration program with the following command: NET-CONFIG> EXIT 4.
Overall WEBES Release Notes 1.6 WEBES Known Issues Do you want to continue? [NO] YES The messages appear because of a new feature that allows OpenVMS patches to be removed. You only see these messages if you have installed the new OpenVMS PCSI patch that adds the feature (or you are running a newer version of OpenVMS that includes the feature), and you have installed OpenVMS patches that use the feature.
Overall WEBES Release Notes 1.6 WEBES Known Issues To enable verbose information for SMTP notification, you will need to stop and restart both the SMTP service and the DESTA Director. Following are the steps to enable SMTP debug information. 1. Run the following commands: $ $ $ $ $ $ $ define /sys tcpip$smtp_log_level 5 define /sys tcpip$smtp_recv_debug 5 define /sys tcpip$smtp_recv_trace 1 desta msg -log debug desta stop @sys$startup:tcpip$smtp_shutdown @sys$startup:tcpip$smtp_startup 2.
Overall WEBES Release Notes 1.7 Further Information 9. Examine the above DESTA_DIR.LOG file (search for SMTP) and the following SMTP log files: The SYS$SPECIFIC:[TCPIP$SMTP]TCPIP$SMTP_LOGFILE.LOG generally logs activity once a job is placed on a queue for execution. The SYS$SPECIFIC:[TCPIP$SMTP]TCPIP$SMTP_RECV_RUN.LOG generally logs activity of the TCPIP receiver. 10. If the problem is not evident from the log files, send the desta_dir_debug_.
Overall WEBES Release Notes 1.7 Further Information Rev.
2 System Event Analyzer This chapter contains information that applies specifically to System Event Analyzer. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . page 2–2 Supported Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . page 2–2 SEA Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Event Analyzer 2.1 Summary 2.1 Summary System Event Analyzer (SEA) is a fault analysis utility included with the Web-Based Enterprise Services (WEBES) service tools. Each WEBES-based service tool adds functionality to the Director, a process (or set of processes) that executes continuously. SEA provides the Director with the capability to capture and interpret hardware events. The analysis of events can be performed automatically or when requested by an outside process.
System Event Analyzer 2.2 Supported Products • • • • • • HP Integrity Servers rx3600, rx6600, rx7620, rx7640, rx8620, rx8640 (automatic analysis and bit to text) and Integrity Superdome (SD16A, SD32A, SD64A, SD32B, SD64B) on Windows 2003 Server Enterprise Edition and OpenVMS 8.3. • Coming soon in future SEA releases: HP Integrity Servers rx7620 and rx8620, and SuperDome platforms SD16, SD32, and SD64 (Windows Server 2003 Enterprise Edition (manual analysis only, no automatic) and OpenVMS v8.
System Event Analyzer 2.
System Event Analyzer 2.3 SEA Known Issues 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.
System Event Analyzer 2.3 SEA Known Issues Could not find file: /WCCApplet102BeanInfo.class It is safe to ignore this message since it does not impact the performance, stability, or functionality of SEA. 2.3.1.6 Transferring Files with FTP If you move files using FTP, it is important to use the appropriate settings for the transfer. Windows Make sure the FTP transfer mode used for binary error logs is binary rather than ASCII.
System Event Analyzer 2.3 SEA Known Issues Running DECevent and WEBES on the same machine results in duplicate callouts to the CSC when event notification occurs. To resolve this problem, you can choose to only start one of the applications at boot time. OpenVMS To prevent DECevent from starting on an OpenVMS platform, use the following procedure: 1. Edit the startup script, sys$startup:decevent$startup.com. 2.
System Event Analyzer 2.3 SEA Known Issues 2.3.1.9 SEA Problem Reports Not Received by OSEM You may see an error similar to the following in the Director error log (see the section on log files in the WEBES User Guide, Chapter 2): RECOVERED FROM ERROR on January 13, 2004 4:48:05 PM GMT+00:00 (254.912 sec elapsed) IOException : Current Thread[Thread-29: com.compaq.svctools.desta.services.notification.HTTPNotification ,5,main] EXCEPTION java.net.ConnectException: Connection refused at java.net.
System Event Analyzer 2.3 SEA Known Issues Windows When you are entering paths in the CLI on a Windows system you must pay special attention to any space characters. If you specify a path that contains spaces, it must be wrapped in double-quotes. However, the Windows shells do not expand path wildcards wrapped with double-quotes. For example, “C:\Program Files\someDirectory\*.zpd” does not expand to all the *.zpd files in the directory “C:\Program Files\someDirectory.
System Event Analyzer 2.3 SEA Known Issues The second double-quote is considered part of the literal line of characters and the third double-quote is added by Windows. Thus, the two arguments are passed to the program as a single argument with a embedded double-quote character: C:\Program Files\someDirectory” C:\anotherDirectory There are two ways to avoid this problem: • Do not place a trailing backslash character following a double-quoted directory name.
System Event Analyzer 2.3 SEA Known Issues Filenames containing wildcards characters (*) are not expanded and result in command parsing errors. OpenVMS does not expand wildcards before passing arguments to a program, and as a result OpenVMS cannot find any files that match the given argument. For example, the following command does not work and results in the given error: $ wsea n analyze svctools_common:[common.ca.examples]*.
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.
System Event Analyzer 2.3 SEA Known Issues If WEBES is upgraded, or uninstalled (saving configuration data) and later installed, then the recovered WCCPROXY.REG file in {installed directory}/specific/wccproxy/config containing the old hostname can cause WEBES to send no notifications other than to the SEA Web interface. To correct this, after upgrading or installing WEBES, remove the following line from WCCPROXY.REG beginning with: WCCProxy.
System Event Analyzer 2.3 SEA Known Issues number of events (tens of thousands or more). You may be encountering this time-out, if other smaller logs are processed correctly. You can increase this time-out by issuing the following commands: desta dri add “desta.AutoLaunch.Timeout” desta dri set “desta.AutoLaunch.Timeout” nnnn Replace nnnn with the number of milliseconds to set the time-out value. The default is 10 minutes (600000).
System Event Analyzer 2.3 SEA Known Issues 2.3.3.12 Services Fail to Start When the system is heavily loaded, or on very slow machines such as the AlphaServer 1000, the Director may have problems starting its services. If any service fails to start, the Director automatically shuts down and records an error in the Director log (under svctools_home/specific/webes/logs) similar to the following: FATAL ERROR on July 22, 2003 12:39:27 PM MDT (144.002 sec elapsed) The following services failed to start: com.
System Event Analyzer 2.3 SEA Known Issues If you cannot start the Director at all, at any time, because it does not successfully start within the time-out period, then issue the following series of commands to disable the SEA/CCAT services. Start the Director without the commands (which should start within the time-out), change the Director's time-out value, and then re-enable the SEA/CCAT services. Note SEA was formerly CA, and this acronym remains in certain places in the code.
System Event Analyzer 2.3 SEA Known Issues desta msg -chgconf "global" 6 300000 i im desta stop desta exec "com.compaq.svctools.desta.configuration.ChangeEnrollments" -enroll ConfigDefaultsCCAT.txt Ignore the error messages that result from this command. This typically occurs if CCAT is not installed) Change the "-unenroll" parameter to "-enroll" and re-issue the "desta exec" command for SEA (CA) services. Ignore the error messages that result from this command.
System Event Analyzer 2.3 SEA Known Issues WCCProxy. This problem was fixed late in the WEBES v4.4.4 release cycle, so please alert HP Customer Support if you encounter this problem. 2.3.3.15 Old SEA Example File Names Migrated But Inaccessible As of WEBES v4.4.4, a new smaller set of SEA examples is provided, with more descriptive names of previous examples, taking up less disk space on the user's system. If you have added any of the old example file names to your web interface user profile in v4.4.
System Event Analyzer 2.3 SEA Known Issues 1. ISEE was installed or upgraded after WEBES was installed or upgraded. By default, there is a file size limit of 1.5 MB in ISEE. SEA often creates zip files containing EVA collection data that are larger than this. If WEBES is installed or upgraded when ISEE is already installed, then WEBES raises this limit to allow the SEA collections to be sent to HP by ISEE. If ISEE is installed or upgraded after WEBES, however, then the limit remains the default 1.5 MB. 2.
System Event Analyzer 2.3 SEA Known Issues http://support.microsoft.com/default.aspx?scid=kb;en-us;829246 This hotfix should be applied to all HP StorageWorks Management Appliances, especially ones with ISEE or WEBES installed. You can obtain the patch from your HP Customer Support representative. 2.3.4.
System Event Analyzer 2.3 SEA Known Issues 2.3.4.7 Test Command Generates Error 1502 If you run the wsea test command when the Windows Application error log is full, the following error occurs: Windows Error: 1502 Command failed: Could not write the event. To resolve the problem, do one of the following: • (Preferred) Modify the “When maximum logsize is reached” setting in the Windows event viewer utility. Change it from “Do not overwrite events” to one of the “Overwrite events” settings.
System Event Analyzer 2.3 SEA Known Issues not part of WEBES, such as Service Cockpit or SmartScope. See the System Event Analyzer User Guide for information on the permissions required to use WEBES tools. 2.3.4.11 NAPP Error Description NAPP uses the parse file to decode the binary data of the EVA controller event log. The parse file name identifies the specific version and builds for VCS.
System Event Analyzer 2.3 SEA Known Issues 2.3.4.13 Resuming from Standby Loses Network Resources in XP SP2 A Microsoft bug in Windows XP Service Pack 2 may affect WEBES. SYMPTOMS You resume your Microsoft Windows XP-based computer from standby while your network is either disconnected or down. After network connectivity is restored, you lose access to your network resources.
System Event Analyzer 2.3 SEA Known Issues 2.3.6 Linux SEA Issues 2.3.6.1 C/C++ Runtime Libraries Version 6.1.1 or Later Required Your Linux system must have version 6.1.1 or later of the C/C++ runtime libraries installed for SEA to run. Normally this is the case for Red Hat 7.3 or later systems. This dependency will be removed in a future WEBES release. 2.3.6.2 No Binary Event Log Linux has no binary event log to analyze, like the log on Windows or OpenVMS.
System Event Analyzer 2.3 SEA Known Issues # rm -rf /usr/opt/hp/svctools/specific/desta/data/managedentities/*.xml 3. Remove the DESTA.stat file. # rm -rf /usr/opt/hp/svctools/specific/desta/data/DESTA.stat 4. 4. Restart the WEBES Director process. #/usr/sbin/desta start 2.3.7 OpenVMS SEA Issues These issues apply to SEA on OpenVMS: 2.3.7.1 ERRFMT May Create New Version of ERRLOG.SYS During WEBES Processing When the WEBES Director has the ERRLOG.
System Event Analyzer 2.3 SEA Known Issues > at com.compaq.svctools.desta.services.JNIRoot.PrivInterface.SendPckHdr(P rivInterface.java:587) > at com.compaq.svctools.desta.services.JNIRoot.PrivInterface.SendPckAndIn tData(PrivInterface.java:614) > at com.compaq.svctools.ca.services.JNIRoot.EvtInterface.RequestEvtSet(Ev tInterface.java:619) > at com.compaq.svctools.ca.services.eventreaders.connections.EvtProxyFile Connection.retrieveEvent(EvtProxyFileConnection.java:216) > at com.compaq.svctools.ca.services.
System Event Analyzer 2.3 SEA Known Issues -RMS-E-PRV, insufficient privilege or file protection violation $ dir svctools_home:[common.bin] %DIRECT-E-OPENIN, error opening SVCTOOLS_COMMON:[COMMON.BIN]*.*;* as input -RMS-E-PRV, insufficient privilege or file protection violation $ dir sys$common:[hp...] Directory SYS$COMMON:[HP] %DIRECT-E-OPENIN, error opening SYS$COMMON:[HP.NODES]*.*;* as input -RMS-E-PRV, insufficient privilege or file protection violation %DIRECT-E-OPENIN, error opening SYS$COMMON:[HP.
System Event Analyzer 2.4 Further Information If you see this error, add and set the CA.WUI.OLMsgWait key in the Desta Registry to 90 seconds. 1. Add the key if it does not already exist: $ desta dri add “CA.WUI.OLMsgWait” 2. Set the key to 90 seconds: $ desta dri set “CA.WUI.OLMsgWait” 90 2.3.7.5 Exclude Node Names from Filespecs SEA does not accept OpenVMS node names when included as part of a filespec (such as when specifying an input or output file name).
System Event Analyzer 2.4 Further Information Rev.
3 Computer Crash Analysis Tool This chapter contains information that applies specifically to Computer Crash Analysis Tool. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . page 3–2 Supported Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . page 3–2 CCAT Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Computer Crash Analysis Tool 3.1 Summary 3.1 Summary Computer Crash Analysis Tool (CCAT) is a software application that enables Hewlett-Packard Customer Services engineers and system administrators to analyze operating system crashes. CCAT matches information collected about a crash against a set of operating system-specific rules to determine if the footprint of the collected crash data matches any known crash data footprints for which a solution or corrective action has been found.
Computer Crash Analysis Tool 3.3 CCAT Known Issues 3.3.1.1 CCAT IVP File Not Found The following message that appears in the Director log shortly after installation is a known issue and expected. It causes no harmful effects, and the message will be removed in a future release. The directory path and filename will vary by operating system, but it will always end in “_RULES_CCAT-IVP.CMP”. An example is: WARNING on May 27, 2004 6:10:45 AM IST (150.351 sec elapsed) CCATRuleMain decrypt () -> IOException:java.
Computer Crash Analysis Tool 3.3 CCAT Known Issues 3.3.3 OpenVMS CCAT Issues The following known issues affect CCAT on OpenVMS. 3.3.3.1 Insufficient Privilege or File Protection Violation If you are not a member of the SYSTEM group, or your user ID does not have the privileges specified in the WEBES Installation Guide, you will not be able to access or see any directories or files under the WEBES CCAT directory tree pointed to by the SVCTOOLS_HOME logical (SYS$COMMON:[HP] by default).
Computer Crash Analysis Tool 3.4 Further Information 3.4 Further Information See the Computer Crash Analysis Tool User Guide for more details about CCAT. Kits, updates, and documentation for WEBES are available at the following URL: http://www.hp.com/services/webes Rev.
Computer Crash Analysis Tool 3.4 Further Information Rev.
