Forum Discussion
Anyone experiencing session hosts becoming unavailable at random
AndreasJ5325 we also have this issue running Citrix in multi user Win 10 in azure. Out of 50+ session hosts running per day we get 2 or 3 isssues per week. Session host becomes unavailable in Citrix, rdp won’t work. We can still access the machine via unc path to c$ and get to services remotely. The machine isn’t completely dead but all sessions freeze on it. Event logs usually show a terminal services failure svchost. I have been working with MS on a ticket for a few weeks with logs/memory dumps. the host needs to be rebooted to bring it back to a working state. It could be down to certain we redirect as we also usually see audiobuilder service issues around the same time but that could just be because termservice is dead. The issue is completely random though intermittent we went a whole month between dec and jan with no issues and then started up again mid January. We’ve had these issues since November.
PioWi still waiting for MS to come back after analysing full memory dump
- Did you ever solve this?
Ebot_H Still working through this with MS, funny enough, their latest update appears to be pointing to a HW failure on AMD 64-bit CPU EPYC 7763 which is run on their servers cause by the GPU driver that's integrated with the CPU.
They are advising to update the graphics drivers on the VM, although that's not possible since our VMs are not GPU enabled and it's just using the Citrix display adapter.
So something running on the VM could be causing the HW failure with the type of AMD CPU used in the hosts.
They've asked for a couple more things to check, it's totally random failures though, we haven't had any for a week or 2. I wouldn't be surprised if some of the hosts in Azure are missing updated HW or GPU drivers and sometimes the VM's just happen to run on an out of date one causing the failure....
steveturnbull1975
Please configrm that you have the same : when pool will delleocate VM from pool it's not possible to power on it again, but whe you manually power on it it became in pool, the agent is newest 1.60 something, i have tried with Startr VM on connect but also no result
- We are not seeing this issue, so first step is opening a ticket with Microsoft. No issue on 40-50 hosts with 1.0.6028.2200. It could very well be the symptoms are the same, but this is a different issue.
