Error 500 new on-prem exchange 2019

as-1m 21 Reputation points
2021-04-22T20:30:21.98+00:00

We are upgrading our exch 2016 to 2019. It's a hybrid environment with no on-prem mailboxes. Mails still flow through the local exchange though. I have updated dns entries n emails are flowing seemless through the new server.

The issue:

When I shutdown the 2016 exch, I can no longer login to ecp from server 2019 using https://fqdn/ecp or https://mail.domain/ecp . After I login with correct creds it presents "http error 500 server is currently unable to handle this request". I have recreated virtual directories on the new server via powershell but not getting anywhere.

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,335 questions
Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
1,875 questions
0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Kael Yao-MSFT 37,491 Reputation points Microsoft Vendor
    2021-04-23T08:35:07.807+00:00

    Hi @as-1m

    Agree with Andy, please run this command Get-Mailbox -arbitration via EMS to check if the arbitration mailboxes are still on the Exchange 2016 server.
    If there are some, you may need to move them to the Exchange 2019 server.

    The cause of the issue may probably be the system mailboxes(Arbitration mailboxes) are unavailable, which are responsible for admin accounts without a mailbox to log in EAC.

    For more information on this topic, please refer to this link: HTTP 500 Internal Server Error when logging into Exchange 2013 Exchange Control Panel (ECP)

    If the response is helpful, please click "Accept Answer" and upvote it.
    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.

    1 person found this answer helpful.
    0 comments
  2. as-1m 21 Reputation points
    2021-04-23T17:19:38.987+00:00

    It definitely was arbitration mailboxes. They were still on the 2016 server.
    Migrating them over fixed the prob

    0 comments