The PCoIP session ended abruptly and the PCoIP Zero Client PCoIP Splash screen appears

Problem

Occasionally issues can cause the PCoIP Zero Client to reboot. Issues such as the ones listed below are good signs that the PCoIP Zero Client has rebooted even though at first it may not be certain the PCoIP Zero Client rebooted.

• Unexpectedly the screen goes black briefly and the PCoIP logo splash screen appears before the logon screen appears.
• Shortly after plugging in a USB device the screen goes black briefly and the PCoIP logo splash screen appears the logon screen appears.

Resolution

To confirm the PCoIP Zero Client has performed an unexpected reboot you can do two things.

1. Perform the same actions which caused the issue to bring you to the logon screen and while doing so observe the status lights on the PCoIP Zero Client. If they briefly go off and on, then the PCoIP Zero Client has performed a reboot
2. You can also investigate the log file in the PCoIP Zero Client and look for lines similar to the following. ()

 LVL:2 RC:   0        MGMT_SYS :Teradici Corporation (c)2007-2012
 LVL:2 RC:   0        MGMT_SYS :Bootloader Version: 2.2.0
 LVL:2 RC:   0        MGMT_SYS :Bootloader Build ID: v327 
 LVL:2 RC:   0        MGMT_SYS :Bootloader Build date: Apr  6 2011 19:28:23
 LVL:1 RC:   0        MGMT_SYS :*** CRITICAL ERROR CONTEXT DUMP ***
 LVL:1 RC:   0        MGMT_SYS :Reset cause: ROM EXC GENERAL
 LVL:2 RC:   0        MGMT_SYS :Previous Bootloader Build ID: v327 , Version: 2.2.0
 LVL:2 RC:   0        MGMT_SYS :Previous Firmware Build ID: rc_tera1_r3_5@12092, Version: 3.5.1

The boot sequence begins with similar entries seen above (can be slightly different for different firmware releases). In this case the CRITICAL ERROR CONTEXT DUMP message means that the PCoIP Zero Client crashed and rebooted and tech support needs to be contacted.

In either case obtain the PCoIP Zero Client logs and provide them to HP Anyware tech support for further analysis.