HTTP ERROR 500 in Hybrid Exchange ECP/EAC

A_Lop 41 Reputation points
2023-05-25T17:10:42.2+00:00

Hello, I need assistance opening my Exchange Hybrid (Microsoft Exchange Server 2013 Cumulative Update 23) ECP browser. I get an error "The website cannot display the page This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem that prevented the webpage from displaying. For more information about HTTP errors, see Help." My path is https://<server name>/ecp/ExchClientVer=15 . I've turned on all the Microsoft Exchange services. My EMS is working and only the ECP is not. I also tried a different browser like Google and had the same result "This page isn't working, <server name> is currently unable to handle this request HTTP ERROR 500." Exchange Hybrid is running on Windows Server 2012 R2 (VM) and also has IIS.

Finally, (Separate question) is it possible to use Exchange Management Shell on a Local Machine remotely? For example, install EMS on my Windows 10 machine and work from there instead of logging on directly to the Exchange Hybrid to open the EMS. Is there an EMS tool that I can download and install in my local machine?

Your input is greatly appreciated. Thanks.

Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
2,165 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Dezhi Li-MSFT 790 Reputation points
    2023-05-26T06:36:49.1066667+00:00

    Hi @A_Lop ,

    Colud you please tell me if your owa can access normally?

    1. When accessing ecp fails, please check the application log for Event ID 1309. This issue occurs if SharedWebConfig.config is missing from either of the following locations:C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxyC:\Program Files\Microsoft\Exchange Server\V15\ClientAccess.Event ID 1309 and you can't access OWA and ECP after you install Exchange Server 2016 or Exchange Server 2013 - Exchange | Microsoft Learn
    2. You can try to check whether the path under BinsearchFolder of ECP Virtual directory is correct in IIS Manager. If not, please modify it and use the UpdateConfigFiles.ps1 and UpdateCAS.ps15 PowerShell scripts to update the server configuration.OWA or ECP stops working after you install a security update - Exchange | Microsoft Learn

    下载

    1. Finally you can try to re-create/reset the IIS virtual directories.

    https://theitbros.com/recreate-owa-ecp-virtual-directories-exchange-server-2016/

    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    You can install Exchange 2013 management tools on other devices, but there is no win10 among the supported operating systems.

    https://learn.microsoft.com/en-us/exchange/install-the-exchange-2013-management-tools-exchange-2013-help,

    https://learn.microsoft.com/en-us/exchange/exchange-2013-system-requirements-exchange-2013-help#supported-operating-systems-for-exchange-2013

    下载 (1)

    On win10 you can use power shell to connect to Exchange servers and run Exchange commands.

    https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-servers-using-remote-powershell?view=exchange-ps

    下载 (2)

    Best Regards,

    Dezhi


    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](https://aka.ms/msftqanotifications)"https://aka.ms/msftqanotifications)") to enable e-mail notifications if you want to receive the related email notification for this thread.  


  2. Amit Singh 4,986 Reputation points
    2023-05-26T08:32:07.84+00:00

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.