Workaround for OWA blank page after Exchange 2013 input account password

To show that I'm not in the hole, so share a little something out.

Recently in helping customers do upgrade Exchange 2010 only 2013, during a few issues, have the opportunity to share. Today, let's talk about the problems that have plagued me for several days. When you log in to OWA, the entire page is blank after you enter your account password, and nothing happens.

The first type:

ECP page login After the entire page blank, the estimated people will be surprised to see, the EAC can not get in, but also how to look at the server problem ah.

This situation, will let ordinary users even OWA can not login, that is, unable to login via the Web mailbox with the EAC interface.

Workaround:

1 Start-management tools--iis Manager

I here is the front end and back end are all on the same server, if your front and back end is not the same server, then to the corresponding server to find the corresponding site Oh.

IIS Manager has two Web sites, one default Web site, and one Exchange back-end Web site (the back-end Mailbox role Server's Web site). The default Web site is for the front End server (CAS), allowing us to log in to OWA and other Oab,autodiscover and virtual directories.

Then check the two Web site binding certificate, to the same line, that is, two Web site binding certificate is the same, generally because there is a Web site certificate binding problem, resulting in the inability to communicate to make OWA blank.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/6C/21/wKiom1VAeFzTbgU4AALekn8lYgQ193.jpg "title=" 2015-04-29_142013.png "alt=" Wkiom1vaefztbgu4aalekn8lygq193.jpg "/>

2 Expand Server--sites (site)--default Web site, click the Default Web Sites page, click the right-most activation (actions) window-bindings (bindings)

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/6C/21/wKiom1VAeKWSeBy6AAVf_DjwiqY673.jpg "title=" 2015-04-29_142133.png "alt=" Wkiom1vaekwseby6aavf_djwiqy673.jpg "/>

3 in the pop-up Site Bindings window, select HTTPS, the address is *, the port is 443 entries, click Edit on the right side of the window.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/6C/1D/wKioL1VAekqQRC0SAADoWQt56e4891.jpg "title=" 2015-04-29_142248.png "alt=" Wkiol1vaekqqrc0saadowqt56e4891.jpg "/>

4 Pop up the edit Site Bindings window, select the SSL certificate below (SSL certificate), select the drop-down box, set the Exchange certificate that we want to use (if self-signed, use self-signed, select the certificate you requested if you request a certificate from a Certificate server). Click OK to confirm

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/6C/21/wKiom1VAeSGS76zOAAD6eVT4QTo371.jpg "title=" 2015-04-29_142351.png "alt=" Wkiom1vaesgs76zoaad6evt4qto371.jpg "/>

5 Restart the site, you can use the command iisreset or restart the server, you can also restart the window page (restart).

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/6C/21/wKiom1VAeU-hsmqtAAJo3-TOh78163.jpg "title=" 2015-04-29_142439.png "alt=" Wkiom1vaeu-hsmqtaajo3-toh78163.jpg "/>

6 similarly setting up the backend site is the Exchange back end site, as in the previous steps.

Set the certificates that they use for the same certificate.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/6C/21/wKiom1VAeXvT0zfFAAUxnR-YpTg640.jpg "title=" 2015-04-29_142520.png "alt=" Wkiom1vaexvt0zffaauxnr-yptg640.jpg "/>

Restart the website, log in to EAC and OWA, and find that you can login normally. Jump Normal.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/6C/1D/wKioL1VAeyXxkpyDAAJIoXbL89c235.jpg "title=" 2015-04-29_142627.png "alt=" Wkiol1vaeyxxkpydaajioxbl89c235.jpg "/>

The second type:

The EAC normally logs on, and the Exchange 2013 OWA is logged on normally, but during coexistence, exchange2010 users logged on with the Exchange 2013 Web site, failed to jump normally, popped 500 errors, and Exchange 2013 's OWA was 500 error.

Set--internet properties on IE-Advanced-browse, Cancel "show friendly HTTP error message".

When using OWA to log in to Exchange 2010 users, enter the account password, skip to the blank page, no movement.

Of course, this normal is not the case, in case the Exchange CAs can not log on to 2010 users, do as I said below.

The Exchagne 2010 certificate is exported to the Exchange 2010 server, imported to the Exchagne 2013 server, through the Exchange EAC page import to 2013, the certificate how import export please teach yourself, or Baidu tutorial, very simple, here is not.

1 Expand Server--sites (site)--default Web site, click the Default Web Sites page, click the right-most activation (actions) window-bindings (bindings)

2 in the pop-up Site Bindings window, click Add

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/6C/1D/wKioL1VAe4azSxj1AADaqmtpAmI323.jpg "title=" 2015-04-29_142805.png "alt=" Wkiol1vae4azsxj1aadaqmtpami323.jpg "/>

3 type; HTTPS Address: (Exchange 2010 IP) port: 443 Certificate: Exchange 2010 Certificate

4 Click OK to restart the website

Later, users using Exchange 2010 logged on to the OWA in Exchange 2013, and the discovery automatically jumps past to the version of OWA 2010.

If you meet a similar situation, you can also direct me.

This article from the "Technology sharing" blog, reproduced please contact the author!

Workaround for OWA blank page after Exchange 2013 input account password