Link to home
Start Free TrialLog in
Avatar of pjam
pjamFlag for United States of America

asked on

VMWare Client 3.5 Broken

Windows 7 64-bit Enterprise notebook.  I connect to several varieties of ESXi and so over a period of time have the attached installed on my notebook.  yesterday I tried accessing my first ESXi 5.1 server and of cours it asked me to update my VMWare client, you can see it it the jpeg.
Now I cannot access my ESXi 3.5 servers.  I get the attached errors that do not close out.
I think I had the same issue when I added the ESXi 5.0 client some time ago and I fixed it by uninstalling all clients in reverse order, cleaning the registry of vmware and installing again oldest to newest.  Would that work again?
I just re-read hanccoka's article:
HOW TO: Connect to the VMware vSphere Hypervisor 5.1
(ESXi 5.1) using the vSphere Client.  I did not find anything about causing issues with older clients.
vmware-clients.jpg
jsom-vsphere-error-3-4.jpg
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of pjam

ASKER

hanccocka,
I was afaid you would say that but thanks.  I will give it a try.
do I need to remove vmware from registry also?
The clients will uninstall information from the registry.
Avatar of pjam

ASKER

Thanks,
Just finished up and had a crisis on a ESXi 4.1 where a server was hung.  So will test ESXi 3.5 when finished.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of pjam

ASKER

Thanks once again hanccocka,
have a great day