HP Web-Based Enterprise Services 4.5 manual Execute the following command

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.WEBES raises the limit to 3 MB. It is possible that SEA created a zip file larger than 3 MB. We do not anticipate this occurring on any possible EVA configuration.

If either reason seems feasible, then raise the limit by following these steps:

1.In a Command Prompt window, "cd" to the directory containing the script which raises the limit, that can vary depending on where you installed WEBES. For example:

cd C:\Program Files\Hewlett-Packard\svctools\specific\ca\config

2. Execute the following command:

cscript changeFileSizeLimit.js 10

This will change the file size limit to 10 MB, which is the maximum.

3.A log file is created in the current directory named changeISEEFileLimit.log. Open this log file in an editor such as Notepad, to see whether the script is executed successfully or not.

2.3.4.2Error while Entering Product Serial Number and Product Number for EVA Managed Entities

The following error messages will be seen when entering the product serial number and the product number for EVA managed entities. They are harmless and should be ignored.

"RECOVERED FROM ERROR on May 4, 2005 1:36:02 PM PDT (268.162 sec elapsed) Error sending ISEE Notification

Current Thread[Thread-29,5,main] EXCEPTION java.lang.NullPointerException at com.compaq.svctools.desta.services.notification.transport.ISEETransport. sendParcel"

2.3.4.3Microsoft HotFix Corrects Application Event Log Corruption Problem

There is a problem in how Windows 2000 writes to the Application Event Log that can cause corrupted events to be written to the log, in some cases. SEA may not be able to analyze the corrupt events, which may be analyzable EVA events, for example, and thus will not generate the proper problem notifications.

Microsoft has made a patch available through a limited means. For information from Microsoft, refer to:

Rev. 9/8/06

Web-Based Enterprise Services Release Notes 2–19