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?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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.

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,
tabushAuthor Commented:
Thanks ill give this a try and let you know.
We're using the View Client (PCoIP).
tabushAuthor Commented:
This GP didnt fix it.
pcoip_server process doesnt launch. Must be that this "force shutdown" screen is preventing it from launching.
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

you mean its not started?
it will lunch on boot - otherwise the user would never be able to connect
tabushAuthor Commented:
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

can you post the debug and pcoip log when one of the users tries to connect and fails?
tabushAuthor Commented:
We ended up changing the process for our weekly reboot so it wont get stuck on this window. Rather than executing the reboot as a scheduled task we do it using a batch file which forces the reboot.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
tabushAuthor Commented:
I found a workaround because we couldnt find a good solution.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.