Seeing this error on my Virtual Center client while tryign to get to the console.. We are running Virtual Center 5.0 Build 455964
Anyone now how to fix it?
I was running the vSphere client from my Windows 7 system.
Downloaded the tools vSphere Client from my bare metal ESXi 5 server.
Uninstalled and then installed the vSphere client and it solved the issue.
+1 for mwpreston.
For those looking for how to do this:
0. Close all instances of the vSphere client.
1. Start task manager on the system you're running the client on - presumably your laptop/PC.
2. Under processes, look for vmware-vmrc.exe.
3. Kill them. Kill them all. Mwahahahaaaaaaaa!!
Same problem here on a 2008 R2 Server with last vSphere Client 5.0.
Appears only after using Veeam Exchange/AD Restore (Version 184.108.40.206 and earlier).
Fixed only after a system reboot ...
Had the same problem running Windows 8 CP, trying to connect to a new vSphere 5.0
Work around for me was to use Workstation 8, not a problem with console view there.
Hope they are able to fix it soon! Thx.
jbickford - Thank you, that worked perfect!
this happend with me only after install the vmware converter tool. (i have Windows 8 Pro)
solution that worked with me :
1- from task manager: close any processes related to vmware console or vmware converter
2- uninstall the vmware converter
3- restart PC
4- download the lates vmware vsphere client and reinstall it.
This also happens with Windows 8 - when connecting to 5.0
Guaranteed fix for Windows 8: upgrade to vSphere 5.1. Fully.
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).
I can confirm that the VGC does work form Windows 8 to ESX 5.0 but its still a Work-Around!
Cannot Open a Console Session in the VMware VI Client on Windows 8
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!
Just download the file from following location and install................
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,