Forum Discussion
Cannot Connect to VMs in Windows Admin Center
Hi all,
I have 1 Server Cluster made up of 3 Server 2022 Hosts on which there is a large number of VMs running on Hyper-V.
The typical process for accessing the VMs has been through Windows Admin Center, which is hosted on one of the VMs in the cluster.
Around 1 week ago, it was no longer possible to connect to the VMs through Windows Admin Center as an infinite loading screen was presented. Sometimes, the following error shows up in VMConnect:
The cluster and servers are still connected to WAC and all the VMs that are expected are present on WAC.
Since then, the following things have been attempted:
- Restart all servers
- Rebuild WAC on Current VM
- Build WAC on Fresh VM with the same and different network configuration, using current (2606) and previous (2511) versions of WAC
- Build WAC on one of the hosts
All these attempts result in the same error as seen before.
Has anyone experienced this issue before? Or does anyone have any advice?
Thank you in advance!
Hi there,
So for us the issue wasn't anything on the hardware or OS side but for some reason the WAC extensions were just not working. We turned off automatic update extensions and reverted to previous extension versions.
WAC Version: 2410
Build: 2.4.2.1
The relevant extensions with the versions we are using:
Cluster Manager: 5.2.6
Remote Desktop: 6.0.20
Virtual machines and switches: Version 6.2.6
Hope this helps
11 Replies
I have this same proublem. My try before seeing this post is putting my WAC OS in flight mode , no internet connection. Installing WAC2606 with select not to do automatic update. When WAC WEBUI come up.. I go to setting>> extension >> do not update the extension.. Then connect my WAC to network and start adding the cluster IP and nodes IP . everything fine. I can connectVM to my vms. until tomorrow morning.. I see the splash notification of succesfully extension update. From this point the proublem is comeback again..
After seeing this post.. I roll back the extension from 9.0.12 to 6.2.6 . but the proublem still be there.. There might be I need to use the old WAC 2410 , not sure.
Because the cluster and VM inventory still load, I would troubleshoot the VMConnect extension path rather than rebuilding Windows Admin Center again. From the WAC gateway, confirm the browser can reach each host over the management network and that CredSSP/WinRM settings have not changed. Then test VMConnect directly from Hyper-V Manager on one host using the same admin account. If Hyper-V Manager works but WAC stays on the loading screen, update Windows Admin Center and its extensions, clear the WAC gateway cache, and collect the browser console error plus WAC gateway logs. That evidence is more useful than another fresh WAC install.
I am just getting a spinning circle and I am unable to connect either
I am having this same issue. Were you able to find a fix?
Hi there,
So for us the issue wasn't anything on the hardware or OS side but for some reason the WAC extensions were just not working. We turned off automatic update extensions and reverted to previous extension versions.
WAC Version: 2410
Build: 2.4.2.1
The relevant extensions with the versions we are using:
Cluster Manager: 5.2.6
Remote Desktop: 6.0.20
Virtual machines and switches: Version 6.2.6
Hope this helpsi am currently using the same extensions and versions:
Cluster Manager: 5.2.6
Remote Desktop: 6.0.20
Virtual machines and switches: Version 6.2.6
and i am not able to connect to my VM's still. i can download an RDP file and that works but all i get is a spinning circle when trying form Virtual Machines under a host
The screenshot narrows this down: cluster inventory works, but WAC's browser-based VMConnect fails while the keyboard-layout field is unset and returns a JavaScript “undefined” error. Because it follows fresh gateways and two WAC versions, this alone does not show that Hyper-V or the guests are unavailable. First, explicitly select a keyboard layout before Connect. Retry in current Edge or Chrome InPrivate. If that works, clear cached site data for the WAC gateway. From Virtual Machines, try Download RDP file and open it with Remote Desktop Connection, using an account that can administer the Hyper-V host; success isolates the fault to WAC's web console. Confirm the Windows Admin Center and WinRM services are running. If it still fails, collect Microsoft-ServerManagementExperience errors from Event Viewer and a sanitized browser HAR during reproduction. Submit those, both WAC versions, and the exact error to Windows Admin Center feedback.
Thank you for the suggestions and time! We found the issue was specific with the extension versions so after reverting to previous versions the problem was solved.
