Windows Server 2016 - Can't RDP with one specific user

Question

This is a new Windows 2016 server. We have three users on it and two of them are able to login without issue. The third one, no matter what we've tried (except rebooting; trying to avoid that) is not able to login. He keeps getting this error:

The task you are trying to do can't be completed because Remote Desktop Services is currently busy

I tried rwinsta to reset the session, resetting the user's password, running shutdown /l from a command prompt running under his credentials. Nothing worked. Any ideas?

UPDATE Tried everything I knew to try. Nothing worked. Had to buckle down and reboot.

Solution 1

What worked for me finally was to logon as a different admin user and start Task Manager, switch to the Users tab, right-click the problem user and select "Connect".

Solution 2

Just had the same issue. Interesting that it was only me. Here's my fix. Since the message said RDP service is busy. But there were no sessions open. I went backdoor into the server via "Computer Management" and restarted the RDP service. Worked like a charm!!!

Solution 3

I had this exact problem. When I got in with the one account that could connect, I found in the Users tab of Task Manager that there were four sessions with null usernames. When I ended the Windows Login Application task for each, the null entries disappeared and I was able to log in via RDS normally. It did not require a restart.

Comments

[Admin]

Is each user initiating the RDP from a different workstation? What is different about each workstation? What happens if problem user starts RDP from workstation of a working user? See this

[Admin]

Possible licensing limitation? Can he login while you both are logged out?

[Admin]

Definitely not licensing. Even if we are all logged out, he gets the same error.

[Admin]

Happens on a Win10 Pro machine too - can't even log in through local console anymore on that user. I'm so glad Windows is now stable and Enterprise grade and you don't have to reboot anymore to fix problems.

[Admin]

for me , i just restarted the remote desktop services and its works fine after restarting the service. :)

[serverstackqns]

Thank you, this step solved my issue.

[Sohail Ahmed]

I tested this trick on a working VM before applying it on an affected production VM but the RDP service hanged while stopping. I had to connect using VNC and restart it.