Filter
Top Products
Overall WEBES Release Notes
1.6 WEBES Known Issues
Rev. 9/8/06
Web-Based Enterprise Services Release Notes 1–9
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)