question

martinskorvald avatar image
0 Votes"
martinskorvald asked BillGarcia-9014 commented

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

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

office-exchange-server-connectivityoffice-exchange-server-itprooffice-exchange-server-deployment
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

KaelYao-MSFT avatar image
2 Votes"
KaelYao-MSFT answered KaelYao-MSFT commented

@martinskorvald
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.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@martinskorvald
Hi,
I am writing here to confirm with you how thing going now?
If you need further help, please provide more detailed information, so that we can give more appropriate suggestions.


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 Votes 0 ·
martinskorvald avatar image
0 Votes"
martinskorvald answered KaelYao-MSFT commented

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



· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,
Thanks for your information.

Do to that i'm with in the domain, I have generated a certificate from the domain CA.
Have you checked the bindings of the Default Web Site and the Exchange Back End in IIS manager?
Is there the certificate issued by the internal CA or a valid certificate bound?
39536-21.png
39622-22.png


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 Votes 0 ·
21.png (102.7 KiB)
22.png (140.5 KiB)
martinskorvald avatar image
0 Votes"
martinskorvald answered

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

!40604-1capture.jpg



1capture.jpg (86.6 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

martinskorvald avatar image
0 Votes"
martinskorvald answered

40605-2capture.jpg



2capture.jpg (116.0 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

martinskorvald avatar image
0 Votes"
martinskorvald answered martinskorvald edited

40496-4capture.jpg



4capture.jpg (50.6 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

martinskorvald avatar image
0 Votes"
martinskorvald answered BillGarcia-9014 commented

Forgot.
Thanks for all help you giving me.

Is the any possibility to reinstall the IIS part of Exchange 2019?

//marsk

· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,
You are welcome and wish we can find a solution to this problem.

Can you open EMS(Exchange Management Shell) on the Exchange 2019 server?
If you can,please run the following commands to recreate ECP/OWA virtual directories.

 Remove-EcpVirtualDirectory -Identity "Server01\ecp (Default Web site)"
 New-EcpVirtualDirectory 
    
 Remove-OwaVirtualDirectory -Identity "Server01\owa (Default Web site)"
 New-OwaVirtualDirectory

If it doesn't help with your problem,please create a new self-signed certificate via EMS and bind it to the Exchange Back End site.

 New-ExchangeCertificate

1 Vote 1 ·

Creating and binding a new self signed backend certificate did it for us. Thank you!

0 Votes 0 ·

Glad to hear it worked for you :)

0 Votes 0 ·

Did you ever solved this issue I'm having the same http error 503 only in ECP, OWA works fine.

Bill

0 Votes 0 ·
martinskorvald avatar image
0 Votes"
martinskorvald answered KaelYao-MSFT commented

Hi
No, it's exactly as it was before the reconstruction.
I've recreated the Exchange certificate, have bound it to standard and backend sites.
Exchange 2013 had a “Best Practices Analyzer” do you know if there is anything for 2019?

//marsk

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,
Please refer to this link: Exchange Analyzer
It also applies to Exchange 2019.


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 Votes 0 ·
MuhammadBilal-8946 avatar image
3 Votes"
MuhammadBilal-8946 answered JeffWalton-3328 commented

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



exchange.png (132.0 KiB)
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you! This solved our issue as well!

1 Vote 1 ·

Glad I was able to Help

0 Votes 0 ·

Thanks for posting this! We had recently installed a new certificate and had issues after the first reboot. Sure enough, the back end binding was blank and everything fired up as soon as I applied the certificate.

0 Votes 0 ·