Azure WVD Users Trying to Connect Session says "No Resources available resources" Error

Question

We have a Host Pool with 15 Hosts, where we have several Users having active sessions during the business hours. We have some Users having Issues with Error saying " we couldn't connect because there are currently no available resources...." attached the snip of the Error. We tried to clear browser cache.cookies data and also reset on the remote desktop App still see the same Error. Monitored the usage of the Hosts it is been minimal. How can we know which hosts these specific set of Users are trying to connect and if that specific Host users are having Issues. Not Sure if this is an Issue on the User Side Computer or anything to do with the Pool Hosts However we have other active sessions going on fine. If this is a known behavior Please let us know what is the resolution.

Answer 1

@Jaganljpmail
Apologies for the delay. The cause of it is usually lacking WVD, which means the session meets the max limitation.

FAQ 1: Is there any method to check the records of session usage ?
Yes the Azure Portal's WVD page can display the current sessions:

FAQ 2: Is 'idle/ disconnect' being counted in the 'MaxSessionLimit' being configured in the wvd host pool ?

Yes all active, disconnected, idled sessions will be counted into the sessions. (Idled session is one kind of active sessions. Being idle for too long may get the session disconnected.)

Only the user sessions which were "logged off" will not be taking the session counts.

So please make sure all the active and disconnected sessions are below the max limitation. Otherwise the users will get the mentioned error when trying to connect to WVD.

Hope that helps.

----------

Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer.

Answer 2

**Please run below command msrdcw.exe /reset and restart the vm and go to your host pool properties and increase max pool quota
and alternatively you can user RDP license in group policy for each VM **