RDS Cluster - Intermittent "No available computers in the pool"

%3CLINGO-SUB%20id%3D%22lingo-sub-1785570%22%20slang%3D%22en-US%22%3ERDS%20Cluster%20-%20Intermittent%20%22No%20available%20computers%20in%20the%20pool%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1785570%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20deployed%20a%20second%20RDS%20cluster%20and%20are%20in%20the%20process%20of%20migrating%20the%20VMs%20from%20the%20old%20WinServer%202016%20based%20cluster%20to%20the%20new%202019%20based%20cluster.%20Occasionally%20we%20see%20the%20error%20%22There%20are%20no%20available%20computers%20in%20the%20pool.%20Try%20connecting%20again%20or%20contact%20your%20network%20administrator.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMost%20of%20the%20time%20they%20can%20successfully%20reconnect%20after%20another%20attempt%20or%20two.%20Occasionally%20they%20have%20to%20wait%20a%20few%20minutes%20but%20can%20generally%20reconnect%20after%20some%20time.%20The%20old%20cluster%20does%20not%20exhibit%20this%20behavior%20and%20I%20cannot%20find%20good%20resources%20on%20what%20to%20investigate%20to%20alleviate%20this%20problem.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESuggestions%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1785570%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActive%20Directory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EClustering%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHyper-V%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ENetworking%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
New Contributor

We have deployed a second RDS cluster and are in the process of migrating the VMs from the old WinServer 2016 based cluster to the new 2019 based cluster. Occasionally we see the error "There are no available computers in the pool. Try connecting again or contact your network administrator."

 

Most of the time they can successfully reconnect after another attempt or two. Occasionally they have to wait a few minutes but can generally reconnect after some time. The old cluster does not exhibit this behavior and I cannot find good resources on what to investigate to alleviate this problem.

 

Suggestions?

0 Replies