Forum Discussion
The task you are trying to do can’t be completed because Remote Desktop Services is currently busy
We have a WVD deployment and we have faced some issues with WVD, here you have the list of our current pain points:
- Users are getting this error messages while trying to access WVD through the Remote Desktop App or through the Web
- The error message: “The task you are trying to do can’t be completed because Remote Desktop Services is currently busy” while connecting to the WVD pool”
- The error message: “Oops, we couldn’t connect to “MyPC-E3” we could not connect to the gateway because of an error” while connecting to the WVD pool”
- The error message: “We couldn’t connect to the Remote Desktop Gateway because of an orchestration error”
To add a little bit more on this, we have found that every time that the users are getting these errors, some of the WVD hosts in an RDP session with the local administrator account are showing a black screen and the only way to fix it is by restarting the PC.
Our current WVD host pool has 8 PCs, 4 are Windows 10 Enterprise version 1809 and 4 are Windows 10 Enterprise version 1903.
Feel free to ask any minor details that could be relevant for a solution.
Daghoberto:Thank you for reaching out for those issues. I recommend to file a support request as those issues might have different root causes. Additional logs will help to pin down those issues.
- evasse
Microsoft
Daghoberto:Thank you for reaching out for those issues. I recommend to file a support request as those issues might have different root causes. Additional logs will help to pin down those issues.
What was the fix in your case? I have a different setup but I'm also receiving the same message periodically.
Chris Parker Yes, I was able to fix it by having a different svchost.exe process for each process.
The problem is bisrv (BrokerInfrastructure) is receiving a large number of events using threadpool threads and then it is sending a ALPC request (which again uses thread pool threads) to SystemEventBroker Service which is running in same SVCHost. This caused thread pool exhaustion. Since thread pool threads are exhausted, we can no longer process requests resulting in hang.
We do have a workaround for the issue, run SystemEventsBroker or BrokerInfrastructure service into its own host process.
Action Plan: Perform following on all WVD computers
- RDP into the computer with admin account -> Start Regedit
- Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SystemEventsBroker\ and change the value of the key “Type” to 16 (decimal) (or 0x10 hex)
- Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BrokerInfrastructure\ and change the value of the key “Type” to 16 (decimal) (or 0x10 hex)
- Reboot the machine
- Log into the VM again -> open command prompt as administrator and enter command tasklist /svc > c:\tasklist.txt
- Open tasklist.txt and verify SystemEventsBroker or BrokerInfrastructure are in own svchost
7. Monitor and let me know if the issue resurfaces
Daghoberto Much appreciated!
