Share via

How to pass "ajax error 500" with Windows Admin Center 24.10 (v2)

Ville Tuulos 15 Reputation points
2025-04-06T20:14:19.1633333+00:00

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?

ShotOnError_WAC_2410_AjaxError_2025-04-06

(above the screen cap on the error after clicking my Server "Hyperpilvi" -> "Connection error")

Any ideas how to resolve this one?

Windows Server Remote and virtual desktops Session connectivity

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. 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.

    https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/deploy/install?tabs=server-core&pivots=windows-server-2022

    1 person found this answer helpful.
    0 comments
  2. Randall Okwei 16 Reputation points
    2025-04-23T00:46:31.1633333+00:00

    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.

    0 comments
  3. 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:

    1. Check the WAC logs: Look in %ProgramData%\Microsoft\Windows Admin Center\Logs for detailed error logs that might reveal what's causing the 500 error.
    2. Test PowerShell Remoting specifically:
    Enter-PSSession -ComputerName hyperpilvi

    This will verify if basic PS remoting works between your client and server.

    1. Check the HTTP listener configuration:
    winrm enumerate winrm/config/listener

    Make sure both HTTP and HTTPS listeners are properly configured.

    1. Verify that your TLS certificate is properly trusted by the client machine.
    2. Try modifying the WAC gateway to use HTTP temporarily (for testing only):
    powershell
    1. 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?
    2. 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.
    3. Try removing and readding the connection with different credentials or using a domain account if available.
    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.