Exchange 2013, single server environment.  The administration logon page comes up fine, but after you authenticate, the page looks like this (it worked fine yesterday):

I tried resetting the ECP virtual directory, the page is still displaying the same way.

I tried resetting the ECP virtual directory, the page is still displaying the same way.

• Proposed as answer by Fuzail Motan 11 hours 15 minutes ago
• Unproposed as answer by Fuzail Motan 11 hours 15 minutes ago

I tried resetting the ECP virtual directory, the page is still displaying the same way.

• Proposed as answer by Fuzail Motan Saturday, June 06, 2015 8:11 PM
• Unproposed as answer by Fuzail Motan Saturday, June 06, 2015 8:11 PM

I tried resetting the ECP virtual directory, the page is still displaying the same way.

• Proposed as answer by Fuzail Motan Saturday, June 06, 2015 8:11 PM
• Unproposed as answer by Fuzail Motan Saturday, June 06, 2015 8:11 PM

RD Wilderman,

Do these above steps and give me your result. If it is solve then please mark an answer.

It will solve your problem.

Use below command to reset your IIS on cas: iisreset.

It will update IIS Virtual Directory and reset all its settings.

Thanks.

I had tried that several times already, and it did not help the problem. It seems as though updating to cumulative update 8 has fixed the issue though.

when these kind of stuff happens it often helps to add to compatibility list or to trusted sites/local intranet.

Did you access ECP from server or a client?Internal or external?

I had tried compatibility view settings as well.  This was accessing it from a client, a server, or even the Exchange server... all the same.

I had tried compatibility view settings as well.  This was accessing it from a client, a server, or even the Exchange server... all the same.

Hi,

Please change a browser and check whether the issue persists.

Also confirm whether the latest IE updates KB3038314 was installed in your environment. If that is the case, please uninstall recent IE updates : KB3038314 and KB3049563 to have a try.

Regards,

Sorry Winnie, I cannot test that. As stated earlier, it seems as though updating to cumulative update 8 has fixed the issue.

• Marked as answer by RDWilderman 2 hours 22 minutes ago