Hello,
any idea why I'm getting this errors:
Error parsing the server "SERVER IP" "clients.xml" file. Login will continue, contact your system administrator.
and after pressing OK buttom I'm getting another error:
The type initializer for "VirtualInfrastructure.Utils.HttpWebRequestProxy" threw an exception
when I try to connect to ESXi 4.0 with vSphere client?
My clients.xml file contents (https://SERVER IP/client/clients.xml):
<ConfigRoot> \\ <clientConnection id="0000"> \\ <authdPort>902</authdPort> \\ <version>4</version> \\ <exactVersion>4.0.0</exactVersion> \\ <patchVersion>1.0.0</patchVersion> \\ <apiVersion>4.0</apiVersion> \\ <downloadUrl>https://*/client/VMware-viclient.exe</downloadUrl> \\ </clientConnection> \\ </ConfigRoot> \\
Thanks
getting the same problem here... grrrrrr
Bug confirmed .. trying on Windows 7 RTM .. still waiting a patch for vSphere client
Try to take[ this dll|http://www.techhead.co.uk/files/system.dll], put it in directory C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib, open VpxClient.exe.config, and add there
<runtime>
<developmentMode developerInstallation="true"/>
</runtime>
Than make a bat file - and write there SET DEVPATH=%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe
StarWind Software R&D
Thanks for reply.
A'll trying it, but after starting .bat Win7 show Error : VpxClient.exe stopped working
Now All is OK, slightly modify .bat file
SET DEVPATH=C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
"C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe"
Thanks.
Very interesting bug. You can also try to connect to your VM throught RDP or web.
StarWind Software R&D
Ok I found an answer, from the this blog
My Modification is to open Computer Properties
Advanced System Settings
Environment Variables
New in System Variables
DEVPATH =C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
Edit the VpxClient.exe.config adding
<runtime>
<developmentMode developerInstallation="true"/>
</runtime>
right before </configuration>
Copy VpxClient.exe.config to C:\Program Files\VMware\Infrastructure\VIUpdate 4.0 and rename it to VIUApp.exe.config
Notes:
Filenames of the config files appear to be case sensitive.
Theoreticly all exe's that VMWARE uses here can utilize the same trick
i have same solution
but unser Windows 7 and this way, the Plugins dont work (i have Windows 7 64 Bit)
no Update Plugin works
no Converter Plugin works
when will the vshere 4.1 Client released?
i phoned 4 weeks ago, and the engeneers said, there will be soon a new Version avaiable..
but when?
english version below.
where is below?
searched in Download section, i dont find anything?
http://downloads.vmware.com/d/info/datacenter_downloads/vmware_vsphere_4/4
dont find any 4.1 vsphere Client
where is Below? your post dont show anything?
Thanks
Lol, this is my out of office reply message.
Since when does vmware allow to post via e-mail??
Sorry guys.
Cheers
I am getting this to when I have installed vCenter onto an server 2008 r2 virtual machine then loaded on the client, it comes up with those errors when trying to run locally.
Also I can't connect to it remotely even from an xp or vista machine.
Dan
there is a workaround, see the post of fernando.I tried it with win 7 and it worked.
Several posting in the forums. A search in the forums or a Google search will turn up the steps.
I have the perfect fix. How about 2 VMware programmers sit in a room and FIX the client. That way it will work for everyone
Mike
Install XML parser 4 SP 2
Re-install the VI Client Check the ^¨host update agent utility¨
It will work.
This work fine for me, i am using win7 ultimate, the win7 enterprise did not work well, so i change my windows from enterprise to ultimate.
http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7
Appears that the June 2010 Windows updates has now broken this for Windows 2003 Server too. Nice.
last nights windows updates also broke it for XP