Link to home
Start Free TrialLog in
Avatar of tabush
tabush

asked on

Horizon View "The display protocol for the desktop is currently not available" (ET)

Noticed this issue a few times lately where a user cannot connect to their desktop and it is giving this error "The display protocol for the desktop is currently not available." When i console into the desktop is see its on this screen (screenshot below). The previous day they must have tried shutting down/restarting and had programs open so it go hung up waiting to close. Not sure why this should be preventing user from logging in and clicking cancel or force shutdown though.
Anyone know of a solution?
CaptureB.PNG
Avatar of nbeutler
nbeutler
Flag of Germany image

So first at all it might be that the view agent gets shut downed already in the process which makes the PCOIP protocol unavailable. Are they using RDP or the View Client?

I would suggest following to get rid of this windows feature by using (local) GPO.

SOLUTION:
1. Press "Window +R" keys to start "Run" dialogue box and type "gpedit.msc" in the dialogue box.

2. Click "OK", "Local Group Policy Editor" window will pop up.

3. Navigate to "Computer Configuration" --> "Administrative Templates" --> "System" --> "Shutdown Options". Double-click "Turn off automatic termination of applications that block or cancel shutdown" on the right panel. In the new dialogue box popped up, set configuration option as "Enabled".

4. Next time when you shut down your machine, the machine will be shut down directly without prompt.

---

To be honest this is a workaround but it might be worth to check if the pcoip_server process still runs at the time you login via console to check the machine. It most likely is not.


best regards,
Niko
Avatar of tabush
tabush

ASKER

Thanks ill give this a try and let you know.
We're using the View Client (PCoIP).
Avatar of tabush

ASKER

This GP didnt fix it.
pcoip_server process doesnt launch. Must be that this "force shutdown" screen is preventing it from launching.
you mean its not started?
it will lunch on boot - otherwise the user would never be able to connect
Avatar of tabush

ASKER

pcoip_server process only starts when the user connects. First image is console into the computer before user us connected. Seconds is after he's connected

User generated image
User generated image
can you post the debug and pcoip log when one of the users tries to connect and fails?
ASKER CERTIFIED SOLUTION
Avatar of tabush
tabush

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of tabush

ASKER

I found a workaround because we couldnt find a good solution.