I have a VMWare View environment which mixes hardware and software PCoIP clients, as well as hardware and software PCoIP hosts. Don't ask me why. This is mostly working fine, except for an intermittent error that I hit when trying to connect from a software client onto a hardware host. About 50% of the time this works fine, for the other 50% the client raises the classic error: "the selected display protocol is currently unavailable". A quick dig in the Agent log shows this output for the failures:
09/20/2012, 11:12:21.457> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: For Hard Host: Using Version 1 Tag
09/20/2012, 11:12:21.457> LVL:2 RC: 0 PRI :pcoip_agent_connect_req: Session ID Tag for Hard Host: zKjitIJHL9NQ
09/20/2012, 11:12:21.457> LVL:2 RC: 0 AGENT :server_listen_on_addr is X.X.X.X (host order)
09/20/2012, 11:12:21.457> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: Session ID = 11
09/20/2012, 11:12:21.457> LVL:2 RC: 0 AGENT :codec = 0.
09/20/2012, 11:12:21.457> LVL:2 RC: 0 AGENT :PCOIP_AGENT_CODEC_HW_TERA1 - selected.
09/20/2012, 11:12:21.457> LVL:2 RC: 0 AGENT :PCOIP_AGENT_CODEC_HW_TERA1 - checking for card ready.
09/20/2012, 11:12:21.457> LVL:2 RC: 0 AGENT :PCOIP_AGENT_CODEC_HW_TERA1 - getting MAC.
09/20/2012, 11:12:21.472> LVL:2 RC: 0 AGENT :ipv4_cfg_get returned ipaddr=Y.Y.Y.Y.
09/20/2012, 11:12:21.488> LVL:2 RC: 0 AGENT :conn_port_get returned port='<port>'.
09/20/2012, 11:12:21.488> LVL:2 RC: 0 AGENT :setting response ipaddr to YHex.
09/20/2012, 11:12:22.488> LVL:1 RC: 0 AGENT : cTERA_DEV::synch_ioctl: synch ioctl timed out
09/20/2012, 11:12:22.504> LVL:1 RC: 0 AGENT : cTERA_PCOIP_LINK::sess_tag_set: TERA_PCOIP_HCC_IOCTL_HMI_VAR_SET ioctl failed -504
09/20/2012, 11:12:22.504> LVL:1 RC:-504 AGENT :tera_agent_remove_tera1_tag: sess_tag_set failed.
09/20/2012, 11:12:23.504> LVL:1 RC: 0 AGENT : cTERA_DEV::synch_ioctl: synch ioctl timed out
09/20/2012, 11:12:23.519> LVL:1 RC: 0 AGENT : cTERA_PCOIP_LINK::sess_tag_set: TERA_PCOIP_HCC_IOCTL_HMI_VAR_SET ioctl failed -504
09/20/2012, 11:12:23.519> LVL:1 RC:-504 AGENT :sess_tag_set failed.
09/20/2012, 11:12:23.519> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req (end): connection_response, 2
A quick google has suggested that other people have had similar issues when particular security applications have locked down resources that the view agent needed to access. This seems a quite likely cause in my environment, but I'm not using any of the specific applications that I've seen listed as causing issues. What would be great is if I could find out what resource the agent is failing to gain access to so that I can grant this permission. I haven't seen anything relevant in the windows event logs.
In general, having had the failure, restarting the agent gives me another ~50% chance of a successful connection so continued restarts do eventually give me a working connection.
If anybody can clarify this behaviour I will be eternally grateful. Or grateful for a few weeks at least.
Versions:
View 5.1.1
Windows XP
ESXi 5.0
TERA1, firmware 3.4.0