exchnage 2016 cu18 server error in /ecp application

Maher Ramadan 286 Reputation points
2020-10-13T07:45:14.997+00:00

server error in /ecp application

An exception occurred while processing your request. Additionally, another exception occurred while executing the custom error page for the first exception. The request has been terminated.

Exchange | Exchange Server | Management
{count} votes

Accepted answer
  1. Maher Ramadan 286 Reputation points
    2020-10-29T09:41:22.983+00:00

    thank you all and sorry for my late response i was totally booked, i figured out i just need to add the version number on the url

    could it be because we have different CU levels 2016 CU 16 and Cu 18 on other servers

    https://Mailbox01/ecp/?ExchClientVer=15.

    also it seams to be a service issue as even the above url does not work sometime but that seams to be another case

    0 comments No comments

3 additional answers

Sort by: Most helpful
  1. Ashok M 6,846 Reputation points
    2020-10-13T08:04:56.153+00:00

    Hi,

    Could you please provide more information,

    1. Is this a new installation
    2. Are you getting the ECP login page while browsing https://localhost/ecp?
    3. Error message appears after providing credentials or while browsing https://localhost/ecp
    4. Does it happen to one user or all users?
    5. Is OWA working fine

    Can you check the below,

    1. Check if ECP App pool is running, try recycling it -> IIS -> ServerName -> Application Pools -> MSExchangeECPAppPool
    2. Check the Authentication, Get-ECPVirtualDirectory -Server "ServerName" | fl Identity,auth. It should be same as OWA
    0 comments No comments

  2. Henning Uhle 1 Reputation point
    2020-10-13T10:00:27.797+00:00

    Is it the case that you've recently installed an update? Let's say, CU18? In this case please check what you find in IIS Manager -> Sites -> Exchange Back End -> ecp -> Application Settings -> BinSearchFolders. It may be the case that there are incorrect information.

    How to solve?

    1. Run an elevated EMS and navigate to the scripts folder %ExchangeInstallPath%\Scripts
    2. Run the .\UpdateCas.ps1
    3. Run the .\UpdateConfigFiles.ps1

    After this, you perform an IISRESET, but WITHOUT forcing to do so. When finished, ECP should work again. I wrote a german blog article discussing this topic in March this year.

    0 comments No comments

  3. Joe Evangelista 1 Reputation point
    2021-05-03T12:47:29.48+00:00

    re-run the CU update ensure you are running in admin mode. (cmd prompt admin mode)

    0 comments No comments

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.