500 непредвиденная ошибка exchange

Имеется AD с сервером Exchange 2010, установили новый сервер, поставили Exchange 2016. 

При установке никаких ошибок нет.

Сейчас при открытии консоли ecp на новом сервере выдает ошибку 500.

На старом сервере всё открывается без проблем. 

Подскажите в чем проблема, в какую сторону смотреть?

Логи UpdateCas

[21:46:52] ***********************************************
[21:46:52] * UpdateCas.ps1: 24.09.2021 21:46:52
[21:47:03] Warning: Mailbox role is not installed on server MX1
[21:47:03] Updating OWA/ECP on server MX1
[21:47:03] Finding ClientAccess role install path on the filesystem
[21:47:03] FixUnversionedFolderAfterUpgrade: No srcVersions 15.1.2242.*
[21:47:03] Adding owin:AutomaticAppStartup appSetting with value true
[21:47:03] Updating owa handlers
[21:47:03] Adding Microsoft.Owin binding redirect
[21:47:03] Adding Microsoft.Owin.Security binding redirect
[21:47:03] Trying to add clients common module to Web.config file
[21:47:03] Adding clients common module to Web.config file
[21:47:04] Updating OWA to version 15.1.2242.4
[21:47:04] Copying files from ‘C:Program FilesMicrosoftExchange ServerV15ClientAccessowaCurrent’ to ‘C:Program FilesMicrosoftExchange ServerV15ClientAccessowa15.1.2242.4’
[21:47:07] Update OWA done.
[21:47:07] Updating OWA to version 15.1.2242.4
[21:47:07] Copying files from ‘C:Program FilesMicrosoftExchange ServerV15ClientAccessowaCurrent2version’ to ‘C:Program FilesMicrosoftExchange ServerV15ClientAccessowaprem15.1.2242.4’
[21:57:16] Update OWA done.
[21:57:17] Updating ECP to version 15.1.2242.4
[21:57:17] Copying files from ‘C:Program FilesMicrosoftExchange ServerV15ClientAccessecpCurrent’ to ‘C:Program FilesMicrosoftExchange ServerV15ClientAccessecp15.1.2242.4’
[21:57:22] Update ECP done.

Логи файла установки

[09.24.2021 19:49:04.0245] [2] Ending processing Set-ServerComponentState
[09.24.2021 19:49:04.0245] [2] Beginning processing Write-ExchangeSetupLog
[09.24.2021 19:49:04.0245] [2] Install is complete.  RecoveryActionsEnabled has been set to Active.
[09.24.2021 19:49:04.0245] [2] Ending processing Write-ExchangeSetupLog
[09.24.2021 19:49:04.0245] [2] Параметры сеанса Active Directory для ‘Set-ServerComponentState’: Просмотреть весь лес: ‘True’, Контроллер домена конфигурации: «TOR.WEW.local», Предпочтительный глобальный каталог: «TOR.WEW.local»,
Предпочтительные контроллеры домена: «{ TOR.WEW.local }»
[09.24.2021 19:49:04.0245] [2] User specified parameters:  -Component:’ServerWideOffline’ -Requester:’Functional’ -State:’Active’ -DomainController:$null -Identity:’MX1′
[09.24.2021 19:49:04.0245] [2] Beginning processing Set-ServerComponentState
[09.24.2021 19:49:04.0276] [2] Calling ADSession.GetSharedConfigDC()
Hostname of DC: TOR.WEW.local
Created a session to a DC with affinity: TOR.WEW.local

[09.24.2021 19:49:04.0385] [2] Machine:MX1 and Process:ExSetup is executing the request
Parameters — LocalOnly:[False], RemoteOnly:[False], Target:[mx1.WEW.local], Component:[ServerWideOffline], Requester:[Functional], State:[Active], DomainController:[TOR.WEW.local]
Before:[1:RecoveryActionsEnabled:Functional:1:637681097441668677,1:Monitoring:Functional:1:637681097433074280]
After:[1:RecoveryActionsEnabled:Functional:1:637681097441668677,1:Monitoring:Functional:1:637681097433074280,1:ServerWideOffline:Functional:1:637681097443231310]
Save Completed for Server Object mx1.WEW.local

[09.24.2021 19:49:04.0385] [2] Ending processing Set-ServerComponentState
[09.24.2021 19:49:04.0401] [2] Beginning processing Write-ExchangeSetupLog
[09.24.2021 19:49:04.0401] [2] Install is complete.  Server state has been set to Active.
[09.24.2021 19:49:04.0401] [2] Ending processing Write-ExchangeSetupLog
[09.24.2021 19:49:04.0401] [1] Finished executing component tasks.
[09.24.2021 19:49:04.0401] [1] Ending processing Start-PostSetup
[09.24.2021 19:49:04.0416] [0] Операция по установке Exchange Server выполнена успешно.
[09.24.2021 19:49:04.0416] [0] CurrentResult console.ProcessRunInternal:205: 0
[09.24.2021 19:49:04.0416] [0] Для применения изменений параметров операционной системы, внесенных программой установки, требуется перезагрузка. Перезагрузите сервер перед помещением его в рабочую среду.
[09.24.2021 19:49:04.0432] [0] CurrentResult launcherbase.maincore:90: 0
[09.24.2021 19:49:04.0432] [0] CurrentResult console.startmain:52: 0
[09.24.2021 19:49:04.0432] [0] CurrentResult SetupLauncherHelper.loadassembly:452: 0
[09.24.2021 19:49:04.0432] [0] CurrentResult main.run:235: 0
[09.24.2021 19:49:04.0432] [0] CurrentResult setupbase.maincore:396: 0
[09.24.2021 19:49:04.0432] [0] End of Setup
[09.24.2021 19:49:04.0432] [0] **********************************************

Hi

I would like to ask for help with Exchange 2016 installed on Windows Server 2016. I have just installed Exchange and when trying to access ECP https://localhost/owa  I am receiving an error just after type the <domain>Administrator and the password:

500 — Unexpected Error
An error occurred and your request couldn’t be completed. Please try again.

I have tried to use other accounts that also have admin rights but the same error is presented.

On the other hand, I am being able to access the OWA https://localhost/owa normally the same accounts (Administrator and others with server and exchange administrator rights)

I have experienced some issues during the installation since we have MDaemon installed on the same Server (Windows Server 2016). We have only one server in the organization and we are planning the migration from MDaemon to Exchange.

During the installation process the Exchange Transport Service was not able to start and the installation stopped with an error. After many verification I found out that since the MDaemon was running and using the port 25 is causes the Exchange installation
to stop at this step. So, I have to restart the server and start the installation again since it was not completed successfully but part of the product was installed and part not. Anyway, after successfully complete the installation we are experiencing this
error after log in in the ECP.

Any suggestion?

Thanks a lot for your help!!!

Exchange Management Console (EMC) and Exchange Control Panel (ECP) were two different interfaces used in Exchange 2010 and earlier versions to manage the Exchange Servers. With Exchange 2013, Exchange Administrative Center (EAC) — a web-based management console optimized for on-premises, hybrid, and online Exchange Server deployments—replaced EMC and ECP.

And since EAC is web-based, you need to use a web browser and require the OWA/ECP virtual directory URL to access the management console. By default, you can access the ECP/EAC console using the following URLs,

Internal URL— https://<CASServerName>/ecp

It allows users to access the EAC within the organization’s firewall.

External URL— https://mail.abc.com/ecp

It provides access to users from outside of your organization’s firewall.

Administrators and users with permission can access the EAC/ECP panel by signing in using valid credentials.

However, many users have reported an HTTP ERROR 500 after they sign in to EAC/ECP.

Reason for HTTP ERROR 500 in Exchange ECP/EAC

The HTTP ERROR 500 is usually reported after upgrading or updating the Exchange Server without an elevated command prompt.

However, it may also occur due to many other reasons, such as,

• Exchange Services stopped or not working
• Damaged OWA virtual directories
• Damaged Exchange Server
• Improper configuration
• Low Resource allocation
• Corrupt or incomplete .NET framework installation

Solutions to Fix HTTP ERROR 500 in Exchange Server

Follow these solutions in the given sequence to troubleshoot and fix the HTTP 500 error in Exchange Server EAC/ECP after login.

Solution 1: Use a Different Browser

Sometimes browser cache and cookies can cause issues while accessing the Exchange Admin Center. You can reset either the web browser or use a different browser to fix the error and access the EAC/ECP.

If you still encounter the HTTP ERROR 500, proceed to the next solution.

Solution 2: Install Pending Server Updates

On your Windows Server, open the Windows Updates section and install any pending updates as they may stop certain Exchange Services resulting in HTTP ERROR 500 after EAC login.

After the update, restart the server and then try to log in to the EAC. You may disable automatic Windows Updates to prevent HTTP ERROR 500. However, it is highly recommended to install the updates to stay protected.

If there are no pending updates but the error persists, follow the next solution.

Solution 3: Reinstall Updates

If the HTTP ERROR 500 occurred after installing the Exchange Server security updates, reinstall those using the elevated command prompt. The steps are as follows,

• Open Command Prompt as administrator
• Navigate to the location where Security updates are downloaded (.msp files) using ‘cd’ command. For instance,

cd “C:UsersUserNameDownloadsUpdates”

• Then execute the following command in the Command Prompt window,

.UpdateName.msp

• Follow the update wizard and complete the installation process.
• Restart the server and check if you can now access the EAC/ECP.

Solution 4: Check Resource Allocation

Some users have reported that the HTTP ERROR 500 occurred simply because their Exchange VM doesn’t allocate enough CPU cores. To fix this, shut down the server VM and review the allocated resources.

Add or allocate more CPU cores and RAM, if available. Restart the server and check if EAC is accessible.

Similarly, for physical servers, upgrading the hardware may fix the error. However, we recommend you follow all the troubleshooting solutions discussed in this blog before upgrading the hardware to resolve the HTTP 500 error.

Solution 5: Update Server Configurations

Improper or outdated server configuration after the server upgrade or update can also render EAC or ECP inaccessible, causing HTTP ERROR 500 after login.

In such a case, you can run UpdateConfigFiles.ps1 and UpdateCAS.ps1 PowerShell scripts located in the Exchange Server ‘Bin’ directory (C:Program FilesMicrosoftExchange ServerV15Bin) to resolve the error.

To execute these PowerShell scripts, follow these steps,

• Open PowerShell as administrator and use the ‘cd’ command to navigate the Exchange ‘Bin’ directory. For instance,

cd “C:Program FilesMicrosoftExchange ServerV15Bin.”

Then execute the following commands to run the PowerShell scripts to fix the configuration issues.

.UpdateConfigFiles.ps1

.UpdateCAS.ps1

This may take a while to finish. Once done, restart the server and check if the HTTP 500 error is resolved and ECP/EAC is accessible.

Solution 6: Recreate Virtual Directories

As a last resort, you can remove the existing OWA and ECP virtual directories and create new ones to fix the HTTP 500 error in Exchange. The steps are as follows,

• Open Exchange Management Shell (EMS) as administrator and run the following commands to remove the current OWA and ECP virtual directory

Remove-OwaVirtualDirectory –Identity “ExchangeServerNameowa (Default Web Site)”

• Press ‘a’ or ‘y’ and then press the ‘Enter’ key.

• Now execute the following command in the same EMS window to rebuild OWA virtual directory,

New-OwaVirtualDirectory –WebsiteName “Default Web Site”

The commands are case-sensitive.

This will rebuild the virtual directories and possibly fix the issue. It will also change the way you log in. Instead of the login page, you will see the following pop-up for login.

Enter username and password to log into ECP/EAC web console.

Solution 7: Repair Exchange Server

If none of the solutions worked for you, try repairing your Exchange Server. For this, you need to mount the same Cumulative Update ISO as installed on the server. Then use the following command in EMS to repair the server.

Setup /Mode:upgrade /IAcceptExchangeServerLicenseTerms

Use ‘/IAcceptExchangeServerLicenseTerms_DiagnosticDataOFF’ if your server is running on September 2021 or later Cumulative Update.

After the repair, restart the server and check if the HTTP ERROR 500 is resolved.

You may also set up a new Exchange Server if server repair fails and move your mailboxes and mail items from the old server to the new server. For this, you can use an EDB converter tool, such as Stellar Converter for EDB. The software can extract mailbox data from your faulty Exchange server with an online or offline database and export them to PST. You may also export the mailboxes from offline EDB to your new Exchange Server database to PST. The software auto-maps the source mailboxes with destination mailboxes and exports up to four mailboxes simultaneously to the target server database in a few simple steps.

Conclusion

HTTP ERROR 500 is common, especially after improper server update installation. However, it may also occur due to several other reasons, as discussed in this blog. We also discussed all possible solutions to resolve the HTTP ERROR 500 in Exchange Server 2013 and later versions. However, if the error isn’t resolved, it’s recommended to set up a new server and move your data from the faulty server to a new server using an EDB converter tool, such as Stellar Converter for EDB. The software helps you extract and move mailbox data from offline or online databases hosted on your faulty server and exports them to PST, Office 365 tenant, or Live Exchange Server. It automates the entire mailbox data migration process, saving tons of time required to manually export and import mailboxes via EMS or EAC. Moreover, the cmdlets do not work if the database is offline.

Query: “Are you getting http 500 internal server error in Microsoft Exchange 2016, 2013 and 2010 ECP/OWA after login? Don’t worry, Read this blog and get the best solution for Exchange server error 500.”

Most of the time it seems that whenever you login to your Exchange Admin centre (EAC) a common Exchange server http 500 error occurs. The main source of this problem is caused due to improper configuration of the device. The Error indicates that the device tried to establish a connection with the server, but the request was rejected with an error message by the Exchange server itself. Let’s see the solution of Exchange Server 500 error.

Method 1: Step by Step Solution for HTTP 500 Error in Exchange Server 2016

Step 1: Go to Search bar and type «Exchange Managmenent Shell».

Step 2: A new window will appear named as: Administrator: Exchange Managmenent Shell.

Step 3: It will start connecting to your local EAC ip.

Step 4: After connecting, type Remove-OwaVirtualDirectory ‘win2owa

Step 5: Message will appear “Are you sure you want to perform this action? Outlook Web App virtual directory “win2owa ” is being removed.

Step 6: Type y.

Step 7: Type New-OwaVirtualDirectory – Website Name ‘Default Web site’.

Step 8: Restart your Computer.

Step 9: Now re-login. Exchange Server http 500 Error will be fixed.

Method 2: How to Fix 500 internal server error in Microsoft Exchange

1. Create a separate virtual directory which doesn’t require SSL or any other authentication method to establish a connection with the server. In this way you could temporarily connect with the server but that might serve as a potential threat due to lack of authentication.

2. Alternatively you can enable the settings on the root Exchange directory for the front end server using Microsoft utility “Metaedit.exe”.

3. To determine the Maximum token size allotted to the user, use Microsoft provided tool : Tokensz.exe : By default the maximum token size- 8,000 bytes were allotted for the legacy versions; but for the later versions , token size was increased upto 12,000 bytes.

4. Insufficient permissions problem might be raised due to broken Access Control List inheritance in the Active Directory. To resolve this follow these steps:

• Launch Active Directory Users and Computers.
• Locate View >> Advanced Features.
• Select the mailbox and right click to explore the properties.
• Navigate to Security >> Advanced.
• Ensure that “Include inheritable permissions from this object’s parent» is selected.

5. Alternatively you can re-add the existing users and new users to the Exchange. For that you need to access Active Directory Service Information:

• Open adsi edit.
• Locate the user in your existing domain.
• Expand the user details and remove the object “CN=ExchangeActiveSyncDevices”.

Tools that could be beneficial: http://test exchange connectivity.com helps to test the connectivity between the exchange server and the device.

Exchange Remote Content Analyzer: Helps to determine the connectivity issues between the exchange server and the deployments easily.

Causes of Exchange Server HTTP 500 Error

Now let’s examine the root cause for http 500 internal server error in Exchange here:

For the legacy Exchange server versions such as Exchange 2016, 2013, 2010, 2007,etc. the 500 internal server error is caused due to the following circumstances:

The Server uses SSL or Secure Sockets Layer protocol or form based authentication.

1. Virtual Directory of the Exchange Server has disabled Windows Authentication: The Active Sync Service uses the virtual directory to access the Outlook Web Access Templates and the WebDav on the Exchange Server. Hence, If the Virtual Directory is not enabled then Active Sync returns error.

2. Members existing in too many groups might face the error as the tokens generated might be larger than the maximum size allotted to them.

3. For Exchange 2010 and later versions, the user account might not have sufficient Permissions to access the mailbox in the Active Directory.

Conclusion

In the above content, I have discussed the best solution to resolve Exchange admin center http 500 internal server error quickly. Using step by step Exchange Management Shell method easily fix Exchange server error 500 without getting any hurdle.