We recently upgraded our VDI platform to VMWare View 6.1 using vSphere 6.0 and Nvidia vGPU (Grid K1). (HP T310 ZeroClient 4.7.1)
Some of our users complaining about disconnects, some users have this error more then others.
Mouse stops moving and after 30 seconds a disconnect.
Here are some log entries:
03/25/2015, 08:42:41.131> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: ==========> New connection request <===========
03/25/2015, 08:42:41.131> LVL:2 RC: 0 AGENT :tera_agent_read_external_udp_address: RegQueryValueEx could not find the pcoip.external_udp_address value in the Software\Policies\Teradici\PCoIP\pcoip_admin_defaults key, sending no value to server.
03/25/2015, 08:42:41.131> LVL:2 RC: 0 AGENT :tera_agent_read_external_udp_address: RegQueryValueEx could not find the pcoip.external_udp_port value in the Software\Policies\Teradici\PCoIP\pcoip_admin_defaults key, sending no value to server.
03/25/2015, 08:42:41.131> LVL:2 RC: 0 AGENT :Client address is 0.0.0.0:0 (host order)
03/25/2015, 08:42:41.132> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: For Soft Host: Using Version 1 Tag
03/25/2015, 08:42:41.132> LVL:2 RC: 0 PRI :pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} Session ID for Soft Host: Tag:'W/AenY+In+UA' Value:5bf01e9d8f889fe5
03/25/2015, 08:42:41.132> LVL:2 RC: 0 AGENT :server_listen_on_addr is 0.0.0.0:0 (host order)
03/25/2015, 08:42:41.132> LVL:1 RC: 0 AGENT :pcoip_agent_connect_req: type = 2
03/25/2015, 08:42:41.132> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} Session ID = 4; codec = 2.
03/25/2015, 08:42:41.132> LVL:1 RC: 0 AGENT :pcoip_agent_connect_req: debug trace log 1
03/25/2015, 08:42:41.133> LVL:2 RC: 0 AGENT :tera_agent_launch_server: {s_tag:0x5bf01e9d8f889fe5} Launching pcoip_server_win32
03/25/2015, 08:42:41.133> LVL:2 RC: 0 AGENT :tera_agent_launch_server: {s_tag:0x5bf01e9d8f889fe5} Optional log file path specified as "C:\ProgramData\VMware\VDM\logs\"
03/25/2015, 08:42:41.133> LVL:2 RC: 0 AGENT :tera_agent_launch_server: {s_tag:0x5bf01e9d8f889fe5} use_vmware_launcher = true.
03/25/2015, 08:42:41.135> LVL:2 RC: 0 AGENT :create_session_process: Opened pcoip server process handle 00000000000003DC
03/25/2015, 08:42:41.135> LVL:2 RC: 0 AGENT :tera_agent_launch_server: {s_tag:0x5bf01e9d8f889fe5} Using VMWare's launcher code: worked [system is vista or newer, windows session id: 0x1, pid: 0x1e4, proc handle: 0x3dc].
03/25/2015, 08:42:41.381> LVL:2 RC: 0 AGENT :sSERVER_SESSION::agent_receiver_callback: message from A:srvr4;B:srvr0004 to A:srvr4, message = 00 00 00 00, len=144
03/25/2015, 08:42:42.135> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] Waiting for ready message.
03/25/2015, 08:42:42.236> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] Got ready message.
03/25/2015, 08:42:42.236> LVL:2 RC: 0 AGENT :selected server_addr is 0.0.0.0:4172 (host order)
03/25/2015, 08:42:42.236> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] Connecting to server's mailbox.
03/25/2015, 08:42:42.236> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] Sending session tag.
03/25/2015, 08:42:42.236> LVL:2 RC: 0 AGENT :sSERVER_SESSION::send_message: {s_tag:0x5bf01e9d8f889fe5} 136 bytes
03/25/2015, 08:42:42.236> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] Sending session option #0 key='pcoip.enable_tera2800' value='1'.
03/25/2015, 08:42:42.236> LVL:2 RC: 0 AGENT :sSERVER_SESSION::send_message: {s_tag:0x5bf01e9d8f889fe5} 48 bytes
03/25/2015, 08:42:42.236> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] Sending session option #1 key='pcoip.priority_level' value='4'.
03/25/2015, 08:42:42.236> LVL:2 RC: 0 AGENT :sSERVER_SESSION::send_message: {s_tag:0x5bf01e9d8f889fe5} 47 bytes
03/25/2015, 08:42:42.236> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] Sending session option #2 key='pcoip.server_fqdn' value='PS-VDI-01.PROJECTSERVE.local'.
03/25/2015, 08:42:42.236> LVL:2 RC: 0 AGENT :sSERVER_SESSION::send_message: {s_tag:0x5bf01e9d8f889fe5} 71 bytes
03/25/2015, 08:42:42.236> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] End of options: sending null-option message
03/25/2015, 08:42:42.236> LVL:2 RC: 0 AGENT :sSERVER_SESSION::send_message: {s_tag:0x5bf01e9d8f889fe5} 26 bytes
03/25/2015, 08:42:42.362> LVL:2 RC: 0 AGENT :sSERVER_SESSION::agent_receiver_callback: message from A:srvr4;B:srvr0004 to A:srvr4, message = 05 00 00 00, len=136
03/25/2015, 08:42:42.388> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] Adding session to list.
03/25/2015, 08:42:42.388> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] Total number of active sessions = 1
03/25/2015, 08:42:42.388> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] Sending connection response ok.
03/25/2015, 08:42:42.388> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] connection_response (end), 0
03/25/2015, 08:42:42.580> LVL:2 RC: 0 AGENT :sSERVER_SESSION::agent_receiver_callback: message from A:srvr4;B:srvr0004 to A:srvr4, message = 0b 00 00 00, len=16
03/25/2015, 08:42:42.602> LVL:2 RC: 0 AGENT :monitor_soft_hosts: {s_tag:0x5bf01e9d8f889fe5} MBX_CON_COMPLETE
03/25/2015, 08:42:42.602> LVL:2 RC: 0 AGENT :monitor_soft_hosts: {s_tag:0x5bf01e9d8f889fe5} connection_complete: SOFT - MBX_CON_COMPLETE
03/25/2015, 08:42:43.645> LVL:2 RC: 0 AGENT :monitor_soft_hosts: {s_tag:0x5bf01e9d8f889fe5} monitor thread: connection_complete(MBX_CON_COMPLETE) callback is successful
03/25/2015, 08:42:43.646> LVL:2 RC: 0 AGENT :mb_send_acknowledgement: {s_tag:0x5bf01e9d8f889fe5} Sending ack.
03/25/2015, 08:42:43.646> LVL:2 RC: 0 AGENT :sSERVER_SESSION::send_message: {s_tag:0x5bf01e9d8f889fe5} 8 bytes
03/25/2015, 08:42:43.748> LVL:2 RC: 0 AGENT :mb_send_acknowledgement: {s_tag:0x5bf01e9d8f889fe5} Succeeded to srvr0004
03/25/2015, 08:52:46.565> LVL:2 RC: 0 AGENT :monitor_soft_hosts: {s_tag:0x5bf01e9d8f889fe5} Server died.
03/25/2015, 08:52:46.666> LVL:2 RC: 0 AGENT :tera_agent_disconnect [soft host]: agent close code: 6, disconnect reason: 0
03/25/2015, 08:52:46.666> LVL:2 RC: 0 AGENT :tera_agent_disconnect: {s_tag:0x5bf01e9d8f889fe5} disconnect is ** NOT ** pending (hndl: 4, pid: 484, process handle: 000003dc)
03/25/2015, 08:52:46.666> LVL:2 RC: 0 AGENT :tera_agent_disconnect: {s_tag:0x5bf01e9d8f889fe5} Server process already exited (hndl: 4, pid: 484, process handle: 000003dc)
03/25/2015, 08:52:46.666> LVL:2 RC: 0 AGENT :tera_agent_finish_disconnect_thread: connection_closed 6
03/25/2015, 08:52:46.939> LVL:2 RC: 0 AGENT :sSERVER_SESSION::~sSERVER_SESSION: {s_tag:0x5bf01e9d8f889fe5} Closing pcoip server process handle 00000000000003DC
03/25/2015, 08:53:01.517> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: ==========> New connection request <===========
03/25/2015, 08:53:01.518> LVL:2 RC: 0 AGENT :tera_agent_read_external_udp_address: RegQueryValueEx could not find the pcoip.external_udp_address value in the Software\Policies\Teradici\PCoIP\pcoip_admin_defaults key, sending no value to server.
03/25/2015, 08:53:01.518> LVL:2 RC: 0 AGENT :tera_agent_read_external_udp_address: RegQueryValueEx could not find the pcoip.external_udp_port value in the Software\Policies\Teradici\PCoIP\pcoip_admin_defaults key, sending no value to server.
03/25/2015, 08:53:01.518> LVL:2 RC: 0 AGENT :Client address is 0.0.0.0:0 (host order)
03/25/2015, 08:53:01.518> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: For Soft Host: Using Version 1 Tag
03/25/2015, 08:53:01.518> LVL:2 RC: 0 PRI :pcoip_agent_connect_req: {s_tag:0x3c5d2733bc4b5aa} Session ID for Soft Host: Tag:'A8XSczvEtaoA' Value:03c5d2733bc4b5aa
03/25/2015, 08:53:01.518> LVL:2 RC: 0 AGENT :server_listen_on_addr is 0.0.0.0:0 (host order)
03/25/2015, 08:53:01.518> LVL:1 RC: 0 AGENT :pcoip_agent_connect_req: type = 2
03/25/2015, 08:53:01.518> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: {s_tag:0x3c5d2733bc4b5aa} Session ID = 5; codec = 2.
03/25/2015, 08:53:01.518> LVL:1 RC: 0 AGENT :pcoip_agent_connect_req: debug trace log 1
New Windows driver is GA and the ESX driver stayed the same so luckily only an update of the Windows driver.
Link is here.
NVIDIA DRIVERS NVIDIA GRID VGPU SOFTWARE RELEASE 346.68/348.27 WHQL
The log lines you've pasted don't show the root cause, only that the pcoip session was terminated:
03/25/2015, 08:52:46.565> LVL:2 RC: 0 AGENT :monitor_soft_hosts: {s_tag:0x5bf01e9d8f889fe5} Server died.
You can look at the pcoip_server log file to see why it terminated. Depending on the cause you may need to look at client logs too.
This is what i could find on another system regarding server logs.
03/23/2015, 08:35:12.376> LVL:2 RC: 0 SCNET :(scnet_setup_server_certificates): Setting verification depth to 1
03/23/2015, 08:35:12.376> LVL:2 RC: 0 PRI :tera_pri_server_reserve: Reservation Session ID: 'VpjB+AqPUnYA' Value:5698c1f80a8f5276
03/23/2015, 08:35:12.376> LVL:2 RC: 0 COMMON :parse_janus_session_tag: session tag flags = 0x5A81
03/23/2015, 08:35:12.376> LVL:2 RC: 0 SERVER :handle_null_option_msg_from_agent: sending back updated session tag
03/23/2015, 08:35:12.406> LVL:2 RC: 0 SERVER :server mailbox: MBX_SHUTDOWN with agent disconnect reason code (0x5)
03/23/2015, 08:35:12.406> LVL:2 RC: 0 SERVER :server mailbox: Stopping mailbox message loop
03/23/2015, 08:35:12.406> LVL:2 RC: 0 SERVER :server main: got terminate application message
03/23/2015, 08:35:12.406> LVL:2 RC: 0 SERVER :server main: exiting
03/23/2015, 08:35:12.406> LVL:2 RC: 0 SERVER :server cleanup: tearing down pcoip with agent disconnect reason code(5) and waiting
03/23/2015, 08:35:12.406> LVL:1 RC: 0 SERVER :map_agent_to_tera: DISCONNECT_FOR_RECONNECT -> TERA_DISCONNECT_CAUSE_HOST_BROKER_RECONNECT
03/23/2015, 08:35:12.406> LVL:0 RC: 0 MGMT_SESS :Tearing down the session
03/23/2015, 08:35:12.406> LVL:1 RC: 0 VGMAC :Stat frms: R=000000/000000/000000 T=000000/000000/000000 (A/I/O) Loss=0.00%/0.00% (R/T)
03/23/2015, 08:35:12.406> LVL:2 RC: 0 COMMON :TERA_PCOIP: SESSION_EVENT=TERA_MGMT_SYS_SESS_EVENT_RESET, disconnect cause (0x105)
03/23/2015, 08:35:12.406> LVL:2 RC: 0 SERVER :server main: cb_notify_session_status called (mask 0x10) with tera_disconnect_cause (0x105)
03/23/2015, 08:35:12.406> LVL:2 RC: 0 SERVER :server main: TERA_MGMT_SYS_SESS_EVENT_RESET with disconnect cause (0x105).
03/23/2015, 08:35:12.406> LVL:1 RC: 0 SERVER :map_tera_to_agent_close_code: TERA_DISCONNECT_CAUSE_HOST_BROKER_RECONNECT -> PCOIP_AGENT_CLOSE_CODE_BROKER_INITIATED
03/23/2015, 08:35:12.406> LVL:1 RC: 0 VGMAC :Session stats: Average TX=0 average RX=0 (Mbps) Loss=0.00%/0.00% (R/T)
03/23/2015, 08:35:12.406> LVL:2 RC: 0 MGMT_SYS :Session closed remotely!
03/23/2015, 08:35:12.406> LVL:2 RC: 0 MGMT_SYS :********************************************************
03/23/2015, 08:35:12.406> LVL:2 RC: 0 MGMT_SYS :********************************************************
03/23/2015, 08:35:12.406> LVL:2 RC: 0 MGMT_SYS :********************************************************
03/23/2015, 08:35:12.406> LVL:2 RC: 0 MGMT_SYS :********************************************************
03/23/2015, 08:35:12.406> LVL:2 RC: 0 SERVER :connection_closed: code = 2.
03/23/2015, 08:35:12.506> LVL:2 RC: 0 MGMT_VCHAN :VChanPluginExit: Closing plugin 'VMware_Server'.
03/23/2015, 08:35:12.533> LVL:2 RC: 0 MGMT_VCHAN :VChanPluginExit: Plugin 'VMware_Server' is closed.
03/23/2015, 08:35:12.533> LVL:2 RC: 0 MGMT_VCHAN :VChanPluginExit: Closing plugin 'VMwareView-RdeVchanStub'.
03/23/2015, 08:35:12.533> LVL:2 RC: 0 MGMT_VCHAN :VChanPluginExit: Plugin 'VMwareView-RdeVchanStub' is closed.
03/23/2015, 08:35:12.533> LVL:2 RC: 0 MGMT_VCHAN :VChanPluginExit: Closing plugin 'ViewMMDevRedir'.
03/23/2015, 08:35:12.533> LVL:2 RC: 0 MGMT_VCHAN :VChanPluginExit: Plugin 'ViewMMDevRedir' is closed.
03/23/2015, 08:35:12.533> LVL:2 RC: 0 MGMT_VCHAN :VChanPluginExit: Closing plugin 'pcoip_mfw'.
03/23/2015, 08:35:12.533> LVL:2 RC: 0 MGMT_VCHAN :VChanPluginExit: Plugin 'pcoip_mfw' is closed.
03/23/2015, 08:35:12.533> LVL:1 RC: 0 MGMT_VCHAN :=> Successfully exited all the VChan plugins
03/23/2015, 08:35:12.534> LVL:2 RC: 0 SERVER :server cleanup: detaching inputdevtap
03/23/2015, 08:35:12.534> LVL:0 RC: 0 EXTERN :input_devtap ==> InputDevTapWin32PollThreadStop Signaling win32 poll thread at index 0 stop event.
03/23/2015, 08:35:12.534> LVL:0 RC: 0 EXTERN :input_devtap ==> InputDevTapWin32PollThreadStop win32 poll thread at index 0 stopped successfully.
03/23/2015, 08:35:12.534> LVL:0 RC: 0 EXTERN :input_devtap ==> InputDevTapWin32PollThreadStop closing poll thread stop event.
03/23/2015, 08:35:12.534> LVL:0 RC: 0 EXTERN :input_devtap ==> InputDevTapWin32PollThreadStop Signaling win32 poll thread at index 1 stop event.
03/23/2015, 08:35:12.534> LVL:0 RC: 0 EXTERN :input_devtap ==> InputDevTapWin32PollThreadStop win32 poll thread at index 1 stopped successfully.
03/23/2015, 08:35:12.534> LVL:0 RC: 0 EXTERN :input_devtap ==> InputDevTapWin32PollThreadStop closing poll thread stop event.
03/23/2015, 08:35:12.538> LVL:0 RC: 0 EXTERN :input_devtap ==> RdeGetImpersonatedTokenAsLogonUser: Unable to query user token of session 0 (err 1008). Remote Desktop service may not be running.
03/23/2015, 08:35:12.538> LVL:0 RC: 0 EXTERN :input_devtap ==> RdeGetImpersonatedTokenAsLogonUser: No shell window to impersonate.
03/23/2015, 08:35:12.538> LVL:2 RC: 0 SERVER :server cleanup: closing mailboxes
03/23/2015, 08:35:12.538> LVL:2 RC: 0 SERVER :server cleanup: freeing argument copy
03/23/2015, 08:35:12.538> LVL:2 RC: 0 SERVER :server cleanup: cleanup complete
The only thing i could find was TERA_DISCONNECT_CAUSE_HOST_BROKER_RECONNECT 0x00000105
"Pre-connection warmup initialization of PCoIP Server. This is not for actual connection. If the size of the log is under 15 Kbytes, this is a pre-connection warmup startup/shutdown sequence."
There is another TERA_DISCONNECT_CAUSE_HOST_BROKER_RECONNECT 0x00000105 in VMware KB: PCoIP Disconnection Codes , but the user doesn't get the message that he's been disconnect due to login from another location, just "You have been disconnected".
Hey,
Have you ever find a solution for this issue? We are in the same boat as it seems. Only thing is we don't only have it with the TC's but with all clients. Plus we are using AppVolumes but don't think this will be it.
What i did is compare the agent against the server logs and the one strange thing i found as last logging is this.
MGMT_HDA :Speaker audio encoding changed to MONO-8K-ADPCM
I've opened a ticket and uploaded logs regarding this issue, so far still getting disconnects.
Thanks for your reply, i will do the same thing and see what happens.
I will also check with the networking department to see if they have an idea of what happens. If i find or hear anything i will let you know.
I do know that they changed the PCoIP protocol, maybe there's still a bug inthere.
Do you also have issues with monitor refreshments? We see large white parts in the screen, mostlty wiith Excel that seems to be a bug in the configuration we're using (vgpu with VSphere 6.0 and horizon 6.1).Non vGPU users don't have these issues.
I already raised a call to see if it is a bug.
Hey projectserve,
It seems like we might have a solution.
Did you try to use Aero in your VDI when using vGPU?
I know it is somewhat far fetched but after changing to Aero display a few issues just disappeared and it looks like we don't have display refresh issues and as it seems now no disconnects. See information below i received from a VMWare engineer
I have seen reports of an issue with vGPU and artifacting in Excel. If it is not already enabled, can you enable Windows Aero on the Windows 7 machine and retest? This was found to workaround the previously reported artifacting issue which Nvidia is working to resolve.
We are using Aero by default.
Hi Ray_handels,
Thank you for your tip.
We also have exactly the same issue with vGPU.
I'll try to switch the Aero on and see if the problem still persists.
Hey Alexey,
There seems to be a new driver which is available through the link below. Í'm in the process of working with a VMWare Engineer in installing this driver into the golden image. We are using the k120Q option (so 32 cards on our K1) but we still have some "discussion" if the driver is correct. If i look into the .inf files provided in the driver I cannot see the hardware ID of the K120Q which is PCI\VEN_10DE&DEV_0FF7.
We are still, to this day, having quite some disconnect issues and I truly hope VMWare/NVidia will deliver a solution on short term, otherwise we cannot use it in production.
http://www.nvidia.com/download/driverResults.aspx/84395/en-us
Anyway, after enabling Aero we never ever had that issue with thw "white spaces" again so that was indeed fixed by using Aero
Guys,
New driver is available. We will be trying it out asap. Any else wanne try out and let us know if it works??
http://www.nvidia.co.uk/download/driverResults.aspx/85399/en-uk
I will.
I was looking through release notes and the white spaces issues is not mentioned anymore which implies it is indeed fixed with this version.
Unfortenately this was also in the document. So it seems like they actually did acknowlegde there being an issue with disconnects but unfortenately it is not fixed yet (so it seems). We will still be testing however to see what gives.
#59 Horizon session shows a black screen and then disconnects when establishing a multi-monitor connection Description At times a Horizon session disconnects when establishing a multi-monitor connection. Windows Event Viewer shows that pciop_server process crashed, as a result the Horizon session could not be established. Version Workaround None Status Open Ref. # 1638314
Hi Projectserve,
Could you please grep PCoIP server log with this "svga_devtap " keyword. I want to see whether capturing screen buffer is successfully established with nVidia driver.
Thanks.
Hi h3nkYh3nkY,
here are the svga_devtap greps.
05/20/2015, 07:27:48.551> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap setting global loglevel to 10
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY1, flags 0x0
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY2, flags 0x0
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K120Q, name \\.\DISPLAY3, flags 0x80005
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K120Q
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K120Q, name \\.\DISPLAY4, flags 0x80000
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K120Q
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDPDD Chained DD, name \\.\DISPLAYV1, flags 0x200008
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Encoder Mirror Driver, name \\.\DISPLAYV2, flags 0x200008
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Reflector Display Driver, name \\.\DISPLAYV3, flags 0x200008
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> vmwDisplays 2, nvDisplays 2, amdDisplays 0
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: connecting to driver: Try VMW 0 NoWDDM 0, force win32 0
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: connecting to driver: NV displays available 2 NVFBC disabled 0
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: profiling disabled.
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY1, flags 0x0
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY2, flags 0x0
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K120Q, name \\.\DISPLAY3, flags 0x80005
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K120Q
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K120Q, name \\.\DISPLAY4, flags 0x80000
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K120Q
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDPDD Chained DD, name \\.\DISPLAYV1, flags 0x200008
05/20/2015, 07:27:54.044> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Encoder Mirror Driver, name \\.\DISPLAYV2, flags 0x200008
05/20/2015, 07:27:54.045> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Reflector Display Driver, name \\.\DISPLAYV3, flags 0x200008
05/20/2015, 07:27:54.045> LVL:0 RC: 0 EXTERN :svga_devtap ==> vmwDisplays 2, nvDisplays 2, amdDisplays 0
05/20/2015, 07:27:54.045> LVL:0 RC: 0 EXTERN :svga_devtap ==> The default path is C:\Windows\Syswow64\NvFBC.dll
05/20/2015, 07:27:54.203> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: NvFBC reports capture is possible.
05/20/2015, 07:27:54.203> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: using NvFBC version 0
05/20/2015, 07:27:54.544> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: created the sys object - adapter 0, sys object BD9B060
05/20/2015, 07:27:54.577> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: handshake usermode backend
05/20/2015, 07:27:54.577> LVL:0 RC: 0 EXTERN :svga_devtap ==> found: driver:0.11 build-2471431, client:0.11 build-2471431
05/20/2015, 07:27:54.577> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: svga driver API version:0.11 build-2471431, driver version: 0.0 ("0.0.0.0"), build-0
05/20/2015, 07:27:54.577> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTap_Attach2: inRdsSession 0 sessionId 2
05/20/2015, 07:27:56.331> LVL:0 RC: 0 EXTERN :svga_devtap ==> The default path is C:\Windows\Syswow64\NvFBC.dll
05/20/2015, 07:27:56.461> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: NvFBC reports capture is possible.
05/20/2015, 07:27:56.461> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: using NvFBC version 0
05/20/2015, 07:27:56.746> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: created the sys object - adapter 0, sys object BD9B060
04/10/2015, 13:27:52.209> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap setting global loglevel to 5
04/10/2015, 13:27:54.997> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY1, flags 0x0
04/10/2015, 13:27:54.997> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D
04/10/2015, 13:27:54.997> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY2, flags 0x0
04/10/2015, 13:27:54.997> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D
04/10/2015, 13:27:54.997> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K120Q, name \\.\DISPLAY3, flags 0x80005
04/10/2015, 13:27:54.997> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K120Q
04/10/2015, 13:27:54.997> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K120Q, name \\.\DISPLAY4, flags 0x80001
04/10/2015, 13:27:54.997> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K120Q
04/10/2015, 13:27:54.998> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDPDD Chained DD, name \\.\DISPLAYV1, flags 0x200008
04/10/2015, 13:27:54.998> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Encoder Mirror Driver, name \\.\DISPLAYV2, flags 0x200008
04/10/2015, 13:27:54.998> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Reflector Display Driver, name \\.\DISPLAYV3, flags 0x200008
04/10/2015, 13:27:54.998> LVL:0 RC: 0 EXTERN :svga_devtap ==> vmwDisplays 2, nvDisplays 2, amdDisplays 0
04/10/2015, 13:27:54.999> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: connecting to driver: Try VMW 0 NoWDDM 0, force win32 0
04/10/2015, 13:27:54.999> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: connecting to driver: NV displays available 2 NVFBC disabled 0
04/10/2015, 13:27:54.999> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: profiling disabled.
04/10/2015, 13:27:54.999> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY1, flags 0x0
04/10/2015, 13:27:54.999> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D
04/10/2015, 13:27:54.999> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY2, flags 0x0
04/10/2015, 13:27:54.999> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D
04/10/2015, 13:27:54.999> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K120Q, name \\.\DISPLAY3, flags 0x80005
04/10/2015, 13:27:54.999> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K120Q
04/10/2015, 13:27:54.999> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K120Q, name \\.\DISPLAY4, flags 0x80001
04/10/2015, 13:27:54.999> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K120Q
04/10/2015, 13:27:54.999> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDPDD Chained DD, name \\.\DISPLAYV1, flags 0x200008
04/10/2015, 13:27:54.999> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Encoder Mirror Driver, name \\.\DISPLAYV2, flags 0x200008
04/10/2015, 13:27:55.000> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Reflector Display Driver, name \\.\DISPLAYV3, flags 0x200008
04/10/2015, 13:27:55.000> LVL:0 RC: 0 EXTERN :svga_devtap ==> vmwDisplays 2, nvDisplays 2, amdDisplays 0
04/10/2015, 13:27:55.003> LVL:0 RC: 0 EXTERN :svga_devtap ==> The default path is C:\Windows\Syswow64\NvFBC.dll
04/10/2015, 13:27:55.208> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: NvFBC reports capture is possible.
04/10/2015, 13:27:55.208> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: using NvFBC version 0
04/10/2015, 13:27:55.571> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: created the sys object - adapter 0, sys object BA5B930
04/10/2015, 13:27:55.575> LVL:0 RC: 0 EXTERN :svga_devtap ==> The default path is C:\Windows\Syswow64\NvFBC.dll
04/10/2015, 13:27:55.760> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: NvFBC reports capture is possible.
04/10/2015, 13:27:55.760> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: using NvFBC version 0
04/10/2015, 13:27:55.880> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: NvFBC can't create now, adapter 1
04/10/2015, 13:27:55.880> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: UpdateDisplayWatcher ERROR
04/10/2015, 13:27:55.902> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: usermode backend init failed
04/10/2015, 13:27:56.902> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY1, flags 0x0
04/10/2015, 13:27:56.902> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D
04/10/2015, 13:27:56.902> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY2, flags 0x0
04/10/2015, 13:27:56.902> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D
04/10/2015, 13:27:56.902> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K120Q, name \\.\DISPLAY3, flags 0x80005
04/10/2015, 13:27:56.902> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K120Q
04/10/2015, 13:27:56.902> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K120Q, name \\.\DISPLAY4, flags 0x80001
04/10/2015, 13:27:56.902> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K120Q
04/10/2015, 13:27:56.902> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDPDD Chained DD, name \\.\DISPLAYV1, flags 0x200008
04/10/2015, 13:27:56.902> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Encoder Mirror Driver, name \\.\DISPLAYV2, flags 0x200008
04/10/2015, 13:27:56.902> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Reflector Display Driver, name \\.\DISPLAYV3, flags 0x200008
04/10/2015, 13:27:56.902> LVL:0 RC: 0 EXTERN :svga_devtap ==> vmwDisplays 2, nvDisplays 2, amdDisplays 0
04/10/2015, 13:27:56.902> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: connecting to driver: Try VMW 0 NoWDDM 0, force win32 0
04/10/2015, 13:27:56.902> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: connecting to driver: NV displays available 2 NVFBC disabled 0
04/10/2015, 13:27:56.902> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: profiling disabled.
04/10/2015, 13:27:56.902> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY1, flags 0x0
04/10/2015, 13:27:56.902> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D
04/10/2015, 13:27:56.902> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY2, flags 0x0
04/10/2015, 13:27:56.903> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D
04/10/2015, 13:27:56.903> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K120Q, name \\.\DISPLAY3, flags 0x80005
04/10/2015, 13:27:56.903> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K120Q
04/10/2015, 13:27:56.903> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K120Q, name \\.\DISPLAY4, flags 0x80001
04/10/2015, 13:27:56.903> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K120Q
04/10/2015, 13:27:56.903> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDPDD Chained DD, name \\.\DISPLAYV1, flags 0x200008
04/10/2015, 13:27:56.903> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Encoder Mirror Driver, name \\.\DISPLAYV2, flags 0x200008
04/10/2015, 13:27:56.903> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Reflector Display Driver, name \\.\DISPLAYV3, flags 0x200008
04/10/2015, 13:27:56.903> LVL:0 RC: 0 EXTERN :svga_devtap ==> vmwDisplays 2, nvDisplays 2, amdDisplays 0
04/10/2015, 13:27:56.903> LVL:0 RC: 0 EXTERN :svga_devtap ==> The default path is C:\Windows\Syswow64\NvFBC.dll
04/10/2015, 13:27:57.000> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: NvFBC reports capture is possible.
04/10/2015, 13:27:57.000> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: using NvFBC version 0
04/10/2015, 13:27:57.247> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: created the sys object - adapter 0, sys object BA5B930
04/10/2015, 13:27:57.251> LVL:0 RC: 0 EXTERN :svga_devtap ==> The default path is C:\Windows\Syswow64\NvFBC.dll
04/10/2015, 13:27:57.345> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: NvFBC reports capture is possible.
04/10/2015, 13:27:57.345> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: using NvFBC version 0
04/10/2015, 13:27:57.599> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: created the sys object - adapter 1, sys object BA5BB00
04/10/2015, 13:27:57.603> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: handshake usermode backend
04/10/2015, 13:27:57.603> LVL:0 RC: 0 EXTERN :svga_devtap ==> found: driver:0.11 build-2471431, client:0.11 build-2471431
04/10/2015, 13:27:57.603> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: svga driver API version:0.11 build-2471431, driver version: 0.0 ("0.0.0.0"), build-0
04/10/2015, 13:27:57.604> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTap_Attach2: inRdsSession 0 sessionId 1
Crashlog:
Naam van toepassing met fout: pcoip_server_win32.exe, versie: 3.30.1.43017, tijdstempel: 0x54cf48a6
Naam van module met fout: NvFBC.dll, versie: 6.14.13.4752, tijdstempel: 0x54d3ad55
Uitzonderingscode: 0xc0000005
Foutoffset: 0x00002474
Id van proces met fout: 0x910
Starttijd van toepassing met fout: 0x01d0912d7b727667
Pad naar toepassing met fout: C:\Program Files\Common Files\VMware\Teradici PCoIP Server\pcoip_server_win32.exe
Pad naar module met fout: C:\Windows\Syswow64\NvFBC.dll
Rapport-id: fdd095bf-fd25-11e4-a3b5-005056953cb7
We've installed new drivers for ESC and Windows and the white square issue is gone if Aero is disabled so that works as intended.
We now have a few people working on the VDI machines with the new drivers and so far no disconnects.
If we do have disconnects i will let you guys know.
projectserve I would suggest installing the new driver (if possible off course due to downtime) but it seems like it's worth a shot.
Thanks for the info; also i noticed from Vmware when u use 1 vCPU u don't get dissconects aswell.. (not a solution, but a temp fix..) Need to test both..
We also have here the same problem with disconnections. Someone knows when NVIDA will fix this issue #59? Tomorrow I wil try to use 1vGPU and Aero disabled.
When we use only one monitor then we do not have disconnections.