Highlighted
Contributor
Contributor

Problems with the VMware vSphere Client

Jump to solution

Hallo

I have problems with the new VMware vSphere Client.

Before i did install the new client on my system i did have the old VMware inferstructure client 2.5 for managing my esxi.

I was then gonna test esx 4 on anther box, and did then install the vsphere client.

But!

When i try logon my old esxi 3.5 or the new esx 4 i get the following error from the vsphere client:

"Error parsing the server "192.168.2.2" "clients.xml" file.

Login will continue, contact your system administrator.

I then clik Ok and get this message:

The type initializer for 'VirtualInfrastructure.Utils.HttpWebRequestProxy' threw an exception.

I have tried to remove both the old client and the new, and then install the new, but still it dosent work.

I am running Windows 7 64 bit.

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Immortal
Immortal

it won't work on windows 7, period. You need to launch the VIC from a supported OS

View solution in original post

0 Kudos
24 Replies
Highlighted
Immortal
Immortal

it won't work on windows 7, period. You need to launch the VIC from a supported OS

View solution in original post

0 Kudos
Highlighted
Enthusiast
Enthusiast

This thread is pretty much the same error:

http://communities.vmware.com/message/1260290#1260290

I still wonder....

Does this have something to do w/ Win7 Beta w/ IE8 beta (not RC1 yet) not trusting the SSL cert that VC setup. I was unable to even open the VC web site to download the client directly usinjg IE8 beta. No errors no warnings, no messages saying the cert was invalid or non-trusted. I then installed Firefox it showed me the cert was untrusted. I was able to download and export the SSL certificate within Firefox as a .crt file. I then tried to make IE8 beta trust the certificate by importing it, but it still is not working.

Any chance that the OS itself w/ Win7 must trust the certificate to run the vSphere client?

As I recall the client speaks to the VC server via SSL. So maybe if IE can be made to trust it, the client would in fact work.

VMware VCP 3.5 VMware VCP 4.0 VMware VCP 5.0
0 Kudos
Highlighted
Immortal
Immortal

In Windows 7 you can use Windows XP Compatibility Mode.

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
Highlighted
Immortal
Immortal

In Windows 7 you can use Windows XP Compatibility Mode.

Still won't work for the vSphere Client.

0 Kudos
Highlighted
Immortal
Immortal

For Windows XP Compatibility Mode in Windows 7 I mean this:

http://community.winsupersite.com/blogs/paul/archive/2009/04/24/secret-no-more-revealing-virtual-win...

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
Highlighted
Contributor
Contributor

I don't think this has anything to do with windows versions especially since this is an error on the server not the client. (<- Wrong on my part, it's the client unable to read from the server)

If you look at the certificate for the ESXi website you'll probably see something like "localhost.localdomain" for the server name. I'm not sure about vSphere but I know in my .Net apps if I try to attach using https I'll get an error every time if I'm not using the correct name that was used when creating the cert for the server. I also have to have my own internal CA's cert and I don't remember every downloading a CA cert for VMWare.

Oh, I tried putting localhost.localdomain in my hosts file and installing the cert in every single repository but all to no avail since I still don't have the CA cert.

Yep it's the bad cert that's the problem. You'll see an error message about a bad cert when you try to run vSphere in Windows 2003 but you can ignore it there while in Win7 you can't.

So, I guess you could say it's the OS that's the problem but it's really how the OS handles the security that's the problem.

0 Kudos
Highlighted
Contributor
Contributor

Just FYI, but I was successfully running the previous version of the VIC from Windows 7 RC1. I see from that the client is supported on Vista. Obviously they don't yet support Windows 7, but I do wonder what it is that's blocking it from working, since MS claims that Windows 7 isn't very different from Vista from an application compatibility perspective, so that apps that work in Vista should typically work in Windows 7.

0 Kudos
Highlighted
Contributor
Contributor

I tested on winserv 2008, win 7 both failed i reloaded the client box to XP and was able to connect. this was using cleint v4. did anyone fine a work around for successfull connection using msft server8 or windows 7?

0 Kudos
Highlighted
Contributor
Contributor

I found a page, , which gives steps the author says worked for him to get this to work on Windows 7. They didn't work for me, but perhaps you'll have better luck.

0 Kudos
Highlighted
Contributor
Contributor

yeppers didn't work for me either....

0 Kudos
Highlighted
Contributor
Contributor

One thing I noticed on the orig post...

my config file was a little off so maybe yours was as well. check lines 2 and 7 of the config file. yours should read:

<?xml version="1.0" encoding="utf-8"?>

<configuration>

<system.net>

<connectionManagement>

<clear/>

<add address="*" maxconnection="8" />

</connectionManagement>

</system.net>

<appSettings>

<add key = "protocolports" value = "https:443"/>

</appSettings>

<runtime>

<developmentMode developerInstallation="true"/>

</runtime>

</configuration>

mine read like the other guys....

<configuration>

<system.net<[http://system.net/]>>

<connectionManagement>

<clear/>

<add address="*" maxconnection="8" />

</connectionManagement>

</system.net<[http://system.net/]>>

<appSettings>

<add key = "protocolports" value = "https:443"/>

</appSettings>

</configuration>

this seemed to work for them. i'm going to try again when i get home.

thx,

jba

0 Kudos
Highlighted
Contributor
Contributor

okay i got it to work with the info they provided....

my bat file: ( I didn't take the time once it worked to check what the difference is, but i had to type it out--NOT cut and paste even though i was pasting into a txt then transfering into the bat)

@echo off

set devpath=c:\program files\vmware\infrastructure\virtual infrastructure client\launcher\lib+

"c:\program files\vmware\infrastructure\virtual infrastructure client\launcher\vpxclient.exe"

this is the config file:

<?xml version="1.0" encoding="utf-8"?>

<configuration>

<system.net>

<connectionManagement>

<clear/>

<add address="*" maxconnection="8" />

</connectionManagement>

</system.net>

<appSettings>

<add key = "protocolports" value = "https:443"/>

</appSettings>

<runtime>

<developmentMode developerInstallation="true"/>

</runtime>

</configuration>

hope this helps !!! thanks to everyone that provided this data!!!!!

0 Kudos
Highlighted
Contributor
Contributor

This resolve is good for windows7 x86, but that about windows7 x64?

0 Kudos
Highlighted
Contributor
Contributor

I would imagine that it all lies in the scripting. Just making sure that the path is correct for your version.

0 Kudos
Highlighted
Contributor
Contributor

I know this doesn't answer the question but what worked great for me is I have Windows 7 x64 running, and I installed VMWare workstation, setup an VM of XP and just do the things that don't work inside of that. I have my update client running inside of it. This is my way of getting around these issues, plus with dual monitors it's just cool. Smiley Happy

0 Kudos
Highlighted
Contributor
Contributor

Smiley Wink

0 Kudos
Highlighted
Contributor
Contributor

worked on windows 7 64X to confirmed

******************************

Svein E Jensen

IT Avdelningen

ÅRE KOMMUN

Box 201, 830 05 Järpen

0647-16331

****************************** Svein E Jensen IT Avdelningen ÅRE KOMMUN Box 201, 830 05 Järpen 0647-16331 ******************************
0 Kudos
Highlighted
Contributor
Contributor

I was able to get the vSphere Client to work using the instructions from this site

http://www.tinyint.com/index.php/2009/09/04/vsphere-client-on-windows-7/

This involves powershell to allow the program to operate.

I guess there is not enough pressure on VMware to fix this problem? Release to public is later this month and there is still nothing on a fix or updated client to resolve this issue.

Good Luck!

0 Kudos
Highlighted
Contributor
Contributor

Keep in mind that it's been released to software assurance customers for around a month now...

0 Kudos