ESXi

 View Only
  • 1.  [SOLVED] VMRC Error. Cannot open console!

    Posted Dec 19, 2011 05:59 AM

    I keep getting the following error whenever i click on console:

    this is completely frustrating as i have no ability to reach anything.

    i have rebooted the esxi vsphere5 box, i have rebooted my local pc.



  • 2.  RE: [SOLVED] VMRC Error. Cannot open console!

    Posted Dec 19, 2011 06:53 AM

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

    5. Uninstall vSphere client on the desktop machine and reinstall see if this issue exist.

    Also refer the below existing thread on the same issue.,

    http://communities.vmware.com/thread/333026

    Award points for the helpful and correct answer by clicking the below tab :smileyhappy:



  • 3.  RE: [SOLVED] VMRC Error. Cannot open console!

    Posted Dec 19, 2011 10:27 AM

    i tried your suggestions and its not working.

    reinstalling the client after uninstall and also reset the vm.

    another thing i cant do is move to another host. i only have this one host...

    i wish this error was a bit more descriptive...

    in the meantime i am stuck. cant do anything.



  • 4.  RE: [SOLVED] VMRC Error. Cannot open console!

    Posted Dec 19, 2011 10:44 AM

    Is the vmware tools upto date on the VM.,

    Did you try open the console in a seperate window and see if that is working.

    What is the version of vsphere client your using. is that downloaded from the link with the host name.

    did you disable firewall in your local desktop

    is that a physical firewall sitting between esxi host and computer wheren vsphere client is installed, if so make sure port 902 and 903 is open.



  • 5.  RE: [SOLVED] VMRC Error. Cannot open console!

    Posted Dec 19, 2011 10:52 AM

    i can only guess this problem has to be something with the host server itself.

    the  error hints at some buggy code  "d:/build/ob/bora-422570/lib/pollDefault/pollDefault.c:3141" .... so its  polling but failing? perhaps. i guess we'll never know since we cant  see that c file.

    another interesting thing is its saying to find  the log file in the Appdata\Local\Temp\ folder but there is no sub  vmware-**** folder.

    i  also tried another user name. same error. thats why i am confident the  error is not the client nor the virtual machine. its the host software.

    this is version 5.0.0 of the vsphere client.

    there  is no firewall or anything. this is very much a direct connection. it  was working fine last night . ... i have changed absolutely nothing!



  • 6.  RE: [SOLVED] VMRC Error. Cannot open console!

    Posted Dec 19, 2011 11:05 AM

    i wonder if vmware has any statement about this?

    i have tried rebooting the host and i cant get to it for the last 10 minutes. i may have to go to the location and just reinstall...



  • 7.  RE: [SOLVED] VMRC Error. Cannot open console!

    Posted Dec 19, 2011 05:41 PM

    good news.

    i tried two other computers and none of them had the problem. everything worked as expected.

    i guess the problem is now isolated to that one specific pc.



  • 8.  RE: [SOLVED] VMRC Error. Cannot open console!

    Posted Dec 20, 2011 11:48 AM

    Problem has been resolved.

    Although this is not a fix for someone not wanting to start over .. it worked for me.

    contrary to my thoughts at first it appears the probelm was my local pc.

    as i have stated in the last posting i had two other pcs that worked fine and didnt show this error.

    well now going back to my main pc i decided today to do a complete format of windows7 and reinstall over again.

    that seemed to have fix it completely and vmware console is working perfectly.



  • 9.  RE: [SOLVED] VMRC Error. Cannot open console!

    Posted Dec 23, 2011 01:28 PM

    I recently had the same problem.   While not finding the solution, I did find that it was tied to the userid on the local machine.   Using a different (new) userid made the problem go away.  

    Not a great solution but better than reinstalling the entire OS.

    Hope someone finds the root cause of this issue.

    Dan