"HTTP Error 503. The service is unavailable" then browsing to /ECP "exchange 2019"

Martin Skorvald 26 Reputation points
2020-11-06T11:44:30.603+00:00

Hi
Migrating from exchange 2016 to 2019.

Exchange host 2019: elemsex01

I get "HTTP Error 503. The service is unavailable" when browsing to:

I have read all threads and blogs I can finned but nothing is helping me.

Do someone have any idea how I can continue my trouble shooting?

//marsk

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,704 questions
{count} votes

9 answers

Sort by: Most helpful
  1. Muhammad Bilal 71 Reputation points
    2021-06-28T02:10:09.393+00:00

    Hi Martin,

    I ran into similar issue when we installed a windows update. the errors were as below.

    1. users would get the error "Fix Exchange HTTP Error 503. The Service is Unavailable" when trying to access email via OWA
    2. Outlook Clients wont connect to the exchange server

    ****Resolution:****

    1. Open “ISS Manager”, Type “inetmgr” in “RUN” and select Default Web Settings and Open “Edit Binding option”It is vital to provide the correct Exchange Certificates to the ports
    2. as there are two parts of IIS in exchange 2013 onwards i.e. Exchange Frontend and Exchange Backend
    3. first I verified that the SSL corticates bindings with the correct SSL certificate were present.
    4. Than I looked at the Exchange Bank End home and found that there were no certificate bindings for port 444
    5. Selected the Microsoft Exchange Server ( self generated default Certificate by the exchange Server) do not use the third party CA to bind in this location
    6. as soon as this was selected OWA/ECP and outlook clients started working fine.

    I hope this helps.

    Many Thanks

    Bilal109654-exchange.png

    14 people found this answer helpful.

  2. Kael Yao-MSFT 37,661 Reputation points Microsoft Vendor
    2020-11-09T05:46:14.963+00:00

    @Martin Skorvald
    Hi,

    Sorry I need to ask several questions in order to get some more information:

    1. Can you see the login page? If you can,was the administrator account on the Exchange 2016 server and you powered the Exchange 2016 server off?
    2. Are you able to access OWA?
    3. What suggestions have you tried so far? Did you try the following ones?
      (1)check the certificates bindings of Default Web Site and Exchange Back End in IIS manager.
      (2)check if the MSExchangeECPapppool stops or recycle the MSExchangeECPapppool.
    4. Did you find some relevant error messages in the application log?

    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.

    2 people found this answer helpful.

  3. Martin Skorvald 26 Reputation points
    2020-11-12T21:39:26.163+00:00

    sorry if i'm a bit short in my answer.
    A hectic day.

    I only get "HTTP Error 503. The service is unavailable" then i hit the IIS on the Exchange 2019.
    No log on page acure, not for ECP och webmail.
    It doesn't matter if the exchange 2016 server is on or off.
    The App and system logs is empty, nothing that can be related to IIS/Exchange.

    Do to that i'm with in the domain, I have generated a certificate from the domain CA.
    The root certificate for this CA is trusted in all machines that I use.
    The app pool has been recycled.

    //marsk


  4. Martin Skorvald 26 Reputation points
    2020-11-18T07:46:57.127+00:00

    Yes, I think my certificate is in the right place.

    !40604-1capture.jpg

    0 comments No comments

  5. Martin Skorvald 26 Reputation points
    2020-11-18T07:51:34.027+00:00

    40605-2capture.jpg

    0 comments No 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.