Forum Discussion
How to troubleshoot Unavailable Status of SessionHost
- May 01, 2020
Martinsd Thanks for opening the support ticket. That is the right approach as we would need to troubleshoot where the failures are coming from by looking at your logs.
Hi,
i can relate to this. Created multible tenats via powershell. (Azure template does not work ?).
Each VM regsitered in the host pool successfully. But each VM is unavailable. Tried different VM´s and different Host Pools.
- Eventlog displays an error like this:
"Microsoft.RDInfra.Monitoring.AgentMonitoringService.AgentMonitoringServiceWorker
Fail to set default dimensions Invalid Operation: Fail to set default dimensions, error code is 2147942487.. Error code is 80070057"
- I think the SxS Network Stack is broken , because i´m not able to update it (corrupt ressources?).
- qwinsta is not very helpfull.
SESSIONNAME USERNAME ID STATE TYPE
services 0 Disc
console 1 Conn
>rdp-tcp#1 appAdmin 3 Active
31c5ce94259d4... 65536 Listen
rdp-tcp 65537 Listen
corrupt installation files? Anyone with a brilliant idea?
- ayanbbhattacharyaNov 04, 2020Copper Contributor
Did you get around an solution to this. My problem is similar, I have 2 tenant created and I have 2 host pools . Everytime I build a VM it's resides as unavailable. The agents were reinstalled , but still the problem persists. -- Ayan
- DrewPetrieJan 04, 2021Copper Contributor
- DBR14Feb 15, 2021Iron Contributor
Any luck with this? This just suddenly started happening to me today. My test user can connect to the host still despite it saying Unavailable. I can also login with the local admin account via Bastion. But I can't use MSIX App attach as it says none of my hosts have VMs.
- wapereiraAug 31, 2020Copper ContributorGuys,
Follow the step by step to resolve this situation:
https://docs.microsoft.com/pt-br/azure/virtual-desktop/troubleshoot-vm-configuration
Error: The status filed in Get-AzWvdSessionHost cmdlet shows status as Unavailable
Get-AzWvdSessionHost cmdlet shows status as Unavailable.
Cause: The agent isn't able to update itself to a new version.
Fix: Follow these instructions to manually update the agent.
Download a new version of the agent on the session host VM.
Launch Task Manager and, in the Service Tab, stop the RDAgentBootLoader service.
Run the installer for the new version of the Windows Virtual Desktop Agent.
When prompted for the registration token, remove the entry INVALID_TOKEN and press next (a new token isn't required).
Complete the installation Wizard.
Open Task Manager and start the RDAgentBootLoader service.