VMware Horizon Community
MBoes
Contributor
Contributor
‎08-11-2016 01:39 AM

View Client 3.5.2 printers not mapped from Win2008r2 host.

Hello,
After we upgraded from VMWare view client 5.4 to 3.5.2 client printers are no longer mapped in the session.
Using client 5.4 printers are mapped, but after the last round of Windows updates the 5.4 client fails to start with an "the handle is in the wrong state for the requested operation" error.
VMWare Horizon View Client 3.5.2.30397 is installed on Windows 2008R2 running XenApp 6.5.
Users login to the Citrix environment and use the Horizon View client to connect to a 3rd party virtual desktop running Windows 7 with VMWare View Agent 5.1.3.1007228.
Login is successful, but the users printers are not mapped in the virtual desktop.
Running tpautoconnect -d followed by tpautoconnect -v takes ages and ends with the following error.
C:\Program Files\VMware\VMware Tools>TPAutoConnect.exe -d
VCServerAPI::CheckForClientPlugin(): Connected to client XXXXXXXXXX
VCServerAPI::Init(): Protocol = PCoIP
ThinPrint AutoConnect component, Copyright (c) 1999-2012 Cortado AG, 8.8.745.2
VCServerAPI::Exit(): Protocol = NONE
C:\Program Files\VMware\VMware Tools>TPAutoConnect.exe -v
VCServerAPI::CheckForClientPlugin(): Connected to client XXXXXXXXXX
VCServerAPI::Init(): Protocol = PCoIP
ThinPrint AutoConnect component, Copyright (c) 1999-2012 Cortado AG, 8.8.745.2

Virtual channel initialized.
Try .print Client on XXXXXXXXX:4000.
Try .print Client on xxx.xxx.xxx.xxx:4000.
No suitable client protocol found.
No printers to be created in this session were found.
Exiting with code ... (224)
VCServerAPI::Exit(): Protocol = NONE

The vmware-mksvchanserver log in the virtual desktop shows a pcoip_vchan_open error: -503

2016-08-11 09:56:24.585 [0C70] ## Starting MKSVchan Server logging.


2016-08-11 09:56:24.585 [0C70] wWinMain: Loading pcoip_vchan.dll.


2016-08-11 09:56:24.601 [0C70] wWinMain: Finished loading pcoip_vchan.dll.


2016-08-11 09:56:24.601 [0C70] wWinMain: Calling pcoip_vchan_plugin_app_init.


2016-08-11 09:56:24.726 [0C70] wWinMain: pcoip_vchan_plugin_app_init finished.


2016-08-11 09:56:24.726 [0C70] MKSVchanWin32_ReadRegistryDWORD: Registry key HKLM\Software\Policies\Teradici\PCoIP\pcoip_admin not found.


2016-08-11 09:56:24.726 [0C70] MKSVchanWin32_ReadRegistryDWORD: Registry key HKLM\Software\Policies\Teradici\PCoIP\pcoip_admin_defaults not found.


2016-08-11 09:56:24.726 [0C70] MKSVchanWin32_ReadRegistryDWORD: Registry key HKLM\Software\Policies\Teradici\PCoIP\pcoip_admin not found.


2016-08-11 09:56:24.726 [0C70] MKSVchanWin32_ReadRegistryDWORD: Registry key HKLM\Software\Policies\Teradici\PCoIP\pcoip_admin_defaults not found.


2016-08-11 09:56:24.726 [0C70] Registering connect callback function


2016-08-11 09:56:24.741 [0C70] We are already connected, so check the channel state now.


2016-08-11 09:56:24.741 [0C70] mksvchanplugin CONNECTED.


2016-08-11 09:56:24.741 [0C70] MKSVchanPluginHandleConnect: Opening new channel with capability 0x04000001.


2016-08-11 09:56:24.741 [0CAC] MKSVchanWin32_ReadRegistryString: Registry key Software\VMware, Inc.\VMware VDM not found.


2016-08-11 09:56:24.741 [0C70] pcoip_vchan_open succeeded.


2016-08-11 09:56:24.741 [0C70] MKSVchanPluginHandleConnect: Legacy virtual channel state is 1 and capabilities are 0x00000000.


2016-08-11 09:56:24.741 [0C70] MKSVchanPluginHandleConnect: Other side has legacy virtual channel open. Opening now.


2016-08-11 09:56:24.757 [0C70] pcoip_vchan_open error: -503


2016-08-11 09:56:24.757 [0C70] FindProcess: Successfully opened process handle.


2016-08-11 09:56:24.757 [0CAC] MKSVchanPlugin_HandleRecvRdy: Channel is not active.


2016-08-11 09:56:24.757 [0CAC] MKSVchanPlugin_HandleRecvRdy: Channel is not active.


2016-08-11 09:56:24.772 [0C80] MKSVchanPluginHandleOpened: New channel opened with capability 0x04000001.


2016-08-11 09:56:24.772 [0C80] MKSVchanPluginHandleOpened: MKSVchanPlugin is active. Negotiated capability is 0x04000001


2016-08-11 09:56:24.772 [0C80] MKSVchanPluginHandleOpened: Queueing vchan RECV_RDY that we may have missed.


2016-08-11 09:56:24.772 [0CAC] MKSVchanPlugin_HandleRecvRdy: Allocating 869 bytes for the clipboard payload


2016-08-11 09:56:24.772 [0CAC] MKSVchanPlugin_HandleRecvRdy: Retrieving 868-byte payload took 0 seconds


2016-08-11 09:56:24.772 [0CAC] MKSVchan_SetClipboard: Text data size 828.


2016-08-11 09:56:24.772 [0CAC] MKSVchanPlugin_HandleRecvRdy: Setting clipboard took 0 seconds


2016-08-11 09:56:27.315 [0CAC] MKSVchanPlugin_HandleRecvRdy: Allocating 139 bytes for the clipboard payload


2016-08-11 09:56:27.315 [0CAC] MKSVchanPlugin_HandleRecvRdy: Retrieving 138-byte payload took 0 seconds


2016-08-11 09:56:27.315 [0CAC] MKSVchan_SetClipboard: Text data size 98.


2016-08-11 09:56:27.315 [0CAC] MKSVchanPlugin_HandleRecvRdy: Setting clipboard took 0 seconds


2016-08-11 09:56:28.096 [0CAC] MKSVchanPlugin_HandleRecvRdy: Sending the clipboard is disabled by policy. Ignoring clipboard request.

Does anyone have an idea on how to fix this?

0 Kudos
0 Replies