exchange charter business net owa login

After you deploy Exchange 2013 locally, we can use the specified OWA address for mail access, such as: mail.contoso.com. When we implement a hybrid deployment of on-premises Exchange 2013 and Office Exchange online, Whether you are an Exchange online user or a local exchange

Today, you receive a script alert message that an Exchange Server OWA cannot log on!A manual test, found that there is a problem, the error message is as follows:Check the log of the server, found the following information1. The request to access OWA received an error of $ internal Server error at HTTP level (error pointing to

17.3LoginEcpand theOwaTest17.3.1LoginEcpbelow, enter the following ECP URL for Exchange,HTTPS://EX11.ROBIN.COM/ECP650) this.width=650; "Width=" 720 "height=" 537 "title=" 01.png "style=" WIDTH:720PX;HEIGHT:537PX; "src="/HTTP/ S3.51cto.com/wyfs02/m01/6e/89/wkiom1v-1u3wp7waaagzqww9j6q974.jpg "border=" 0 "vspace=" 0 "hspace=" 0 "alt=" Wkiom1v-1u3wp7waaagzqww9j6q974.jpg "/>After clicking Login, you can see the

"border=" 0 "/>Then we can let a tenant use Mail.a.com/owa login to their own mailbox, log in will use the email address as the login name.650) this.width=650; "height=" 418 "title=" clip_image022[4] "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none; "alt=" clip_image022[4] "src=" http://s3.51cto.com/wyfs02/M01/58/B2/

Environment: Dc+exchange 2013 (front and back)Fault:1. Login ECP, OWA, unable to display the page error2.EMS Unable to connect to server, errorExclusion Method:Check the status of the service is normal, view the event log, found a large heap of httpevent 15021 error, view the IIS virtual directory, found IIS default virtual directory 443 is not bound certificate,