Forum Discussion
MicrosoftHow to troubleshoot Unavailable Status of SessionHost
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?
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
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.
Unfortunately, it was a year ago and I built a demo environment that no longer exists. Make sure that the VM is joined in the domain. I had password issues here. You need two passwords for Broker and AD. Make sure all prerequisites are installed. Microsoft has also reworked the management portal. You can now manage wvd in the Azure portal for a longer time. The Powershell patchwork is no longer necessary.
