user manual
System Event Analyzer
2.3 SEA Known Issues
Rev. 9/8/06
2–18 Web-Based Enterprise Services Release Notes
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.1 or earlier, and 
you migrated to WEBES v4.4.4 or later, those filenames will be retained and migrated in your 
profile, but the files will no longer exist on your system. It is recommended that you manually 
delete all of the old example file names from your user profile. You can add any of the new set 
of examples to your user profile at any time, and manual analysis will work correctly on those 
new files. You can obtain the previous set of examples from an installed WEBES v4.4.1 kit, or 
contact HP Customer Support.
2.3.4 Windows SEA Issues 
Internet Explorer on Windows 2000 includes its own Java VM 1.1.4, but no Java is included in 
IE on Windows XP, Windows 2003 and Microsoft no longer supplies a Java VM. You must 
download and install a Sun JRE instead.
2.3.4.1 SEA EVA Collections Too Big for ISEE to Send to HP
The following applies to HP customer support representatives, or customers who have been 
informed by HP customer support that their EVA collections are not being received at HP.
If EVA collections are not appearing at the HP ISEE server, it could be because the zip file 
created by SEA is larger than the limit specified for ISEE. You can verify this case by 
examining the following file:
C:\Program Files\Hewlett-Packard\ISEE\logs\submitProxiedData.log 
Look for errors similar to the following:
Tue Dec 27 03:20:00 UTC+0100 2005 ERROR [125484]: Incident not 
submitted.. File too large! 
c:\progra~1\hewlet~1\svctools\specific\wccproxy\data\s500.1.zip
This can occur for one of two reasons:










