ECP exchange 2019 Error 503

Marc ALLAVENA 1 Reputation point
2020-09-07T15:01:34.947+00:00

Hi,

I don't know how to solve this. I installed an Exchange Server 2019 on a new Windows Server 2019 Standard. I tried to use Storage Migration Service to migrate my AD without success so I migrated it manually. It was successfull.
I installed Exchange server 2019 on my server but when I tried to go to the Exchange ECP, i arrived on the Storage Migration Service. I decided to remove the Storage Migration Service and know I can't access ECP. I have an error 503 - service unavailable.

Any detailed help will be appreaciated.

Thanks in advance.

Marc.

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,349 questions
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Lydia Zhou - MSFT 2,371 Reputation points Microsoft Employee
    2020-09-08T03:08:20.337+00:00

    @Marc ALLAVENA

    Do you have other Exchange servers in your organization?
    I'm a little confused about "migrate my AD". Please provide more details about what you migrated to Windows server 2019.
    Do you get any errors when prepare AD and extend schema before installing Exchange 2019?

    Do you use "https://localhost/ecp" to login to EAC? You can try to use the internal url to test again, and you can check the url with following command:

    Get-EcpVirtualDirectory|fl identity,*url*

    Here are more suggestions for you.
    1.Go to IIS Manager, and recycle MSExchangeECPAppPool in Application Pools. Application Pools > MSExchangeECPAppPool > Recycle:
    23124-555.png

    2.Check site bindings. Right click Default Web Site > Edit Bindings. Check the certificate bound for port 443. By default, the certificate "Microsoft Exchange" is used for a newly installed Exchange server:
    23123-556.png

    Check port 80 and 443, make sure no Host name is set for them.
    Right click Exchange Back End > Edit Bindings, make sure "Microsoft Exchange" is used for port 444, and no host name is set for port 81 and 444.

    3.You also can restart IIS to see if EAC works.

    4.When you reproduce the issue, you can post the screenshot of the error page here and don't forget to cover your personal information. Please also check if any related event logs are generated.

    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.

    0 comments
  2. Marc ALLAVENA 1 Reputation point
    2020-09-08T15:13:33.353+00:00

    Hi,

    Thanks for your answer. Let me tell more about the all story.
    My customer has an old server running Windows SBS 2011 including Windows 2008 R2 ans Exchange 2010.
    He bought a new server with Windows Server 2019 standard.
    To migrate roles from the old server to the new one, I thougth it could be easier to use Storage Migration Service to do it. Using this console I was able to move data from one server to the other but I never have been able to pass the readiness check to do the entire job (migrating AD).
    Finally, I decided to migration the AD, the DHCP, and th DNS "manually". On the Windows server 2019 console, everything was ok on all the roles.
    Then I tried to install Exchange 2019. Installation done, we tried to connect to the ECP console using the url //localhost/ecp but the result was that we were connected to the Storage Migration Console.
    We decided to remove the Storage Migration Console from the server and then trying to go to the ECP console, we had an error 503 : service unavailable.

    It's a nightmare now because we tried to uninstall Exchange and to reinstall it from scratch but each time, we have a stop on the installation as there is some errors. I reaaly don't know how to move out of this situation. Some poeple says that the only solution is to reinstall Windows Server and then create 2 VM (one for the AD part, the other one for Exchange)...

    I don't know what to do.

    Marc.

    0 comments
  3. Lydia Zhou - MSFT 2,371 Reputation points Microsoft Employee
    2020-09-09T07:00:26.47+00:00

    @Marc ALLAVENA

    Actually, Exchange 2010 is not supported to coexist with Exchange 2019. If you want to use Exchange 2019, it's suggested to coexist with Exchange 2013/2016, after the migration, you can uninstall Exchange 2010, then install Exchange 2019. Exchange 2019 is supported to coexist with Exchange 2013 or 2016, and it also requires specific CUs. You can check this for more details: Supported coexistence scenarios for Exchange 2019.

    Before we install Exchange servers, we also have to make sure the AD environment is supported. If needed, we have to add new DC/GC into the organization, insure the AD servers and functional level are supported for your old Exchange 2010 and new Exchange 2013/2016. For your reference: Supported Active Directory environments. Additionally, we don't recommend to install Exchange on a DC. Please check this for more information: Installing Exchange on a domain controller is not recommended.

    For your organization, you can install and migrate to Exchange 2016 firstly, then consider Exchange 2019. Uninstall the Exchange 2019, check and prepare requirements for coexistence scenarios between Exchange 2010 and 2016, then upgrade to Exchange 2016. Here is an Exchange deployment guidance tool for you Exchange Deployment Assistant, you can get more suggestions about the upgrade and migration from it.

    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.