No resources in WVD pool

Jesse Marano 121 Reputation points

We have 5 WVD pools. Recently one pool is giving a "no resources available" error when trying to connect through the WVD portal (, for every user that tried. Investigating I saw that there were sessions on the host that was powered on and it was enabled for new sessions. Powering on a second host allowed new connections again (but only to the newly powered on host). I tried restarting services, but that didn't change the issue. Disabling and then enabling new sessions (via powershell) seems to have fixed the issue, but I'm not sure for how long.

Every other pool has seen no issues. This pool has been in place for 9 months, and the sessions hosts have been up for about 1 week with no issues until last weekend.

I pulled the diagnostics, but they don't seem helpful.

ActivityId : 30a4a7cc-d3e7-426b-9919-673904370000
ActivityType : Connection
StartTime : 1/13/2021 11:01:42 AM
EndTime : 1/13/2021 11:08:52 AM
UserName :
RoleInstances :
Outcome : Failure
Status : Completed
Details : {[ClientOS, Windows 10 Edge 87.0.664.75], [ClientVersion,], [ClientType, HTML], [PredecessorConnectionId, ]...}
LastHeartbeatTime : 1/13/2021 11:08:52 AM
Checkpoints : {TransportConnecting, TransportConnected, OnClientDisconnected, LoadBalancedNewConnection}
Errors : {Microsoft.RDInfra.Diagnostics.Common.DiagnosticsErrorInfo, Microsoft.RDInfra.Diagnostics.Common.DiagnosticsErrorInfo}

Any suggestions on next steps for troubleshooting? I would like to find the root cause so this is no longer a random issue.


Azure Virtual Desktop
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,387 questions
0 comments No comments
{count} votes

Accepted answer
  1. TravisCragg-MSFT 5,681 Reputation points Microsoft Employee

    @Jesse Marano Unfortunately there is not a way to get decent diagnostics on exactly what went wrong, and this error can occur for many reasons. Typically this error is due to permissions, but I do not believe this to be the case with your issue. You also have a recent VM heartbeat, so it is unlikely to be an agent / VM issue.

    If you want to pursue an RCA, your best bet will be to go through Azure Support. If you do not have a support plan and want to work with support, please let me know!

0 additional answers

Sort by: Most helpful