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?
Hello,
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!
Problem
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
Error
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).
Solution
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.
Permanent Fix
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!
Problem Resolved
Update to the latest VI client, and the problem will cease.
Hi all,
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.
KR
Andy
hello all,
i fixed mine by upgrading 5.0.0 to 5.0.0 U3
follow the link below:
https://my.vmware.com/group/vmware/details?downloadGroup=ESXI50U3&productId=229&rPId=4405
cheers
james
i'm having this same issue with 5.5.0.38036, except it isn't all my users and it isn't all the time, nor is it on any specific host (we have 18, all on the same 5.5 version). Using both the web client and the c# client, occasionally their console screen will go black forcing them to close and re-open the window. I have tried looking through logs and haven't been able to find anything useful. Any advice?
I had the same problem after killing VpxClient.exe process on the windows vspehere client. I solved it by closing my Vsphere client and killing vmware-vmrc service. Let me know if it solve your problem.
in my case, just about 90% of the time simply closing the console window and re-opening it works, but randomly and suddenly being disconnected from your console is kind of jarring when you are in the middle of something, hopefully there is a better more permanent solution out there
This issue is also reproducing on Vmware 5.5.0,1398495. Starting this morning, the vSphere Client keeps disconnecting and re-connecting it back only solves this partially.
In addition to this, when I try to launch the Virtual Machine Console I have "The VMRC Console has disconnected... attempting to reconnect" notification.
It seems that reinstalling Vmware vSphere client, is solving this "VMRC console has disconnected.. attempting to reconnect" issue.
Hi,
I just got the the same problem on vcenter 5.1.
I did some research and followed the guidelines of someone who got the same problem.
Below are the steps:
1. Start Task Manager in the Local Windows Account(where vsphere client has been installed)
2. In the "Processes Tab", search for the "vmware-vmrc.exe".
3. kill this process
4. Log out of vphere client and log in again.
This fixed the problem
hope this can help you
While that is a valid workaround, I would rather have a solution to the root cause as to avoid this issue altogether since it is quite disrupting when in the middle of working on a task. It appears to be a fairly common problem that spans multiple versions, so I find it hard to believe that VMware is not aware of the issue. I am actually surprised that they have not weighed in on this issue at all one way or another yet.
Hi all,
today I received the same error,
only my Win7 workstation seems to be affected, we use a test environment with ESXi 5.5.
when I try to open a console from one of our W2K8 servers, it still works, so I think a reboot of the VM is no solution, also rebooting the whole ESXi not.
Looks like a local error on the client computers, the only thing what's sure is, that our Win7 clients are domain computers, with lot's of policies, and updated via local distribution points, where we all know, the "updates" are not really up-to date, since it goes trough eng, scripting, ra, qa, ...
the W2K8 is one of the VM's on the ESXi itself, with direct WSUS updates from MS, so it is up to date.
therefore we need to check local FW rules, and the distributed internal updates, but could not find any updates rolled out today, only some scheduled for Windows security updates, but still not installed.
Reinstall should work, because it kills previously all running vmware processes, but as "nmeard" wrote killing the tasks of "vmware-vmrc.exe" worked fine.
this must not be an error of vmwares applications, we all know windows... (otherwise tell me somebody, why i had running this process 3 times in the background?!)
http://www.empirion.co.uk/vmware/vmware-vsphere-client-direct-download-links/
I found this UK website for the client downloads. I have a 5.0 Host running Win8.1 Pro workstation and I had to use the V5.0 Update 2 (VMware-viclient-all-5.0.0-913577.exe) client. After the reboot worked great.
I solved. Thank you
The machine / Your Machine / Your Mac or Windows machine that you are using with VC Client.
On Your machine, goto task manager. kill vmrc*.*exe . . .
In fact if you are unsure, just close anything related to Virtual Center Client app. goto task manager and ensure all vmware client , vmrc, vm*.* has ended.
Now try again.
My resolution was to kill all vmrc*.*exe . . . Had over 5 processes running.
Killed all and retried.
Thanks
Dom
I tried many of the solutions pointed here but the one that worked was to install the exact client version that goes with the build of the ESXi server.
For instance my old server had 5.0.0 build 623860 which uses client version 623373. This build is 5.0.0 update 1. VMware puts it a little harder publishing versions as x.x.x update # on the site and as x.x.x build ###### on the server screen (or on the client if you are able to connect and go to the Help menu, "About VMware Client". It tells you the current used client version and the current ESXi server version)
On the site you can see the build number on the file that is being downloaded clicking the manual download option (VMware downloads website). ie: When you go to ESXi client 5.0.0 U1 the file is named "VMware-viclient-all-5.0.0-623373.exe"
It might be a different version for you, check it out.
Just install the correct client version and the VMRC console will show up again. I had installed 5.0.0 #noUpdate# Client (ESXi server 5.0.0 Update 1). It connects to the server but doesn't show the console.
Maybe this is why some people fixed this reinstalling... because they had a slightly older version of the client. When reinstalling maybe they didn't notice the difference in version number, so they thought that the same was reinstalled.
I just installed over the other versions without any uninstalling process.
Ps: yes, I know this is for an old ESXi version, I was resurrecting an old backup xD
But the solution should work for later versions too. Hence I'm commenting this solution here.
it worked for me. Thanks for your solution..
I found this to be the solution for my issue: