HP Web-Based Enterprise Services 4.5 manual Error During Reading of Obligation Information

Page 17

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.2 Error During Reading of Obligation Information

The following error message may be seen in the Director log when the WEBES Service Obligation period is close to expiring. They can be ignored. The problem will be corrected in a future WEBES release.

RECOVERED FROM ERROR on May 4, 2005 9:28:15 AM PDT (76952.898 sec. elapsed) <local>:3459688795090195548:com.compaq.svctools.desta.services.web.compo nent.DefaultWebInterfaceServer:4:com.compaq.svctools.desta.messages.serv ices.ProblemReportMessage:Error processing message because java.lang.NullPointerException

Current Thread[Thread-11:com.compaq.svctools.desta.services.web.component.Defaul tWebInterfaceServer,5,main]

1.6.1.3 WEBES Installation Issue on ISEE-OSEM Host

If you are using OSEM to send ISEE notifications, and you are installing WEBES v4.4.4on the same system where the ISEE Client is installed, follow these steps before installing WEBES v4.4.4 to ensure that leftover processes started by previous OSEM calls to WCCProxy do not prevent proper WEBES v4.4.4 installation:

1.Shut down OSEM and the ISEE Client.

2.Remove the existing WEBES version (do not upgrade it).

3.Kill any remaining WCCProxy.exe, WCCAgents.exe, or CAAgents.exe processes.

4.Install WEBES v4.4.4.

1.6.1.4 Intermittent Socket Errors

Occasionally, CLI commands such as "desta stop" or "wsea auto off" that connect to the Director will display errors or cause errors to be written to the Director log file. The errors may include "expecting code" or "socket closed", signifying that the socket connection was disconnected before the disconnect handshaking protocol between the CLI process and the Director or WCCProxy was completed. The error can be ignored, since the required functions have been completed before the disconnect handshaking started. The error will be corrected in a future release. Examples of this error, which can be ignored, are:

RECOVERED FROM ERROR on April 14, 2005 2:45:49 PM GMT+08:00 (6.346 sec elapsed)

Socket has a problem: Expecting code<local>:101331133349757508

EXCEPTION java.io.EOFException: Expecting code

WARNING on August 11, 2005 7:03:41 PM GMT+05:30 (6626.84 sec elapsed)

Rev. 9/8/06

Web-Based Enterprise Services Release Notes 1–9

Page 16 Page 18
Image 17
Page 16 Page 18
Contents Software Version Web-Based Enterprise Services Release NotesIi Web-Based Enterprise Services Release Notes Web-Based Enterprise Services Release Notes Page Contents System Event Analyzer ContentsComputer Crash Analysis Tool Further Information Overall Webes Release Notes Overall Webes Release Notes Summary SummaryHardware Requirements Overall Webes Release Notes Operating System Requirements Operating System RequirementsWindows Test EnvironmentOverall Webes Release Notes Test Environment Overall Webes Release Notes 1.5 New in this Release New in this ReleaseRedHat Linux not Patched OpenVMSIntegrity Servers Overall Webes Release Notes New in this ReleaseMiscellaneous Virtual Library System VLSOverall Webes Release Notes 1.5 New in this Release General Webes Issues Webes Known IssuesInstalling Webes on Unsupported Platforms Overall Webes Release Notes Webes Known IssuesIntermittent Socket Errors Error During Reading of Obligation InformationWebes Installation Issue on ISEE-OSEM Host Workaround Webes Configuration Information Not RestoredWebes Output Log Files Grow Without Bound Workarounds Webes Temporary Files Use Disk SpaceBackward Compatibility Director Process Not Responding Director Process Stopping When Out of MemoryUpgrade Requires Reinitialized Log Service Cockpit Compatibility Errors When the Director or WCCProxy is Restarted Too SoonWebes Uninstall Affects Isee Client WCCProxy Upgrading Versions Older Than Two ReleasesChanging Time Zone Causes Incorrect Report Time Errors From desta siclqsap on CommandsClassNotFoundExceptions in Director Log Windows Webes IssuesInstallation Prompts When File Fails to Delete Webes Installation Appears to HangAddition Webes Configuration is Not Migrated for Windows ItaniumCcat Not Available on Windows Itanium Uninstall of Previous Webes May Hang Installation Internal ErrorWindows Itanium Webes Removal Leaves Files Behind Desta msg -chgport CommandPath Update Required on Terminal Server Installation Director May Require Restart Linux Webes IssuesSegmentation Fault Error Message Set ODS-5 Attributes Before Issuing Webes CLI Commands OpenVMS Webes IssuesCannot Get Local Host Name Jfex ErrorsContinuous CPU Usage After Daylight Savings Time Change New OpenVMS Patch Removal FeatureCannot Get Smtp Notification on OpenVMS Upgrade Requires Same Node as InstallAlternate Boot Start and Stop Methods Run the following commands to stop the Smtp debug logging Overall Webes Release Notes Further Information Further InformationOverall Webes Release Notes 1.7 Further Information System Event Analyzer System Event Analyzer Summary Supported ProductsKZPSC/KZPAC/KZPBA/KZPCM/KZPSA/KZPCC/KSPEA System Event Analyzer Supported ProductsSystem Event Analyzer SEA Known Issues SEA Known IssuesGeneral SEA Issues Fields Contain Unavailable File Not Found Error In Desta Log FileSerial Number Prevents Rules from Working Transferring Files with FTP Duplicate Callouts with both DECevent and Webes InstalledInsert the following code at the beginning of the file SEA Problem Reports Not Received by Osem SEA Command Line Interface IssuesCa Command Changed to wsea Entering CommandsWindows interprets it as With either of the following paths $ wsea n analyze svctoolscommoncommon.ca.examples*.zpd SEA Web Interface IssuesNode Name Change Causes Connection or Notification Failure Enabling Text Entry in Other Logs PaneNull-Pointer Errors High Volume of Events Hangs InterfaceNull-Pointer Errors from Large Log Files Cannot Activate a Running NodeJavaScript Error When Viewing Director Settings JavaScript ErrorsTime-out Issue Multiple Sessions using Mozilla and NetscapeTip Services Fail to StartLinux Run the following commands for all platformsMultiple Java Installs May Affect Web Interface SEA EVA Collections Too Big for Isee to Send to HP Windows SEA IssuesOld SEA Example File Names Migrated But Inaccessible Execute the following command XP Internet Explorer Does Not Have Java Windows Event Log May Not Grow to Configured SizeIncomplete Uninstall of Older Version Webes Directory Tree Missing or Access Denied Test Command Generates ErrorWebes Commands Not Recognized Hewlett-Packard Service Tools Entry on Start Menu is EmptyNewly Added EVA Not Listed in SEA Web Interface Napp Error DescriptionNo Binary Event Log HP-UX SEA IssuesResuming from Standby Loses Network Resources Adding Managed Entities Corrupts Director Linux SEA Issues6.1 C/C++ Runtime Libraries Version 6.1.1 or Later Required OpenVMS SEA Issues Insufficient Privilege or File Protection Violation Slow Response Generating Other Logs List Webes Commands Return Error Activating ImageSystem Event Analyzer Further Information Exclude Node Names from FilespecsCAAgent Processes Created But Not Disappearing System Event Analyzer 2.4 Further Information Page Computer Crash Analysis Tool Computer Crash Analysis Tool Summary Ccat Known IssuesGeneral Ccat Issues CLI Commands Not Recognized Windows Ccat IssuesComputer Crash Analysis Tool Ccat Known Issues Ccat IVP File Not FoundInability To Execute CLI Commands OpenVMS Ccat IssuesComputer Crash Analysis Tool Further Information Computer Crash Analysis Tool 3.4 Further Information
Top Page Image Contents