Find the machine certificate Make sure that the subject is not blank, as well manage the keys by adding the network service account with full control.
How to pass "ajax error 500" with Windows Admin Center 24.10 (v2)
Hi there,
I did successfully deploy the new v2 of Windows Admin Center (Build 2.4.2.1, 2410). I've got a Dell HW as a server, where I have Windows Server Core 2019 running. The server core runs as a Hyper-V host. It has been nice and easy to run Hyper-V with Windows Admin Center so far but the most recent v2 seems to be causing all kinds of head-ache. Seemingly everything worked.
- WAC install can be run from admin cmd as is
- Setup TCP port as 44301 -> ok
- Check firewall -> ok
- ensuring that my star-certificate can be used -> ok
- set trusted hosts as all -> ok
- set anonymous use as ok ->
- set windows authentication as the method -> ok
- setting my own FQDN as de-facto connect point -> ok
- it even checks that PS remoting is on -> ok
- I tested via powershell that my firewall works
- starting WindowsAdminCenter service
- running from a client pc the https://FQDN:44301
- Great, it works, loads bootstrap and everything
- I get in with my admin (<local machine>\Administrator)
- Now here is where it gets funny
- I try to click to my "Server" -> "ajax error 500"
- this is so weird, no real error stack
- kind of getting a feeling that the WAC v2 is just incomplete
- How do you get pass this point?
(above the screen cap on the error after clicking my Server "Hyperpilvi" -> "Connection error")
Any ideas how to resolve this one?
Windows for business | Windows Server | User experience | Session connectivity
6 answers
Sort by: Most helpful
-
-
lukecelente 5 Reputation points
2025-04-18T14:43:07.6766667+00:00 I was getting the AJAX 500 message AFTER I renamed my server. I stopped the process and reinstalled and worked again.
-
Smith Pham 0 Reputation points
2025-04-28T10:46:24.9066667+00:00 Based on this error and what I can see, here are some more specific troubleshooting steps:
- Check the WAC logs: Look in
%ProgramData%\Microsoft\Windows Admin Center\Logsfor detailed error logs that might reveal what's causing the 500 error. - Test PowerShell Remoting specifically:
Enter-PSSession -ComputerName hyperpilviThis will verify if basic PS remoting works between your client and server.
- Check the HTTP listener configuration:
winrm enumerate winrm/config/listenerMake sure both HTTP and HTTPS listeners are properly configured.
- Verify that your TLS certificate is properly trusted by the client machine.
- Try modifying the WAC gateway to use HTTP temporarily (for testing only):
powershell- Since this is a v2 build (2.4.2.1, 2410), it's possible there are compatibility issues with Windows Server 2019. Have you considered testing with a more recent OS version like Windows Server 2022?
- Check if there are any constraints with accessing a Server Core installation - though this shouldn't be an issue as WAC is designed to work with it.
- Try removing and readding the connection with different credentials or using a domain account if available.
- Check the WAC logs: Look in
-
Thomas Amon 0 Reputation points
2025-07-11T14:43:10.0766667+00:00 I had this same ajax 500 error after upgrading from 2311 to 2410. I reinstalled WAC using the self-signed certificate (expire in 60 days) and am no longer getting ajax 500 errors. Seems to me that this is a CERTIFICATE issue per se. WAC didn't seem to like the published certificate and associated permissions for the "NETWORK SERVICE".
-