vmrc console has disconnected attempting to reconnect что делать
Как исправить ошибку «The VMRC console has disconnected…attempting to reconnect» в vSphere
Оглавление
The VMRC console has disconnected
Запустив клиент vSphere и перейдя в консоль управления виртуальной машиной мы получили чёрный экран без возможности управления и сообщение:
Ошибка – The VMRC console has disconnected…attempting to reconnect.
С большей долей вероятности у вас запущен процесс vmware-vmrc.exe. Вот он то как раз и не даёт нормально отобразить консольное окно в vSphere. Этот процесс необходимо завершить.
Завершение процесса vmware-vmrc.exe
Комбинацией клавиш Ctrl + Shift + Esc вызываем Диспетчер задач и ищем тот самый процесс (vmware-vmrc.exe). Как вы его найдёте, то кликнув по нему правой кнопкой мыши выбирайте пункт Снять задачу для завершения процесса.
Завершение процесса vmware-vmrc.exe через командную строку CMD
Ещё один способ завершения работы процесса – это выполнение команды из командной строки (CMD):
Выполнять рекомендую от имени администратора.
Заключение
Теперь осталось только перезагрузить сам vSphere Client, после чего сообщение: «The VMRC console has disconnected…attempting to reconnect» больше не появится.
vSphere Client error «The VMRC console has disconnected attempting to reconnect»
has anyone seen the error «The VMRC console has disconnected attempting to reconnect.» when using vSphere 5.0, and know how to correct it?
I have lost connection to my host, then when I re-login with vSphere everything seems fine, except I cannot view the console on any VM. obviously not fine.
MDO Tecnologia is an IT service provider.
Killing those processes didn’t work for me.
I had to install an updated version of vSphere Client, to be more specific, the 5.0.0-913577 build.
The help desk software for IT. Free.
Track users’ IT needs, easily, and with only the features you need.
14 Replies
Check for the vmware-vmrc.exe processes and kill them. Sometimes they don’t close properly, even when the client is closed.
Brand Representative for VMware
Check for the vmware-vmrc.exe processes and kill them. Sometimes they don’t close properly, even when the client is closed.
I would try this first, and if you are still having issues, let us know!
Thanks and nice suggestion Michael!
MDO Tecnologia is an IT service provider.
Killing those processes didn’t work for me.
I had to install an updated version of vSphere Client, to be more specific, the 5.0.0-913577 build.
Thanka Heitor, That worked for me!
Killing those processes didn’t work for me.
I had to install an updated version of vSphere Client, to be more specific, the 5.0.0-913577 build.
I tried everything here and elsewhere to no avail.
Eventually I found that removing Hyper-V role (W2K8 R2) fixed the problem.
ITC is an IT service provider.
Thanks Heitor! Broke my client after installing Visual Studio Pro 2015. Nothing else worked. Uninstalled the client that came from my vCenter server and installed the 5.0.0-913577 build and life is good.
Recently had this issue on Windows 8. Installing the build mentioned fixed it.
stop vmrc.exe using task maager, uninstall existing client, Download latest v5.0 client 5.0.0-1300600.exe, work fine now
Thanks, that fixed it for me too. There was a later update for me to try by this time though, so I’ve installed 5.0.0-1300600 and now it is working again.
Killing those processes didn’t work for me.
I had to install an updated version of vSphere Client, to be more specific, the 5.0.0-913577 build.
BravesBm Where did you download the 5.0.0-1300600?
I am suffering this problem in win10 as well, tried to download the sphere client 5.0 mentioned in this thread but it disallowed me to download. Anyone can post a link for downloading? Big thanks.
Killing the processes worked for me
Hi there!
I thought I’d let you know you’ve just made my day 🙂
I’ve been through hundreds of posts related to the damn «vmrc disconnected» issue for ages and, once in a while, I take sometime to find out if someone found a solution.
Should anyone else need to update, the link for the whole set of versions available is
https://kb.vmware.com/s/article/2089791
Killing those processes didn’t work for me.
I had to install an updated version of vSphere Client, to be more specific, the 5.0.0-913577 build.
The VMRC console has disconnected
I have recently run into the following error on VMware VSphere client: The VMRC console has disconnected…attempting to reconnect. I’m not sure when this error started happening but I wasn’t able to open any virtual machine on any host.
Some of the suggested solutions I’ve found on the net is to shut down the vmware-vmrc.exe in the task manager. Even though I wasn’t able to find the mentioned process in the list I got the following error when trying to start WMware vSphere client.
vmware-vmrc.exe – Application Error | The application was unable to start correctly (0x0000005). Click OK to close the application.
Another suggested solution is to uninstall the vmware converter and restarting your machine. Then download and install the latest vmware vsphere client.
Some of the other suggested solutions are restarting your vsphere client, rebooting machine, running vpshere client in eleveated mode, restarting vmware management service on vsphere server and checking that DNS is correct from vpshere client to vsphere server. None of suggested helped in my case.
On my machine I had installed two vMware vSphere Client versions. Version 5.5 and 6.0.
In my case first I had to uninstall vMware vSphere Client 6.0 and 5.5 after that followed by installation of 5.5 and then 6.0 versions that solved the problem.
Crusial point of this is to uninstall ALL VERSIONS of vMware vSphere Client and reinstall the software.
Vmrc console has disconnected attempting to reconnect что делать
Обновившись с VMware vSphere 5.0 на VMware vSphere 5.5 я получил неработающий vSphere Data Recovery, на замену которому пришел vSphere Data Protection. И все бы ничего, но неожиданно возник ворох разнообразных граблей с запуском этого сервера резервного копирования.
1. Установочный OVA-файл не видит виртуального свитча dvSwitch и ставится только на VMNetwork, то есть vmnetwork у вас не должен быть удален. Ну и после установки надо не забыть поменять привязку на ethertnet-адаптере.
2. Не возможно подключиться к консоли сервера, vSphere Client выдает ошибку «The VMRC console has disconnected. attempting to reconnect.» Долго соображал как же подключиться к консоли, пока не обнаружил что тот же Vmware Fusion вполне себе хорошо работает с серверами vSphere и, в отличии от vSphere Client, консоль отображает без проблем.
3. Обязательно надо прописать DNS-имя на сервере DNS и в настройке сервера. Иначе все будет тупить и не работать.
4. После всего этого вебинтерфейс начал отзываться, но работать отказывался. Нашел статейку на vmware что разработчики всех популярных браузеров, среди которых Mozilla Firefox, Google Chrome и Internet Explorer в целях безопасности удалили поддержку криптографического алгоритма DSA, который использовался в веб сервере всех версий VDP до 6.0.x включительно. Исправлено начиная с версии 6.0.1 сменой алгоритма DSA на RSA.
Для смены типа алгоритма без обновления VDP vmware предлагает скачать и запустить скрипт исправления 2111900_VDPHotfix.SHA2.sh.zip
Скрипт делает следующее:
Выполнить команды можно в локали машины, зайдя на неё с логином/паролем «root/changeme».
vSphere Client error in Windows 8, “The VMRC console has disconnected…attempting to reconnect.”
*UPDATE 2012-09-11
VMware ESXi 5.1 has now been released to the public along with VIclient v5.1. If you are using Windows 8, view my new post for info on how to avoid console issues as described below as well as the caveats with upgrading to v5.1.
See that screenshot above? This was my nightmare when re-doing my VMWare ESXi setup on my Dell OptiPlex 745. ESXi installed on the OptiPlex 745 just fine, and all of the VI Client features worked in my Windows 8 computer except for the console. A little investigation of this issue points to a warning in the Event Viewer. I found this warning entry for the VMWARE-VMRC.EXE (which is the VMWare Console executable):
Application ‘C:\Program Files (x86)\Common Files\VMware\VMware VMRC Plug-in\Internet Explorer\vmware-vmrc.exe’ (pid 1408) cannot be restarted – Application SID does not match Conductor SID..
Long story short, the VI client as of August 2012 doesn’t work yet in Windows 8 so don’t bother trying. The console view uses an Internet Explorer plug-in, which is not yet compatible with IE10 in Windows 8. Even disabling IE10 and forcing an alternate web browser in Windows 8 doesn’t fix the problem. If you really, really want to use Windows 8, just set up a new Windows XP virtual machine and use the VI client from the VM. That is your only work around for now.
… If VMware wasn’t so entrenched in the enterprise I would only be using Microsoft Hyper-V (Hyper-V 3.0 RTM just might be the version I’ve been waiting for….).