Search the VMware Knowledge Base (KB)
View by Article ID

Connecting to a VDI desktop with PCoIP displays a black screen and disconnects after 10 seconds (1016633)

  • 34 Ratings

Symptoms

When connecting to a VDI desktop (both linked and full clones) using PCoIP, you experience these symptoms:
  • The desktop display is black.
  • The session disconnects within 10 seconds.
Note: This issue does not occur when connecting to the desktop using Remote Desktop Protocol (RDP).

Resolution

This issue can occur if:
  • The template that is used to deploy the virtual machine is set to an unsupported resolution of the Physical Monitor.

    To resolve this issue, change the display on the parent virtual machine to a resolution that is supported by the physical client computer.
  • The Connect using DNS Name Group Policy Object (GPO) becomes corrupt.

    To replace the Connect using DNS Name GPO:
    1. In vCenter Server, power on the parent virtual machine, ensuring that no other users are accessing any desktops in the pool.
    2. Edit the GPO using the Group Policy editor:
      1. In a command prompt on the parent virtual machine, launch the Group Policy editor with the command:

        gpedit.msc

      2. Copy the view agent group policies from Connection Server ( C:\Program Files\VMware\VMware View\Server\Extras\GroupPolicyFiles\vdm_agent.adm) to the parent virtual machine's desktop.
      3. Click Computer Configuration, then right-click Administrative Templates.
      4. Click Add / Remove Templates and import vdm_agent.adm from the desktop.
      5. Click VMware View Agent Configuration > Agent Configuration.
      6. Right-click CONNECT USING DNS NAME > Properties and select Disabled.
      7. Restart the parent virtual machine.
      8. Power off the virtual machine and create a new snapshot.

    3. In a web browser, log in to the Connection Server Admin page by entering the URL, https://<IP>/admin.
    4. Select the pool where the virtual machine's base snapshot resides.
    5. In the Summary tab, click Edit Image.
    6. Click Recompose, then click Next.
    7. Select all of the virtual machines you want to recompose with this new snapshot and click Next.
    8. Select the parent virtual machine which has the GPO disabled, so that the GPO can be pushed to all of its linked clones and click Next.
    9. Select the new base snapshot for the recomposed linked clones.

  • The video RAM (VRAM) configured for the virtual machine is insufficient to display the desktop at the resolution of the displays.

    In this case, in the PCoIP Server logs in the View desktop, you see entries similar to:

    LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapWDDMFlipKTRender: screen dma failed
    LVL:0 RC: 0 IMG_FRONTEND :flip_frame_buffer: Unknown flip error for display 0 [0, 1006]
    LVL:0 RC:-500 IMG_FRONTEND :open_displays(): Flip error in open display first flip.
    LVL:0 RC:-500 MGMT_IMG :cSW_HOST_IPC::enable_frontend failed. 2 retries remaing. Trying again...
    LVL:0 RC: 0 IMG_FRONTEND :Calling open display in Tera1 mode.
    LVL:2 RC: 0 MGMT_SSIG :Session closed locally (IP_Address, MAC_Address, PRI: 0)
    LVL:2 RC: 0 MGMT_SSIG :Sending to peer: BYE disconnect reason cause (0xfffffe0c)
Note: For more information on log locations, see Location of VMware View log files (1027744)
 

See Also

Update History

07/22/2010 - Added information about unsupported resolutions. 11/10/2011 - Added the cause related to insufficient VRAM 10/22/2012 - Added reference to KB 1027744

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 34 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 34 Ratings
Actions
KB: