SOLVED

Started a few days ago at most: Agent on Session host no longer communicates properly with WVD

Contributor

My host pool and tenant are probably from the May timeframe. The agent has version 1.0.1006.2006.

 

I notice that the agent posts a heartbeat on a restart of session host and then no more.

 

When connecting, the RDBroker appears to decide that no session host is available. 

 

I also notice that session hosts that are shut down are marked as Available in Status according to Get-RdsSessionHost. 

 

Have you made some recent (incompatible/bad) upgrade to WVD that I should be aware of. Do I need to do anything or this an issue on the MSFT side?

 

Here are diagnostics from one connect attempt:

PS C:\Users\johan> (Get-RdsDiagnosticActivities -TenantName "prod-fdt-avance" -ActivityId 8b9460d6-a900-4940-85ac-7b46031e0000 -Detailed).Errors


ErrorSource : RDBroker
ErrorOperation : OrchestrateSessionHost
ErrorCode : -2146233088
ErrorCodeSymbolic : ConnectionFailedRDAgentBrokerConnectionNotFound
ErrorMessage : RD Agent from host 6ce85f83-63c8-4c87-adb2-1d7d33dc12f7 is not connected to the Broker instance is
associated with during orchestration request.
ErrorInternal : False
ReportedBy : RDGateway
Time : 8/13/2019 12:02:32 PM

 

Here is the session host status (Last two are shut down since end of May):

PS C:\Users\johan> Get-RdsSessionHost -TenantName "prod-fdt-avance" -HostPoolName "avance"


SessionHostName : prod-rds-vm00.fdtcloud.se
TenantName : prod-fdt-avance
TenantGroupName : Default Tenant Group
HostPoolName : avance
AllowNewSession : True
Sessions : 1
LastHeartBeat : 8/13/2019 10:01:52 AM
AgentVersion : 1.0.1006.2006
AssignedUser :
OsVersion : 10.0.14393
SxSStackVersion : rdp-sxs190614002
Status : Available
UpdateState : Succeeded
LastUpdateTime : 8/6/2019 8:06:44 PM
UpdateErrorMessage :

 


SessionHostName : prod-rds-vm01.fdtcloud.se
TenantName : prod-fdt-avance
TenantGroupName : Default Tenant Group
HostPoolName : avance
AllowNewSession : True
Sessions : 0
LastHeartBeat : 5/28/2019 2:11:07 PM
AgentVersion : 1.0.407.7
AssignedUser :
OsVersion : 10.0.14393
SxSStackVersion : rdp-sxs190329002
Status : Available
UpdateState : Succeeded
LastUpdateTime : 5/28/2019 9:10:18 AM
UpdateErrorMessage :

 

 

SessionHostName : prod-rds-vm02.fdtcloud.se
TenantName : prod-fdt-avance
TenantGroupName : Default Tenant Group
HostPoolName : avance
AllowNewSession : True
Sessions : 0
LastHeartBeat : 5/28/2019 2:19:21 PM
AgentVersion : 1.0.407.7
AssignedUser :
OsVersion : 10.0.14393
SxSStackVersion : rdp-sxs190329002
Status : Available
UpdateState : Succeeded
LastUpdateTime : 5/28/2019 9:28:22 AM
UpdateErrorMessage :

 

23 Replies
I can confirm that after disabling my scheduled task and then monitoring the output of Get-RdsSessionHost over the last five minutes, I no longer see NoHeartbeat status! In addition, the LastHeartBeat is updating consistently every 30 secs now.

@GuyPaddock Thanks for the confirmation !! Again appreciate your time.

@Roop_WVD 

 

I can confirm as well that the issue seems solved. Many thanks!

@Roop_WVD 

 

Hi can confirm that my pools are all online.