vSphere Client does not open on any Windows operating systems with the error: parsing the server „“ „clients.xml“ file

 Allgemein, Updates, vCenter Server, VMware, VMware ESX, vSphere  Kommentare deaktiviert für vSphere Client does not open on any Windows operating systems with the error: parsing the server „“ „clients.xml“ file
Jun 292010


When trying to launch the vSphere Client you receive errors similar to:
Error parsing the server „<servername>“ „clients.xml“ file.
The type initializer for VirtualInfrastructure.Utils.HttpWebRequestProxy‘ threw an exception.


You cannot use vSphere Clients prior to the Update 1 release, to access the vCenter Server or ESX hosts because of a Microsoft update that targets the .NET Framework (980773), released on June 9th 2010.
Perform one of these two options to correct the issue:

Download and install vSphere Client 4.0 Update 1 (build 208111) or Update 2 (build 258672) using method a or b below, depending on your environment.

To download and install the vSphere Client for ESX, ESXi (paid version), and vCenter Server:
Go the downloads site.

Note: The vSphere Client .exe is part of the ESX, ESXi, or vCenter Server download binaries.

Click Download next to your ESX, ESXi, or vCenter Server edition.
Log in with your VMware Account credentials.
Click the .exe link next to vSphere Client and Host Update Utility

Note: You do not need to download the entire vSphere suite, only the vSphere Client.

Follow the on-screen instructions to install the updated vSphere Client.

Read full article here >> http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1022611

Via http://kb.vmware.com

Memory usage in vCenter Server 4.0 by Eric Siebert

 Allgemein, vCenter Server, VMware, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Memory usage in vCenter Server 4.0 by Eric Siebert
Jul 132009
Eric Siebert published an very nice article about Memory usage in vCenter Server 4.0:

If you are using vCenter Server and plan on upgrading to vSphere you should be aware that vCenter Server 4.0 uses much more memory than vCenter Server 2.5 does. According to the official documentation for both 2.5 and 4.0, the system requirements are very similar:

  • 2.0 GHz or faster Intel or AMD x86 processor. Processor requirements can be more if your database runs on the same hardware.
  • 2 GB RAM. You might need more RAM if your database runs on the same hardware.

But VMware has a note in the vSphere documentation that states:

vCenter Server includes a service called VMware vCenter Management Webservices. This service requires128MB to 1.5GB of additional memory. The vCenter Management Webservices process allocates the required memory at startup.

This Webservices component is a Windows service called VMware VirtualCenter Management Webservices. It’s a Tomcat Java application server that is a component of the vCenter Server. You will see this service listed in Task Manager as tomcat6.exe as vCenter Server 4.0 uses the newer Tomcat 6 version. In vCenter Server 2.5, this service was listed as tomcat5.exe, vCenter Server 2.5 uses the older Tomcat 5.5 version. The Webservices component is not used just for Web browsers to access the vCenter Server, many other services rely on this component. If you stop this service component, vCenter Server will still work but anything that relies on Webservices will no longer work (i.e. plug-ins, Converter).

Read complete article on http://itknowledgeexchange.techtarget.com/

Reblog this post [with Zemanta]