The VMRC console has disconnected.. attempting to reconnect

[jslarouche]

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?

[Virtualinfra]

Please paste a screen shot in here....

[DanWebb85]

I'm getting the same message when you open the console to any VM in the vSphere -client 5.0.

[satya1]

DanWebb85 wrote:

I'm getting the same message when you open the console to any VM in the vSphere -client 5.0.

Hi

have you rebooted ?

Yours,

Satya

[pasquito]

Hello,

When i try to open a console-screen of a VM a will receive the following error : The VMRC console has disconnected...attempting to reconnect. The screen stays black.

ESXi : 5.0.0-469512.x86_64

Client : Vsphere 5 Client version 5.0.0-455964

Virtual Machine : Windows 2003 R2 32 bits

I get the error when I attempt to open (in this case) a Windows 2003 VM from my desktop, which is running Windows 7 64-bit with Vsphere 5 Client version 5.

This error is recent, because until a few days ago was to access these VM normally.

Anyone who knows a solution for this case?

Thanks!

[J3anss0n]

Im seeing the same issue but only with the console tab, I have no issues when using the open console option to get the console in a separate window. Thats been our workaround so far

[ph0bia]

We experienced this issue on Windows XP workstations immediately following the installation of Microsoft Visual Studio.  Neither the Console tab or the Console window would work, both reporting the error that "The VMRC console has disconnected, attempting to reconnect" using the vSphere 5 client.

It seems that the installation of Microsoft Visual Studio overwrites or breaks something related to vSphere Remote Console access.

Solution:   Re-installing the VMware vSphere client on the affected systems resolves the problem.

[ph0bia]

We have actually experienced the problem again since then, where MS Visual Studio was not a factor, in this scenario I powered off the VM and migrated it to a new host, then powered it back on and the problem was resolved.

[SandyB]

has anyone found a fix for this issue?

[Virtualinfra]

Just to summaries the work around given so far are as follows

1. Reinstall the vsphere client on the affected system

2. reboot the VM

3. move the VM from one host to another host and reboot.

4. open console in separate window and see..

But dont see a fix for.. let see if we get some input from any expert here for this..bouncing this up..

[ChipSharpDotCom]

I had this problem after I upgraded my VMWare server to 5.0 from 4.1.  I found that installing the 5.0 vSphere client did not upgrade from the 4.1 client.  I had to uninstall both 4.1 and 5.0 and reinstall just the 5.0. 

Hope this helps somebody.

--Chip

[mwpreston]

Did you reboot the machine running the console....

I had a couple of hung vmrc processes in my task manager, I killed those, restarted the client, everything worked fine again :smileyhappy:

[ala139]

Thanks mwpreston...your solution worked for me.

[rodnikosh]

i had the same issue,

If you have a web cam in the guest computer that runs the cSphere client:

* kill the proces called "fixCamera.exe".

* stop the host server

* close the vSphere client.

* open it again and try again.

Problem solved for me.

[cloudsmith]

I had this exact issue, and interestingly enough while i was loading Visual Studio 2010 on a Win 2k8R2 VM.  So i'm assuming something in the Visual Studio load causes an issue with the vSphere client.

At any rate, the same error happend "VMRC console has disconnected.. attempting to reconnect".  Even when i tried to power off the VM it hung at 95%.  I was about to ssh into my esx host to kill the process for the VM when i saw this post and checked the processes running on my PC.  Thank you for saving me some head ache pain.

I did not have to reinstall or reboot.  I just had rogue vmware_vmrc.exe processes running.  I killed them from the task manager and the issue was resolved.

[RickEveleigh]

Thanks mwpreston, that was the answer for me. Go to Task Manager and kill the vmware-vmrc.exe process that has the most CPU.

[huyhuyt]

After upgrade to vCenter 5 Update 1, got exact this issue. I tried to kill process vmware-vmrc in task manager and no go. Have to uninstall vSphere client and installed again, now it works.

[dmyers33]

For those of us just starting with VMware, it would be really helpfull if you gave more detailed informatiion.

After upgrade to vCenter 5 Update 1, got exact this issue. I tried to  kill process vmware-vmrc in task manager and no go. Have to uninstall  vSphere client and installed again, now it works.

How does one go about doing this?

I am running the vSphere client from my Windows 7 systems --> ESXi5 system.

- Wher is the process running? How to access and kill?

- Do you upgrade the vSphere client on the Windoes 7 system?

Thanks

[titaniumlegs]

+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!!

[afeldvary]

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.

[Chris Wade]

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.

[sasikumarsridha]

it worked for me. Thanks for your solution..

[huguesV]

Thanks mwpreston, that was a quick fix :smileyhappy:

[canadavirt]

Hi guys,

I got that error yesterday and I fixed it.

Even after several reboots...no progress. I removed the VClient from my vCenter Server and put it again. I figured this out when I tried connect into my Host by another vClient and worked fine. So the problem was on my VCenter Server.

VSphere Client Version 5.0.0 Build 455964

VMWare vCenter Server Version 5.0.0

[PeteLong]

This also happens with Windows 8 - when connecting to 5.0

Cannot Open a Console Session in the VMware VI Client on Windows 8

[Vad13]

Found an alternative solution, VMware Guest Console. http://labs.vmware.com/flings/vgc

[RickEveleigh]

Guaranteed fix for Windows 8: upgrade to vSphere 5.1. Fully.

[realdreams]

vSphere 5.1 still has this problem..

[RickEveleigh]

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).

[PeteLong]

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

Pete

[WilliamOutsourc]

Try running the vSphere client as an administrator.

[dmyers33]

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.

[vcocaud]

Same problem here on a 2008 R2 Server with last vSphere Client 5.0.

Appears only after using Veeam Exchange/AD Restore (Version 6.1.0.181 and earlier).

Fixed only after a system reboot ...

[jbickford]

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.

[JustinAG]

jbickford - Thank you, that worked perfect!

[mnayel]

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.

[PeteLong]

Heres a work-around

Cannot Open a Console Session in the VMware VI Client on Windows 8

Pete

[Stu_McHugh]

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!

[jraivonen]

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

4. Reboot

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!

[pcanali]

I solved. Thank you

[lipon007]

(SOLVED)

Just download the file from following location and install................

http://rashed.crabdance.com/soft/VMware-viclient-all-5.1.0-786111.exe

[NouraNasri]

To resolve this problem, just close vSphere client and run it  again from his icon as administrator (right click and "run as administrator" )

good luck :smileywink:

[martincortez]

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.

Spanish//

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,

[emrahsrc]

Hello,

everthing is here bullshit. Go Taskmanager and close all tasks vpxclient.exe and start vmware client

[5c0tty]

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

[ChrisSzell]

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!

[AradITC]

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.

[gkpyeung]

Thanks, your workaround fixed my problem....

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.

O/S : Windows 8 with Bing  ....

[DonAtomo]

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

[JCITNZ]

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

[petermie]

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?

[VmUser555]

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.

[petermie]

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

[Andrei_I]

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.

[Andrei_I]

It seems that reinstalling Vmware vSphere client, is solving this "VMRC console has disconnected.. attempting to reconnect" issue.

[nmedard]

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

[petermie]

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.

[echristian]

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?!)

[benersen]

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.

[VM_1000]

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

[Ktulu789]

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.

[rgrinstead462]

I found this to be the solution for my issue:

1. Identify the datastore and virtual machine file location
2. Remove the machine from inventory
3. Re-add the virtual machine to inventory

[DaneC1963]

I happen to have the VMPlayer on my client as well as the vSphere Client. When I get this error with the VMware client, I noticed that (although the app wasn't running) in taskmanager, I have 3 processes running for vmplayer. I end those processes and the problem with the client goes away.

[JLackman]

After reading some of the suggestions, the EASIEST solution is probably to just kill all of the "vmware-rvmrc.exe" processes you have running, restart the client and it should work.

Works every time I've had to try it.

[hokie21]

Killing "vmware-rvmrc.exe" didn't work for me.

I updated to VMware vSphere Client 5.0 Update 3 (VMware-viclient-all-5.0.0-1300600.exe). This solved the problem for me. I can now successfully access the VM console with ESXi 5.0 and Windows 10.

[khingfiles]

Kill the process VM... in the task manager

then try again

[matt_usa]

Just to add another data point;  I'm having this problem myself now, and so far rebooting my workstation where I'm running the vSphere client seems to resolve the issue, at least temporarily. I've tried killing and restarting local processes and services and so far haven't found the right ones, but rebooting so far has worked. 

[max08]

I have this happening on any computer trying to access a vCenter cluster running 5.0.  Windows7/10/w12, local, remote, VPN so unless the client is fubar'd on everyone of those machines it has to be something else.  Tried killing processes, rebooting even restarted vCenter server service to no avail.  This used to work so no idea why it stopped.

In the end I had to install the latest 5.0.0-1300600 client on every machine to get it working again. 

[NRay]

The resolution to the issue is been provided in the KB: The VMRC Console has Disconnected. Trying to reconnect