Share via

Exchange Server Management Console not loading

Chris Melnik 5 Reputation points
2026-03-17T18:24:48.2866667+00:00

Hello,

I am trying to access the Exchange Admin Console on the web on my Exchange Server. The server is running Windows Server 2025, and I have Exchange Server 2019 CU14 installed. Whenever I open the portal on the web, I'm greeted with a login page. I log in with the correct username and password, but then it gives me a "This page isn't working" error.

I've tried restarting IIS, changing SSL certs bindings in IIS, changing authentication settings, Windows updates, etc.

Any help is greatly appreciated!

Thank you,

Exchange | Exchange Server | Management
Exchange | Exchange Server | Management

The administration and maintenance of Microsoft Exchange Server to ensure secure, reliable, and efficient email and collaboration services across an organization.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Hani-Ng 10,070 Reputation points Microsoft External Staff Moderator
    2026-03-18T01:22:20.1+00:00

    Hi Chris Melnik

    Since you can successfully authenticate but receive a "This page isn't working" (HTTP 500) error immediately after, this indicates a breakdown in communication between the Front End and Back End of the Exchange server.

    You can perform the following checks in order:

    Check OS and Exchange Compatibility:

    You are running Exchange 2019 CU14 on Windows Server 2025. According to the support matrix, older Cumulative Updates of Exchange 2019 may not be fully supported on Windows Server 2025 due to changes in IIS and TLS handling. ̣

    Exchange Server supportability matrix | Microsoft Learn

    I strongly recommend updating to the latest Cumulative Update or Exchange Server SE, which includes the necessary fixes for Server 2025. The update process often automatically repairs IIS bindings.

    Verify IIS Back End Bindings:

    • Open IIS Manager > Expand Sites.
    • Default Web Site (Front End): Check Bindings (443). This should use your Third-party/Commercial Certificate.
    • Exchange Back End: Check Bindings (444). This must use the self-signed certificate named "Microsoft Exchange" and do not use your commercial certificate on the Back End (port 444). If you do, the console will not load properly.

    You can refer to:

    Fix Failed Exchange Server Updates - Exchange | Microsoft Learn

    Assign certificates to Exchange Server services | Microsoft Learn

    Check for Expired OAuth Certificate (Event 1003)

    If the bindings are correct, the issue is likely an expired internal Auth certificate.

    • Check Event Viewer > Windows Logs > Application > Look for Event ID 1003 from source MSExchange Front End HTTPS Proxy.
    • If found, you must renew the Exchange Server Auth Certificate.

    Can't access OWA/EAC with expired OAuth certificate - Exchange | Microsoft Learn

    Restart IIS

    After making any of the changes above, run the following in an elevated PowerShell to apply changes:

    Restart-Service WAS, W3SVC
    

    I hope this information helps.


    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


Your answer

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