vSphere 5.1 still has this problem..
vSphere 5.1 is fine -- BUT you must have done the full upgrade including Hosts to 5.1 (I can see 4.1 Hosts fine too).
The problem is fixed now. Just download the latest version of the vSphere client VMware-viclient-all-5.0.0-913577.exe and install it. Reboot and the problem is fixed!
Agreed what is said here. Installing the VMware-viclient-all-5.0.0-913577 version fixed the issue for me also.
Steps to do this is:
1. Close all vShpere clients
2. Kill the "VMWare remote console" -service from Task Manager
3. Uninstall all VMWare clients versions from your PC and VMWare host update software
5. Download the VMware-viclient-all-5.0.0-913577 version from VMWare pages (https://my.vmware.com/web/vmware/details?downloadGroup=VC50U2&productId=229 - scroll all the way down and it is the second last download - need to register)
6. Install the new version of the client
7. Start using the new client
Crusial points of this to work is to uninstall ALL VERSIONS so nothing is remembered by the system. Second thing is to kill the service and remember to reboot before the install.
So no need to update to 5.1 version - though if your license supports it - go for it!
Opening task manager and killing the vmrc32.exe processes works, I had about 10 in my list and once I cleared all of them the console started working again.
Thanks for the help.
I've just had the same error. Only change I made was installing vSphere PowerCLI. I then reinstalled client and problem still existed. (Everything is v5.1)
As a test, I installed client on another server and all worked as expected.
I did eventually solve the issue. I removed a Microsoft Office 2010 DVD from the drive and the problem fixed itself. (Had inserted it earlier in the day ready to install office, but due to the number of errors in the event log, there was an issue with it.
To resolve this problem, just close vSphere client and run it again from his icon as administrator (right click and "run as administrator" )
Hi! Just kill process that said jraivonen VMWare remote console and thats all. I thing this issues is beacuse we have a lot of session opened. Or if you like, you can restart your device (Lap,PC,Console). Gracias.
Solo eliminen los procesos de vmware. En mi caso el error sucedió porque tenia muchas procesos ejecutándose. Los borre y luego ya me dejo entrar. También pensé reiniciar la Lap pero no fue necesario. Saludos,
everthing is here bullshit. Go Taskmanager and close all tasks vpxclient.exe and start vmware client
Just had the problem, so I connected to the ESXi Server and opened the console from there... Went back and now it works via Virtual Center.
Running client Version 5 build 913577
stu_mchugh 's response worked for me. I had tried all other post leading up to his. I'm running Windows 8.1 Pro. I had to install the client in compatibility Mode for XP SP3. After installing the client the issue was no longer present. Thx!
Mostly my conversion to Windows 8 has been pretty painless, the only thing that wont work is the VMware VI client cant open a console session to the VMs on my ESX server.
The VMRC console has disconencted
The VMRC console has disconencted...attempting to reconnect
This happens because the IE10 that comes with Windows 8 does NOT LIKE the requests the VI client is sending to the Internet Explorer plug-in.
Update 08/03/13 - This problem has now been fixed! Download the latest 5.1 version of the VI client. (see screenshot).
Work-Around 1 Use VMware workstation (Note: scroll down for a permanent fix)
Until either Microsoft or VMware change something then we are stuck! however there is a work around. if you have VMware Workstation (download the trial it will keep you ticking over till the problem is fixed!).
1. Launch VMware workstation > File > Connect to Server > Enter your ESX/vCenter server details > Connect.
Note: You may need to accept the certificate warning if you are using self signed certificates.
2. Now you can open a console session to your virtual machines.
Work-Around 2 Use VMware Guest Console
Download and run VMware Guest Console > Connect to to a host or vCenter, and you can access the guest machines consoles from there.
Sorry, the only way to fix this (at time of writing) is to upgrade to vSphere 5.1 AND install the 5.1 version of the vSphere client. (You can't point the 5.1 client at a 5.0 host, it automatically launches the 5.0 version of the VI client).
Note: You will need to update vCenter to 5.1 as well for that to work!
Update to the latest VI client, and the problem will cease.
Before upgrade i had VSphere Client Version 5.0.0 Build 455964 with the same problem.
Fixed only by installing VSphere Client Version 5.0.0 Build 913577.
The problem gone.