Forum Discussion

Copper Contributor

Jun 17, 2022

Exchange 2019 ECP broken after update

Dear all, We currently have a hybrid setup with a Exchange Server 2019 used only for mgmt purposes, and recently CU12 has been installed, and seemed to be working well immediately after the upgra...

MVP

Jun 17, 2022

BDO_BvB
What is the result, when you access the ECP using the configured Exchange namespace FQDN, e.g. https://mail.something.tld/ecp?

It seems that the browser does not load the CSS files.

Do you see any errors in the event log of the server?

Does the IIS binding for the default website contain more than one TCP 443 binding?

What does the IIS W3SVC log file tell you? Do you see any errors accessing CSS files?

BDO_BvB

Copper Contributor

Jun 20, 2022

ThomasStensitzki-MVP
Thomas thank you already for the reply.

If I use the link as you mentioned, same result. A broken page.
There is only 1 port 443 binding on the default website
I don't really see any obvious errors in the W3SVC log file, but not sure what I should be looking for.
Eventviewer doesn't really contain errors for Exchange or the Web server logs.

Is there a way to rebuild the CSS files?