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.
Client : Vsphere 5
Client OS : Windows 8 Developer Preview
When connecting from a windows 7 client to the same VM there is No problem.
Anyone who knows a solution for this?
Thanks!
Nobody??
Addition log info:
viclient:QuickInf:W:17] 2011-10-12 14:51:26.551 WaitForUpdates Version = 117
[viclient:SoapTran:W:17] 2011-10-12 14:51:26.551 Invoke 312 Start WaitForUpdates on PropertyCollector:ha-property-collector [192.168.2.4]. [operationID:90EBB95D-00000138]
[viclient:SrvMsg :W:17] 2011-10-12 14:51:26.551 RMI Request Vmomi.Core.PropertyCollector.WaitForUpdates - 312
<version>117</version>
[viclient:Detailed:M: 7] 2011-10-12 14:51:26.551 in Inventory.OnUpdates(FilterUpdate[])
[ :QuickInf:M: 7] 2011-10-12 14:51:26.551 EmbeddedVMRC::Creating a new console
[viclient:QuickInf:M: 7] 2011-10-12 14:51:26.551 Begin inventory tree update: changed nodes: 1, removed nodes 0
[viclient:QuickInf:M: 7] 2011-10-12 14:51:26.551 End inventory tree update
[ erfInfo:P:33] 2011-10-12 14:51:39.811 [Hndl:GDI=273][Hndl:User=271][Hndl:Kernel=1005][Mem:WS=188559360 (179.82 MB)][Mem:VirtualUsed=667885568 (636.95 MB)][Mem:PrivateUsed=149995520 (143.05 MB)][Mem:NETUsed=17633352 (16.82 MB)][Mem:PF=149995520 (143.05 MB)][Mem:PagedUsed=942152 (920.07 KB)][Mem:NonPagedUsed=120240 (117.42 KB)][CPU:Threads=36][CPU:Total=00:00:24.1801550][CPU:User=00:00:21.2473362][CPU:Kernel=00:00:02.9328188]
[viclient:SoapTran:W:20] 2011-10-12 14:51:41.434 Invoke 23 Finish WaitForUpdates on PropertyCollector:session[522b51a5-15bc-cc0e-8c7d-6f3ad8c95cfe]5224c207-ee8b-b909-e23d-c96ae1e1f9e0 [192.168.2.4] - Serial:0.000, Server:899.881
Suppressed: VirtualInfrastructure.Soap.MethodInvocationSoapImpl: The request failed because the remote server '192.168.2.4' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)
[viclient:Error :W:20] 2011-10-12 14:51:41.434 ConnectionError occurred while executing WFU
VirtualInfrastructure.Exceptions.RequestTimedOut: The request failed because the remote server '192.168.2.4' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)
at VirtualInfrastructure.Soap.SoapServiceWrapper.DoInvokeSync(ManagedObject mo, MethodName methodName, Object[] parameters, Int32 timeoutSecs)
at VirtualInfrastructure.Soap.SoapTransport.VirtualInfrastructure.Transport.InvokeMethod(ManagedObject mo, MethodName methodName, Object[] pars)
at VirtualInfrastructure.ManagedObject.InvokeMethod(MethodName methodName, Object[] pars)
at Vmomi.Core.PropertyCollector.WaitForUpdates(String version)
at VirtualInfrastructure.Updates.PollerDispatcherImpl.ExecuteSingleWFU()
at VirtualInfrastructure.Updates.PollerDispatcherImpl.PollWaitForUpdates()
System.Net.WebException: The command has timed out as the remote server is taking too long to respond.
--- End of inner exception stack trace ---
[viclient:SoapTran:W:20] 2011-10-12 14:51:41.434 Invoke 313 Start CancelWaitForUpdates on PropertyCollector:session[522b51a5-15bc-cc0e-8c7d-6f3ad8c95cfe]5224c207-ee8b-b909-e23d-c96ae1e1f9e0 [192.168.2.4]. [operationID:90EBB95D-00000139][Caller: VirtualInfrastructure.Updates.PollerDispatcherImpl.PollWaitForUpdates]
[viclient:SrvMsg :W:20] 2011-10-12 14:51:41.434 RMI Request Vmomi.Core.PropertyCollector.CancelWaitForUpdates - 313
[viclient:QuickInf:W:20] 2011-10-12 14:51:41.434 WaitForUpdates Version = 1
[viclient:SoapTran:W:20] 2011-10-12 14:51:41.434 Invoke 314 Start WaitForUpdates on PropertyCollector:session[522b51a5-15bc-cc0e-8c7d-6f3ad8c95cfe]5224c207-ee8b-b909-e23d-c96ae1e1f9e0 [192.168.2.4]. [operationID:90EBB95D-0000013A]
[viclient:SrvMsg :W:20] 2011-10-12 14:51:41.434 RMI Request Vmomi.Core.PropertyCollector.WaitForUpdates - 314
<version>1</version>
[viclient:SoapTran:P:40] 2011-10-12 14:51:41.434 Invoke 313 Finish CancelWaitForUpdates on PropertyCollector:session[522b51a5-15bc-cc0e-8c7d-6f3ad8c95cfe]5224c207-ee8b-b909-e23d-c96ae1e1f9e0 [192.168.2.4] - Serial:0.000, Server:000.004
[viclient:SrvMsg :40] 2011-10-12 14:51:41.434 RMI Result Vmomi.Core.PropertyCollector.CancelWaitForUpdates - 313
<Result />
[viclient:SoapTran:W:20] 2011-10-12 14:51:41.434 Invoke 314 Finish WaitForUpdates on PropertyCollector:session[522b51a5-15bc-cc0e-8c7d-6f3ad8c95cfe]5224c207-ee8b-b909-e23d-c96ae1e1f9e0 [192.168.2.4] - Serial:0.001, Server:000.005
Suppressed: VirtualInfrastructure.Soap.MethodInvocationSoapImpl: The task was canceled by a user.
[viclient:Error :W:20] 2011-10-12 14:51:41.434 RequestCanceled fault occurred while executing WFU
Vmomi.Fault.RequestCanceled: The task was canceled by a user.
at VirtualInfrastructure.Soap.SoapServiceWrapper.DoInvokeSync(ManagedObject mo, MethodName methodName, Object[] parameters, Int32 timeoutSecs)
at VirtualInfrastructure.Soap.SoapTransport.VirtualInfrastructure.Transport.InvokeMethod(ManagedObject mo, MethodName methodName, Object[] pars)
at VirtualInfrastructure.ManagedObject.InvokeMethod(MethodName methodName, Object[] pars)
at Vmomi.Core.PropertyCollector.WaitForUpdates(String version)
at VirtualInfrastructure.Updates.PollerDispatcherImpl.ExecuteSingleWFU()
at VirtualInfrastructure.Updates.PollerDispatcherImpl.PollWaitForUpdates()
[viclient:Critical:W:20] 2011-10-12 14:51:41.434 Plugin caused a cancel of the WFU loop, ignoring...
[viclient:QuickInf:W:20] 2011-10-12 14:51:41.434 WaitForUpdates Version = 1
[viclient:SoapTran:W:20] 2011-10-12 14:51:41.434 Invoke 315 Start WaitForUpdates on PropertyCollector:session[522b51a5-15bc-cc0e-8c7d-6f3ad8c95cfe]5224c207-ee8b-b909-e23d-c96ae1e1f9e0 [192.168.2.4]. [operationID:90EBB95D-0000013B]
[viclient:SrvMsg :W:20] 2011-10-12 14:51:41.434 RMI Request Vmomi.Core.PropertyCollector.WaitForUpdates - 315
<version>1</version>
Getting the same error, though it does not appear when I RDP in to the vCenter server itself, and open the same VM console.
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.
Someone who knows a solution for this issue?
similiar here,
error comes with:
vsphere Client 5 connected to vcenter 5 (vm is residing on esxi 4.1)
vsphere Client 5 connected directly to esxi (5)
everything is ok when using:
vsphere Client 5 connected directly to esxi (4.1)
all times using vi-client on windows 8 dev preview
everything is ok when using W2K3 as vi-client
ng, Berndt
PS: also the webclient v5 says that the clientplugin used to connect to the console is not installed (although it is).
I too am having the same issue using the Windows 8 Consumer Preview x64 (Build 8250) edition.
Hi, getting the same issue here.
I get the following output in a plugin-xxx.log file generated when starting vSphere client in C:\Users\<xxxxxxxx>\AppData\Local\Temp\vmrc-plugin : (where <xxxxxxxx> is your user name)
I uninstalled / reinstalled vSphere client to no avail, removed/reinstalled VMRC plugin, rebooted, registered vmwareRemoteConsole.dll with regsvr32, tried various compatibility modes/run as admin combinations nothing helped yet.
Still investigating.
Max
updated path of the log file
I too am having this exact same issue except from win 8 consumer preview. Have tried troubleshooting to no avail. Am looking forward to someone smarter than me figuring this out :smileysilly:
I'm having the same problem. Are there people that aren't or is this everyone on windows 8?
This seems to be a Windows 8 issue. A workaround I have been using is to either RDP to a Windows 7/2008 R2 host with the vSphere client installed or use Workstation 8 to connect to vCenter.
Using vSphere 5 U1 with Windows 8 CP and still have the same VMRC connectivity problem as everyone else.
However I am able to use Workstation 8.0.2 to connect to the host and view the remote console of the VM's An OK workaround.
I think the issue has to do with IE10 and some of the new hardening features they put in it. After looking online it seems the vmrc process is created through a browser plugin, which WKST 8 either does in a different way or has been updated to handle IE 10 and the new hardening features on 8. I will try and virtualize the console by sequencing it on Windows 7 and see if that makes a difference.
I am also having this problem from Windows 8 Server beta.
I am able to connect to vSphere v4, but I cannot connect to the console of VMs on our server that was upgraded to v5.
I think that there is some evidence that this is an IE10 issue. I found this thread:
http://communities.vmware.com/thread/156057
Which documents the command line usage of "vmware-vmrc.exe". I was able to connect to the vSphere 5 hosted consoles using this method.
Hello,
is there still no solution or well work-arround for this issue??
I am currently out of the office and will return Wednesday, July 25th. I will intermittently check and respond to emails and voicemails during this time.
-Brian
this is ridiculous! vmware needs to stay ahead of stuff like this.
Do you have an option to run with compatiblity mode? Try it
Same issue with the client U1a :smileycry: