HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes

4 Known Issues
Known issues and limitations of this release are listed below, organized by VSE product or
functional area. The following categories are used:
Limitations Limitations of the implemented functions and features of this release
Major Issues Known issues that may significantly affect functionality and usability in this
release
Minor Issues Known issues that may be noticeable, but do not have a significant impact
on functionality or usability
General
Limitations
• The Lock is Already Held By ... Message You might repeatedly see a message similar to
either of the following messages:
— Unable to acquire the repository lock necessary to store changes.
The lock is already held by: root(Tue Feb 08 13:11:08 CST 2005).
Please retry your operation.
— Unable to acquire the repository lock necessary to store changes.
The lock is already held by: gWLM Agent on host:
hostname/IP_address (Wed May 24 13:20:32 EDT 2006). Please retry
your operation.
Workaround This situation is normal except when the same lock (user and time) persists
for more than 10 minutes. In such a case, you can clear the lock by stopping and restarting
gwlmcmsd, although you might have to wait up to 1 minute before you can use gWLM. Use
the following commands:
NOTE: Stopping gwlmcmsd disables Virtualization Manager and Capacity Advisor.
# gwlmcmsd --stop
# gwlmcmsd
• The following limitations exist for the online help:
— The Index of the iCAP Manager help volume is empty.
— The logical server management topics in the Virtualization Manager help volume are
not localized. These topics appear in the Japanese help, but the content is English.
— The iCAP Manager help volume is not localized. This volume appears in the Japanese
help, but the content is English.
— The search controls in the Japanese help do not function correctly. Search is available
only in the English help. For Japanese help, consider using the VSE Master Index in
place of search.
Major Issues
• When installing VSE from the Insight Control Management (ICM) onto a Windows CMS,
the VSE installer may detect that HP SIM is not fully up and running. This problem happens
intermittently and causes the following fatal error during the VSE configuration process:
Initial configuration failed. More information can be found in
C:\Program Files\HP\Virtual Server Environment\logs\vseinitconfig.log
Then the VSE Uninstall process is displayed.
General 23