The VMware Horizon View PCoIP server logs show "IPC Can't encode. Waiting. queue" after a random disconnect.

Rate this Article
Average: 1 (1 vote)

August 2, 2018

Last modified: 09/03/2023, 6:12 pm

Knowledge Base Article Troubleshooting Performance Session Third Party Enhancements Zero Clients

Problem

The VMware Horizon View Client or PCoIP Zero Client experience a random disconnect from the VMware Horizon View session. Inspection of the PCoIP server logs show a high slice rate count after a random disconnect.

The following example shows 192 outstanding slices that the pcoip server has sent but has yet to receive a response from the client for:

2011/03/10 12:30:16.567 2 0 IPC  Can't encode. Waiting. queue   0 q_limit  24 s_out 192 max_s_out 192 rate_ctrl 1

Based on the server sending out PCoIP data (slices in UDP datagrams) and not receiving a response from the client, it is assumed that the server side is functioning correctly (unless the ESX host is not delivering the incoming packets past the vswitch).

 

Cause

The following are the possible causes which should be looked into:

  • Client has stopped responding due to software issues, anti-virus, network access security, IDS or IPS (does not apply to PCoIP zero clients)
  • High packet loss or packets being dropped between client and server
  • Defective hardware, edge\floor\datacenter switches, or network jacks
  • QOS is not configured properly - PCoIP traffic is not set to the correct QOS level and is being dropped due to congestion relief methods
  • QOS is not configured correctly - PCoIP is not being QOS'd at all and other traffic is affecting PCoIP