Home

We could't connect because there are currently no available resources. Try again later or...

%3CLINGO-SUB%20id%3D%22lingo-sub-800196%22%20slang%3D%22en-US%22%3EWe%20could't%20connect%20because%20there%20are%20currently%20no%20available%20resources.%20Try%20again%20later%20or...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-800196%22%20slang%3D%22en-US%22%3E%3CP%3ESince%20this%20morning%20we%20receive%20this%20error%20when%20we%20try%20to%20connect%20to%20our%20application%20through%20the%20Remote%20Desktop%20Application%3A%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20could't%20connect%20because%20there%20are%20currently%20no%20available%20resources.%20Try%20again%20later%20or%20contact%20technical%20support.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20this%20is%20the%20error%20retrieved%20with%20powershell%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EErrorSource%20%3A%20RDBroker%3CBR%20%2F%3EErrorOperation%20%3A%20OrchestrateSessionHost%3CBR%20%2F%3EErrorCode%20%3A%20-2146233088%3CBR%20%2F%3EErrorCodeSymbolic%20%3A%20ConnectionFailedRDAgentBrokerConnectionNotFound%3CBR%20%2F%3EErrorMessage%20%3A%20RD%20Agent%20from%20host%200929c773-0c0a-4e02-9ac3-7fd74f6ac183%20is%20not%20connected%20to%20the%20Broker%20instance%20is%20associated%20with%20during%20orchestration%3CBR%20%2F%3Erequest.%3CBR%20%2F%3EErrorInternal%20%3A%20False%3CBR%20%2F%3EReportedBy%20%3A%20RDGateway%3CBR%20%2F%3ETime%20%3A%208%2F12%2F2019%206%3A54%3A35%20AM%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20also%20tried%20to%20recreate%20the%20app%20group%20without%20success.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-802317%22%20slang%3D%22en-US%22%3ERe%3A%20We%20could't%20connect%20because%20there%20are%20currently%20no%20available%20resources.%20Try%20again%20later%20or...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-802317%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F390975%22%20target%3D%22_blank%22%3E%40LucaBerniniKT%3C%2FA%3E%26nbsp%3BI%20have%20similar%20problem%20and%20I%20can%20see%20the%20the%20agent%20on%20the%20session%20host%20is%20not%20posting%20heartbeats%20properly%20to%20WVD%20they%20way%20it%20used%20to.%20Did%20you%20resolve%20your%20problem%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-802338%22%20slang%3D%22en-US%22%3ERe%3A%20We%20could't%20connect%20because%20there%20are%20currently%20no%20available%20resources.%20Try%20again%20later%20or...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-802338%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F390975%22%20target%3D%22_blank%22%3E%40LucaBerniniKT%3C%2FA%3E%26nbsp%3BSame%20problem%20in%20our%20environment.%20Yesterday%20we%20were%20using%20it%2C%20and%20this%20morning%20we%20are%20getting%20this%20error.%20Nothing%20has%20changed%20in%20between.%20Something%20down%20on%20Microsoft's%20end%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-802355%22%20slang%3D%22en-US%22%3ERe%3A%20We%20could't%20connect%20because%20there%20are%20currently%20no%20available%20resources.%20Try%20again%20later%20or...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-802355%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309051%22%20target%3D%22_blank%22%3E%40Johan_Eriksson%3C%2FA%3EUnfortunately%20not%20yet.%20We%20will%20try%20to%20delete%20and%20recreate%20the%20resources.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-802823%22%20slang%3D%22en-US%22%3ERe%3A%20We%20could't%20connect%20because%20there%20are%20currently%20no%20available%20resources.%20Try%20again%20later%20or...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-802823%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F390975%22%20target%3D%22_blank%22%3E%40LucaBerniniKT%3C%2FA%3E%26nbsp%3BSolved%20the%20issue%20on%20my%20end!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20checked%20the%20status%20of%20session%20hosts%20in%20my%20environment%2C%20and%20noticed%20something%20odd.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPS%20C%3A%5CWINDOWS%5Csystem32%26gt%3B%20Get-RdsSessionHost%20-TenantName%20contoso.ca%20-HostPoolName%20contosoWVD%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ESessionHostName%20%3A%20contosoWVD-0.contoso.ca%3CBR%20%2F%3ETenantName%20%3A%20contoso.ca%3CBR%20%2F%3ETenantGroupName%20%3A%20Default%20Tenant%20Group%3CBR%20%2F%3EHostPoolName%20%3A%20contosoWVD%3CBR%20%2F%3EAllowNewSession%20%3A%20True%3CBR%20%2F%3ESessions%20%3A%200%3CBR%20%2F%3ELastHeartBeat%20%3A%207%2F3%2F2019%208%3A41%3A18%20PM%3CBR%20%2F%3EAgentVersion%20%3A%201.0.833.5%3CBR%20%2F%3EAssignedUser%20%3A%3CBR%20%2F%3EOsVersion%20%3A%2010.0.17763%3CBR%20%2F%3ESxSStackVersion%20%3A%20rdp-sxs190429002%3CBR%20%2F%3EStatus%20%3A%20Available%3CBR%20%2F%3EUpdateState%20%3A%20Succeeded%3CBR%20%2F%3ELastUpdateTime%20%3A%207%2F3%2F2019%208%3A38%3A18%20PM%3CBR%20%2F%3EUpdateErrorMessage%20%3A%3C%2FP%3E%3CP%3ESessionHostName%20%3A%20contosoWVD01-0.contoso.local%3CBR%20%2F%3ETenantName%20%3A%20contoso.ca%3CBR%20%2F%3ETenantGroupName%20%3A%20Default%20Tenant%20Group%3CBR%20%2F%3EHostPoolName%20%3A%20contosoWVD%3CBR%20%2F%3EAllowNewSession%20%3A%20True%3CBR%20%2F%3ESessions%20%3A%201%3CBR%20%2F%3ELastHeartBeat%20%3A%208%2F13%2F2019%2012%3A37%3A59%20PM%3CBR%20%2F%3EAgentVersion%20%3A%201.0.1006.2006%3CBR%20%2F%3EAssignedUser%20%3A%3CBR%20%2F%3EOsVersion%20%3A%2010.0.17763%3CBR%20%2F%3ESxSStackVersion%20%3A%20rdp-sxs190614002%3CBR%20%2F%3EStatus%20%3A%20Available%3CBR%20%2F%3EUpdateState%20%3A%20Succeeded%3CBR%20%2F%3ELastUpdateTime%20%3A%208%2F6%2F2019%208%3A08%3A11%20PM%3CBR%20%2F%3EUpdateErrorMessage%20%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20environment%20only%20has%20one%20session%20host.%20The%20other%20host%20%22contosoWVD-0.contoso.ca%22%20was%20probably%20one%20of%20our%20testing%20iterations%20early%20on.%20The%20strange%20part%20is%20that%20it%20was%20marked%20as%20%22Available%22%20even%20though%20it%20doesn't%20exist%20and%20last%20heartbeat%20was%207%2F3%2F2019.%20This%20must%20be%20a%20new%20bug%20starting%20a%20few%20hours%20ago.%20After%20removing%20the%20defunct%20host%2C%20it%20worked%20again.%20Traffic%20must%20have%20been%20routing%20to%20the%20old%20host%20in%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20that%20saves%20someone%20the%20hours%20I%20spent%20on%20it%20this%20morning.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-803727%22%20slang%3D%22en-US%22%3ERe%3A%20We%20could't%20connect%20because%20there%20are%20currently%20no%20available%20resources.%20Try%20again%20later%20or...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-803727%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F390975%22%20target%3D%22_blank%22%3E%40LucaBerniniKT%3C%2FA%3E%26nbsp%3BBorked%20on%20us%20too%20after%20Windows%20Updates%20were%20installed%20this%20afternoon.%20Get-RdsSessionHost%20indicates%20the%20last%20heartbeat%20was%20received%20right%20before%20the%20VM%20was%20rebooted%20to%20install%20updates.%20KB4512508%20is%20the%20culprit%20-%20I%20uninstalled%20it%20but%20the%20agent%20was%20still%20messed%20up.%20Dropped%20the%20Session%20Host%20from%20the%20host%20pool%2C%20uninstalled%20all%20the%20Remote%20Desktop%20agent%20stuff%2C%20followed%20the%20instructions%20for%20registering%20a%20session%20host%20to%20an%20existing%20pool%20via%20powershell%2C%20and%20got%20it%20working%20again%20after%20a%20reboot.%20Going%20to%20pause%20updates%20for%20a%20bit%20until%20a%20new%20agent%20comes%20out.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1018408%22%20slang%3D%22en-US%22%3ERe%3A%20We%20could't%20connect%20because%20there%20are%20currently%20no%20available%20resources.%20Try%20again%20later%20or...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1018408%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F391446%22%20target%3D%22_blank%22%3E%40AS_Streamline%3C%2FA%3E%26nbsp%3B%20I%20am%20having%20the%26nbsp%3B%20same%20problem.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
LucaBerniniKT
New Contributor

Since this morning we receive this error when we try to connect to our application through the Remote Desktop Application: 

We could't connect because there are currently no available resources. Try again later or contact technical support.

 

And this is the error retrieved with powershell:

 

ErrorSource : RDBroker
ErrorOperation : OrchestrateSessionHost
ErrorCode : -2146233088
ErrorCodeSymbolic : ConnectionFailedRDAgentBrokerConnectionNotFound
ErrorMessage : RD Agent from host 0929c773-0c0a-4e02-9ac3-7fd74f6ac183 is not connected to the Broker instance is associated with during orchestration
request.
ErrorInternal : False
ReportedBy : RDGateway
Time : 8/12/2019 6:54:35 AM

 

We also tried to recreate the app group without success.

6 Replies

@LucaBerniniKT I have similar problem and I can see the the agent on the session host is not posting heartbeats properly to WVD they way it used to. Did you resolve your problem? 

@LucaBerniniKT Same problem in our environment. Yesterday we were using it, and this morning we are getting this error. Nothing has changed in between. Something down on Microsoft's end?

@Johan_ErikssonUnfortunately not yet. We will try to delete and recreate the resources. 

@LucaBerniniKT Solved the issue on my end!

 

I checked the status of session hosts in my environment, and noticed something odd.

 

PS C:\WINDOWS\system32> Get-RdsSessionHost -TenantName contoso.ca -HostPoolName contosoWVD


SessionHostName : contosoWVD-0.contoso.ca
TenantName : contoso.ca
TenantGroupName : Default Tenant Group
HostPoolName : contosoWVD
AllowNewSession : True
Sessions : 0
LastHeartBeat : 7/3/2019 8:41:18 PM
AgentVersion : 1.0.833.5
AssignedUser :
OsVersion : 10.0.17763
SxSStackVersion : rdp-sxs190429002
Status : Available
UpdateState : Succeeded
LastUpdateTime : 7/3/2019 8:38:18 PM
UpdateErrorMessage :

SessionHostName : contosoWVD01-0.contoso.local
TenantName : contoso.ca
TenantGroupName : Default Tenant Group
HostPoolName : contosoWVD
AllowNewSession : True
Sessions : 1
LastHeartBeat : 8/13/2019 12:37:59 PM
AgentVersion : 1.0.1006.2006
AssignedUser :
OsVersion : 10.0.17763
SxSStackVersion : rdp-sxs190614002
Status : Available
UpdateState : Succeeded
LastUpdateTime : 8/6/2019 8:08:11 PM
UpdateErrorMessage :

 

Our environment only has one session host. The other host "contosoWVD-0.contoso.ca" was probably one of our testing iterations early on. The strange part is that it was marked as "Available" even though it doesn't exist and last heartbeat was 7/3/2019. This must be a new bug starting a few hours ago. After removing the defunct host, it worked again. Traffic must have been routing to the old host in error.

 

Hope that saves someone the hours I spent on it this morning.

@LucaBerniniKT Borked on us too after Windows Updates were installed this afternoon. Get-RdsSessionHost indicates the last heartbeat was received right before the VM was rebooted to install updates. KB4512508 is the culprit - I uninstalled it but the agent was still messed up. Dropped the Session Host from the host pool, uninstalled all the Remote Desktop agent stuff, followed the instructions for registering a session host to an existing pool via powershell, and got it working again after a reboot. Going to pause updates for a bit until a new agent comes out.

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
38 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies