Exchange server installation 2013 running since 2012. Recently replaced SSL Cert. Since then: URL https://FQDN/ecp opens blueish Outlook Web App (as before). Type in Domain/Username and Password results in a yellowish window stating "Unexpected Error. An error occured and your request couln't be completed. Please try again." Outlook can connect to server, just opening EAC does not work. Worked before the new SSL Cert. Any suggestions how to resolve this? Thank you.

Hi 

Please check if you have followed all the below steps 

http://exchangequery.com/2014/12/12/steps-to-perform-ssl-certificate-renewal-in-exchange-20102013/

Hello

Here you can try 2 options.

1) recreate the Virtual Directories.

http://www.curu.ca/2013/01/how-to-re-create-ecp-virtual-directory-in-exchange-2013/

2) if above option did not work. please fallow below option.

https://social.technet.microsoft.com/Forums/exchange/en-US/777b51ee-330d-43cc-a56e-4614d44aed7b/unable-to-access-owa-or-ecp-something-went-wrong-or-500-unexpected-error?forum=exchangesvrclients

Hi Snx1,

Thank you for your question.

Did the error occur when we logon OWA?

First of all, we make sure the URL which we type is correct without any problems. Then we could create another administrator to check if we could login ECP. We could use current user account logon ECP after we logon successfully with another account.

If  new administrator account logon with same error, we could delete Window Profile, then type https://FQDN/ecp to check if the issue persist.

If the issue persist, we could collect application log and event log and send to ibsexc@microsoft.com for our troubleshooting.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

Dear Jim,

Thank you. OWA is working, Exchange Management Shell can connect, Outlook can connect. Recently replaced SSL Cert. Since then: URL https://FQDN/ecp opens blueish Outlook Web App (as before). Type in Domain/Username and Password results in a yellowish window stating "Unexpected Error. An error occured and your request couln't be completed. Please try again." The old UC Cert had 4 entries: hostname of Exchange server, its FQDN, mail.domain.TLD and autodiscover.domain.TLD. The new Cert does no longer contain the hostname alone because Cert Authorities do not allow them anymore. After installation of the new Cert we had to change SSL binding parameters to correspond to the new Cert because there are 4 other Certs available in IIS Server Certificates (older ones, one revoked). Since then Outlook works again. We could imagine the problem is in connection either with the missing hostname or with a wrong Cert "seen" by ECP login.

Best regards, Marcel

Hi Marcel,

Could you logon ECP by https://localhost/ecp on Exchange CAS server?

Are you enable FBA on ECP virtual directory?  We could disable it to check if the issue persist.

We could refer to Chinthakas advice to re-create ECP virtual directory.

When we didnt login ECP, we could check IIS log and send it to ibsexc@microsoft.com for our troubleshooting.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

Dear Jim

> Could you logon ECP by https://localhost/ecp on Exchange CAS server?

No. As with FQDN, the URL opens a blueish Outlook Web App (as before). Type in Domain/Username and Password results in a yellowish window stating "Unexpected Error. An error occured and your request couln't be completed. Please try again."

> Are you enable FBA on ECP virtual directory?

What is FBA?

Best regards,

Marcel

HI,

he has enabled the FBA otherwise they cannot see bluish WeBAPP page.

Seems they have problem with OWA / ECP Vdir.

Please recreate the OWA/ECP Vdirs. that will resolve your problem.

furthermore update to Latest CU on the Exchange Server.

Regards