Windows 10: Fix: Blank page when loading ECP on Exchange 2013

On Exchange 2013 you might encounter a blank page after the login page of the Exchange ECP portal. The Login page will load without issues but when you login successfully, an empty blank page loads.

This could be due to the Default Website and Exchange Back End website do not have the same certificate. Sometimes this happens when you either change the certificate or renew it.

To solve this, open the Internet Information Services (IIS) Manager
Expand Sites
Right click on Default Website and click on Edit Bindings



From the list click on the https with the port 443 cnad click the edit button and confirm that you have the new cerficate selected and take note of it.

Right click on Exchange Back End site and click on Edit Bindings

From the list click on the https with the port 444 and click the edit button. Here make sure that you have the same certificate assigned and click close. In my case the certificate assigned was empty as the certificate was deleted.



Run IISReset from the command prompt as Admin

The ECP will now load.

(879)

read more...

 

Why OWA showing "Loading"

I am running MS Exchange 2013. Recently I have been able to open OWA on all browsers until I noticed that I can no longer open OWA in Chrome or Internet Exlporer.

1. In Chrome it is showing a blank page with a tab tile "Loading", but it will not display anything.
2. In Internet Explorer it is showing broken messages with "X", it is not displaying properly.

Recently I been able to open it properly on Internet Explorer and Firefox only (On Chrome, after login, it was showing a blank page with the title of my "Outlook username"). Then I followed this
post and run UpdateCas.ps1 as instructed that is when it began to show "Loading" in Chrome (Number Above). I checked my SSL Certificates as some have suggested, they are set to "Microsoft
Exchange".

How do I solve this problem? Any link with possible solutions is appreciated.

 

OWA, ECP issues after exchange 2013 CU update 21

Hi All,

I seem to have run into an error after carrying out a CU update from 7 to 21. I cannot access the ECP and OWA. The upgrade had completed successfully, it had been run through the setup wizard.

I receive the following error when I try to access the exchange management shell

Would anyone be able to assist me with this issue?

Thanks

Dwayne

 

OWA, ECP issues after exchange 2013 CU update 21

Hello

Thank you for participating in the Microsoft Community, My name is Miguel T.

This problem occurs because one or more of the following conditions are true:

The Kerbauth module is configured incorrectly in Internet Information Services (IIS) in one of the following ways:

The Kerbauth module is displayed as a Managed module instead of as a Native module.

The Kerbauth module has been loaded on the Default website level (instead of, or in addition to, the PowerShell virtual directory).

The user does not have Remote PowerShell Enabled status.

The WSMan module entry is missing from the Global modules section of the ApplicationHost.config file that is in the following location:

C:\Windows\System32\Inetsrv\config\ApplicationHost.config

This causes the WSMan module to be displayed as a Managed module in the PowerShell virtual directory.

Note The WSMan Module entry may also be missing from the ApplicationHost.config file if the WinRM IIS Extension feature is installed on the server.

To know how to fix, please follow the steps in this support page:

https://support.microsoft.com/es-us/help/202830...

----------------------------------------------------------------------------------------------------

If the steps did not help you try the following steps:

The Kerberos authentication needs to be configured on the PowerShell website on the Exchange Mailbox Server:

Establish a remote connection to the Exchange server in question.

Click Run and enter inetmgr.

Expand the server in the left-hand pane.

Expand the Sites and Default Web Site trees, and then click PowerShell.

Double-click Authentication under the IIS section.

Right-click on Windows Authentication, and then select Providers.

If the Negotiate:Kerberos item is not present, add it through the Available Providers dialog box.

I hope this information has been useful, please let me know if you still need assistance.