-
Title
The V5.6.2 VMWare Performance agent running from a host using a double-byte OS cannot collect dat -
Description
The V5.6.2 VMWare Performance agent cannot collect data from the vCenter but the Legacy VMWare agent can collect data. The VMWare Performance agent is running from an FglAM on a Windows 2008 R2 host with a double-byte language (Japanese OS or Chinese OS for example).
Error messages like the following are reported in the VMWare Performance agent log:
_________________________________________________________
2011-12-21 11:46:35.449 ECHO <VMwarePerformance/5.6.2/VMwarePerformance/hostname-agent> FATAL [Quartz-1069] com.quest.agent.esx.task.RelationsTask - An unexpected error occurred while connecting to the VirtualCenter. Please review your agent configuration to ensure proper connection information has been entered.
2011-12-21 11:46:35.449 ECHO <VMwarePerformance/5.6.2/VMwarePerformance/hostname-agent> ERROR [Quartz-1069] com.quest.agent.esx.task.RelationsTask - Error during execution: ERROR: VI SDK invoke exception:org.dom4j.DocumentException: Error on line 7 of document : parsing error: org.gjt.xpp.XmlPullParserException: end tag name should be localeVersion not about at line 7 and column 800 seen ...</licenseProductVersion></about... (parser state END_TAG) Nested exception: parsing error: org.gjt.xpp.XmlPullParserException: end tag name should be localeVersion not about at line 7 and column 800 seen ...</licenseProductVersion></about... (parser state END_TAG)
_________________________________________________________
-
Cause
Defect ID VM-2990 is encountered when the agent runs from an FglAM on a double-byte OS (Japanese OS or Chinese OS for example).
-
Resolution
WORKAROUND 1
Use the Legacy VMWare agent.
WORKAROUND 2
Deploy the VMWare Performance agent from a FglAM running on a Windows host using the English language.
STATUS
Waiting for fix in a future release of the vFoglight cartridge for VMWare.
-
Defect ID
VM-2990 -
Additional Information
Defect ID VM-2990 was logged for this issue. Please refer to the "Resolved Issues" section of the Product Release Notes for a complete list of Defect IDs addressed in a new release.