This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 32%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAL%3C/text%3E%3C/svg%3E)
We had similar issue, this was the fix. We were also missing the Exchange Bank End certificate on port 444. Not sure if this matters, but we used our certificate first (third party) and EAC, EMS, and mail flow is working.
Thanks for post
Forgot.
Thanks for all help you giving me.
Is the any possibility to reinstall the IIS part of Exchange 2019?
//marsk
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 22%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKY%3C/text%3E%3C/svg%3E)
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
Creating and binding a new self signed backend certificate did it for us. Thank you!
Glad to hear it worked for you :)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 97%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBG%3C/text%3E%3C/svg%3E)
Did you ever solved this issue I'm having the same http error 503 only in ECP, OWA works fine.
Bill
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
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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(48, 21%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
I also had this error after windows updates. Luckily MuhammadBilal-8946 post fixed it.
Thx