Cannot access ECP and appear error "HTTP 500"

Kelvin Cheng 20

你好，我無法連入ECP，請問有什麼解決方法? 謝謝!

enter image description here

2 answers

Kael Yao-MSFT 37,646 Reputation points Microsoft Vendor

2023-11-17T07:38:49.29+00:00
Hi @Kelvin Cheng,

From the screenshot you are accessing ECP with url mail.domain.com.

Below are a few questions in order to narrow down this issue:

Is it a fresh install of Exchange? If not, what changes have been done before this issue?

If you access ECP on the Exchange server with https://localhost/ecp, would this issue persist?

Does Exchange Management Shell work for you?

Does Outlook on the web (https://localhost/owa) work for you?

Thanks in advance for the information.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Kelvin Cheng 20 Reputation points

2023-11-17T07:55:38.1266667+00:00
We used Exchange long time. After removed the SSL certificate, the problem happened. Also, we had main and backup mail server, but the main server was failure now. So, we already turnoff the main server.

When we access by https://localhost/ecp, it will jump to "https://localhost/owa/auth/logon.aspx?url=https%3a%2f%2flocalhost%2fecp&reason=0".

Yes, the Exchange Management Shell is working.

We also cannot access to (https://localhost/owa).
Please sign in to rate this answer.
Kael Yao-MSFT 37,646 Reputation points Microsoft Vendor

2023-11-17T08:15:47.8866667+00:00

After removed the SSL certificate, the problem happened.

Please have a check in IIS on the affected Exchange server to see if the front site has a valid certificate bind.

Example:

Kelvin Cheng 20 Reputation points

2023-11-17T08:37:04.0766667+00:00

After changed the SSL certificate as Microsoft Exchange, the problem still not fix.

Kael Yao-MSFT 37,646 Reputation points Microsoft Vendor

2023-11-17T09:00:54.14+00:00

Please disable HSTS in IIS, then restart the site.

Retry enter the account and password to sign in.

If you get a warning page like this, select continue:

Kelvin Cheng 20 Reputation points

2023-11-17T09:04:38.4266667+00:00

We checked in IIS, but no setting name as HSTS.

Kael Yao-MSFT 37,646 Reputation points Microsoft Vendor

2023-11-17T09:08:21.4666667+00:00

Please try https://localhost/ecp instead of https://mail.domain.com/ecp.

If you get a warning page like:

select continue to localhost and you would be directed to https://localhost/owa/auth/logon.aspx?replaceCurrent=1&url=https%3a%2f%2flocalhost%2fecp

Then input the credentials and see if you can successfully sign in.

Kelvin Cheng 20 Reputation points

2023-11-17T09:21:49.4+00:00

Appear this error.

Kael Yao-MSFT 37,646 Reputation points Microsoft Vendor

2023-11-17T09:30:54.4033333+00:00

Have you restarted IIS site after you select "Microsoft Exchange" as the certificate?

Kelvin Cheng 20 Reputation points

2023-11-17T09:36:06.2366667+00:00

Yes, I did after select "Microsoft Exchange" as the certificate and select continue to localhost.

appear this error.

Kael Yao-MSFT 37,646 Reputation points Microsoft Vendor

2023-11-17T09:38:16.44+00:00

What about the error message in owa (https://localhost/owa)?

Kelvin Cheng 20 Reputation points

2023-11-17T09:41:21.2933333+00:00

same as above screenshot.

Kael Yao-MSFT 37,646 Reputation points Microsoft Vendor

2023-11-17T09:44:37.4033333+00:00

Please download and run the healthchecker.ps1 script as an admin in Exchange Management Shell:

https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/

Kelvin Cheng 20 Reputation points

2023-11-17T09:55:16.39+00:00

What information you need?

Kelvin Cheng 20 Reputation points

2023-11-20T07:10:04.28+00:00

Hello, is it information what you need?

Exchange IIS Information ------------------------ AppPoolName State GCServerEnabled RestartConditionSet ----------- ----- --------------- ------------------- MSExchangeMapiFrontEndAppPool Started True False MSExchangeOWAAppPool Started False False MSExchangeECPAppPool Started False False MSExchangeRestAppPool Started False False MSExchangeMapiAddressBookAppPool Started False False MSExchangeRpcProxyFrontEndAppPool Started False False MSExchangePowerShellAppPool Started False False MSExchangePowerShellFrontEndAppPool Started False False MSExchangeRestFrontEndAppPool Started False False MSExchangeMapiMailboxAppPool Started False False MSExchangeOABAppPool Started False False MSExchangePushNotificationsAppPool Started False False MSExchangeOWACalendarAppPool Started False False MSExchangeAutodiscoverAppPool Started False False MSExchangeServicesAppPool Started False False MSExchangeSyncAppPool Started True False MSExchangeRpcProxyAppPool Started False False

Kael Yao-MSFT 37,646 Reputation points Microsoft Vendor

2023-11-20T08:02:00.81+00:00

Hi,

Thanks for the update!

While I am afraid we may need to collect many information to troubleshoot this issue, which may not be suitable via forum posts.

If possible please consider contacting support by phone so they can better look into this issue.

Generally speaking, to me the cause of this issue should be the certificate bind to IIS service was removed.

However, there may be other causes involved like HSTS settings in your environment, which may require capturing network packets to troubleshoot.

Kelvin Cheng 20 Reputation points

2023-11-21T07:25:11.6266667+00:00

As you comment, the problem may be cause by HSTS setting, could you provide solution for fix the problem?
We already contact to Microsoft support by phone, but they cannot provide any solution for us. They suggest keep comment in this case and wait someone provide the solution.

Kael Yao-MSFT 37,646 Reputation points Microsoft Vendor

2023-11-21T08:36:33.68+00:00

To me without remote technical support, it's hard to resolve this issue.

While since here we provide support via forum posts, we cannot contact you by phone or email to provide instant support.

If possible I would strongly suggest contacting your Exchange vendor to see if they can help you open a support ticket.

Thanks for your understanding.

Please use packet capturing tools, for example fiddler to capture packets for the 403 error when you access EAC and OWA to see if you can find more detailed information.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Cannot access ECP and appear error "HTTP 500"

2 answers

Your answer