Forum Discussion
Started a few days ago at most: Agent on Session host no longer communicates properly with WVD
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 :
ClearForward Thanks for reporting the issue. This is service side issue and we have fixed it few minutes back. Can you please verify if it working now. We would like to further investigate if that's not the case. Thanks.
Johan_Eriksson When we started the two shut down session hosts, both went on to upgrade and got an upgrade failure. This put them both in Status UpgradeFailed.
The odd thing is that this caused connections to succeed. (Maybe sessions were incorrectly being routed to session hosts that are shut down.)
This leads me to suspect that the marking of shut down session hosts as "Available" is part of the bug that was somehow introduced in a recent deploy by MIcrosoft.
Roop_Kiran_ChevuriMicrosoft
Thanks for bringing this to our attention. Let me review this and get back to you on this.
Johan_Eriksson I'm having what I think is a related issue. Our setup is also from May 2019, and in the last 48 hours we're having constant issues.
Ever since our virtual desktop VMs auto-updated to Remote Desktop Services Infrastructure Agent 1.0.1006.2006, they keep falling into a bad state of "NoHeartbeat" after only a few minutes. When the VMs first boot, the status is "Available" and "LastHeartBeat" reflects the time of boot. We're able to connect to the pool without issue and can maintain sessions, but cannot start new sessions because the status changes to "NoHeartbeat".
If an admin restarts the "RDAgentBootloader" service, the status changes to "Available" and "LastHeartBeat" reflects the time of the service restart.
For reference, I am checking on the status of the pool with the "Get-RdsSessionHost" cmdlet.
- As a quick workaround for my issue, I'm had to setup a task with Task Scheduler that runs NET STOP and NET START of RdAgentBootloader every 1 min, starting at system boot and continuing indefinitely. This gives us about 55 seconds out of every minute where the session hosts are "Available", and 5 seconds where they're "NoHeartbeat". It's an awful hack, but it's better than nothing until MSFT can push a version of the RD Agent that can actually post heartbeats.
- Do you mind sending me your task scheduler settings please. I am in a bind and would like to get through the testing of the task scheduler you already did by reaching out. Thanks a million! GuyPaddock
- Roop_Kiran_ChevuriThanks for bringing this to our attention. Can you reply back with output of Get-RDSSessionHost please? Thanks.
