Http error 500 exchange 2016

Симптомы

При отправке в X-OWA-UrlPostData в среде Exchange Server 2013 или Exchange Server 2016 искаженной JSONRequest, отчеты об ошибках Outlook Web Access может отвечать на запросы с ошибку HTTP 500 OwaSerializationException. Кроме того при использовании такого средства, как Fiddler или Burp комплект сканера, вы можете получить верхней части стека вызовов, похожее на следующее:

{«Тело»: {«Код ошибки»: 500, «ExceptionName»: «OwaSerializationException», «FaultMessage»: «не удается десериализовать объект типа FindConversationJsonRequest»,»IsTransient»:false,»StackTrace»:»Microsoft.Exchange.Clients.Owa2.Server.Core.OwaSerializationException: не удается десериализовать объект типа FindConversationJsonRequest—> System.Runtime.Serialization.SerializationException: элемент»: корень «содержит данные из типа, который сопоставляется с именем «http:////schemas.contoso.com/2004/07/Exchaasdadnge:FindConversationJsonRequest».

Примечание. Эта проблема может быть уязвимости злоумышленник, прошедший проверку удаленного доступа к важной информации.

Информация о накопительном пакете обновления

Для Exchange Server 2013

Для Exchange Server 2016

Статус

Корпорация Майкрософт подтверждает, что это проблема продуктов Майкрософт, перечисленных в разделе «Относится к».

Ссылки

Дополнительные сведения о терминологии , которую корпорация Майкрософт использует для описания обновлений программного обеспечения.

Продукты независимых производителей, обсуждаемые в этой статье, производятся компаниями, независимыми от корпорации Майкрософт. Корпорация Майкрософт не дает никаких явных или подразумеваемых гарантий относительно производительности или надежности этих продуктов.

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.

Отчеты об ошибках OWA выдает ошибку HTTP 500 OwaSerializationException

Симптомы

При отправке в X-OWA-UrlPostData в среде Exchange Server 2013 или Exchange Server 2016 искаженной JSONRequest, отчеты об ошибках Outlook Web Access может отвечать на запросы с ошибку HTTP 500 OwaSerializationException. Кроме того при использовании такого средства, как Fiddler или Burp комплект сканера, вы можете получить верхней части стека вызовов, похожее на следующее:

Примечание. Эта проблема может быть уязвимости злоумышленник, прошедший проверку удаленного доступа к важной информации.

Информация о накопительном пакете обновления

Для Exchange Server 2013

Чтобы устранить эту проблему, установите Накопительное обновление 14 для Exchange Server 2013 или более поздней версии накопительного обновления для Exchange Server 2013.

Для Exchange Server 2016

Чтобы устранить эту проблему, установите Накопительное обновление 3 для 2016 Exchange Server или более поздней версии накопительного обновления для Exchange Server 2016.

Статус

Корпорация Майкрософт подтверждает, что это проблема продуктов Майкрософт, перечисленных в разделе «Относится к».

Ссылки

Дополнительные сведения о терминологии , которую корпорация Майкрософт использует для описания обновлений программного обеспечения.

Продукты независимых производителей, обсуждаемые в этой статье, производятся компаниями, независимыми от корпорации Майкрософт. Корпорация Майкрософт не дает никаких явных или подразумеваемых гарантий относительно производительности или надежности этих продуктов.

Источник

Http error 500 exchange 2016

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

After a crash on the Exchange server and an abnormal reboot, there was a problem with ECP access. There were errors in the journal. At the same time OWA works! The «Distribution groups» page is not yet displayed in the mail options in the Web version of Outlook with Error 500. I managed to enter the ECP administration center via the link https://mailkenk.ru/ecp/?ExchClientVer=15 but this does not always work. Restarting the server does not fix the error

Log Name: Application

Source: MSExchange Control Panel

Date: 23/08/2017 8:55:29

Task Category: General

Current user: ‘KEKGuskov’

Request for URL ‘https://ex02.kek.kemnet.ru:444/ecp/DDI/DDIService.svc/GetList?ActivityCorrelationID=4d30293d-6e44-4e0c-a276-0c34b585a6b0&reqId=1503453329340&workflow=GetCount&ua=0&schema=Notification&msExchEcpCanary=Pd9hFx7TlkGA1434eQYxB3CJfamo59QI2rXLqQczq-nKOcfh02DnrSL6xNTPvrEDRl-H_tV3z9Q.(https://mailkenk.ru/ecp/DDI/DDIService.svc/GetList?ActivityCorrelationID=4d30293d-6e44-4e0c-a276-0c34b585a6b0&reqId=1503453329340&workflow=GetCount&ua=0&schema=Notification&msExchEcpCanary=Pd9hFx7TlkGA1434eQYxB3CJfamo59QI2rXLqQczq-nKOcfh02DnrSL6xNTPvrEDRl-H_tV3z9Q.)’ failed with the following error:

System.TypeInitializationException: Инициализатор типа «Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor» выдал исключение . —> System.InvalidOperationException: Не удается загрузить данные имени счетчика , поскольку в реестре обнаружен недопустимый индекс «».

в System.Diagnostics.PerformanceCounterLib.GetStringTable(Boolean isHelp)

в System.Diagnostics.PerformanceCounterLib.CategoryExists(String machine, String category)

в System.Diagnostics.PerformanceCounterCategory.Exists(String categoryName, String machineName)

— Конец трассировки внутреннего стека исключений —

в Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor.LogActivity(CounterType counterType, String organizationName)

в Microsoft.Exchange.Management.ControlPanel.AuthenticationSettings..ctor(HttpContext context)

в Microsoft.Exchange.Management.ControlPanel.RbacModule.Application_PostAuthenticateRequest(Object sender, EventArgs e)

в System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

в Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor.LogActivity(CounterType counterType, String organizationName)

в Microsoft.Exchange.Management.ControlPanel.AuthenticationSettings..ctor(HttpContext context)

в Microsoft.Exchange.Management.ControlPanel.RbacModule.Application_PostAuthenticateRequest(Object sender, EventArgs e)

в System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

System.InvalidOperationException: Не удается загрузить данные имени счетчика, поскольку в реестре обнаружен недопустимый индекс «».

в System.Diagnostics.PerformanceCounterLib.GetStringTable(Boolean isHelp)

в System.Diagnostics.PerformanceCounterLib.CategoryExists(String machine, String category)

в System.Diagnostics.PerformanceCounterCategory.Exists(String categoryName, String machineName)

в System.Diagnostics.PerformanceCounterLib.GetStringTable(Boolean isHelp)

в System.Diagnostics.PerformanceCounterLib.CategoryExists(String machine, String category)

в System.Diagnostics.PerformanceCounterCategory.Exists(String categoryName, String machineName)

Flight info: Features:[[Global.DistributedKeyManagement, False],[Global.FrontdoorDefaultURL, False],[Global.GlobalCriminalCompliance, False],[Global.MultiTenancy, False],[Global.PopulateGroupMasterSid, False],[Global.WindowsLiveID, False],[Eac.AllowMailboxArchiveOnlyMigration, True],[Eac.AllowRemoteOnboardingMovesOnly, False],[Eac.AllowSender, False],[Eac.AntiSpamBulkThresholdUI, False],[Eac.AntispamTenantAllowBlockLists, False],[Eac.BulkPermissionAddRemove, True],[Eac.CaseHoldQuery, False],[Eac.CaseHoldSearch, False],[Eac.CmdletLogging, True],[Eac.ComplianceAllPublicFolderSearch, False],[Eac.ComplianceCase, False],[Eac.ComplianceCaseClosing, False],[Eac.ComplianceCaseSources, False],[Eac.ComplianceExportIndividualMessageFormat, False],[Eac.ComplianceMnc, False],[Eac.ComplianceSearchRefiners, False],[Eac.ComplianceSearchStatistics, False],[Eac.ConditionCards, False],[Eac.ConditionCardsForCaseHoldQuery, False],[Eac.ConvertMailboxUI, False],[Eac.CrossPremiseMigration, False],[Eac.CustomizableMaxMsgSizeUI, True],[Eac.CutomizableSenderAuthenticationInNewDistributionGroup, False],[Eac.DevicePolicyMgmtUI, False],[Eac.DiscoveryDocIdHint, False],[Eac.DiscoveryMultiHoldSearch, False],[Eac.DiscoveryMultiQuerySearch, False],[Eac.DiscoveryMultiQueryV2Export, False],[Eac.DiscoveryPFSearch, True],[Eac.DiscoverySearchStats, False],[Eac.DiscoveryV1Export, True],[Eac.DistributionToUnifiedGroupMigrationEac, False],[Eac.DKIMSigningConfigUI, False],[Eac.DLPBlockForUnifiedCompliance, False],[Eac.DlpFingerprint, False],[Eac.DlpPolicyDetailsAndError, False],[Eac.DLPUnifiedCompliancePreview, False],[Eac.DLPWarnForUnifiedComplianceAvailability, False],[Eac.EACClientAccessRulesEnabled, False],[Eac.EacFeedbackControl, False],[Eac.EacPswsProxy, False],[Eac.EDiscoveryEacDecommisionExemption, True],[Eac.EdiscoveryExportPaging, False],[Eac.EdiscoveryExportV2AnalyzeWithZoom, False],[Eac.EdiscoveryExportV2ClientExportToolLiteEngine, False],[Eac.EdiscoveryExportV2General, False],[Eac.EdiscoveryHold, False],[Eac.EdiscoveryPreviewSearchUI, True],[Eac.EdiscoverySearchUI, False],[Eac.ExportDedupe, False],[Eac.ExportReportOnly, False],[Eac.FileFilter, False],[Eac.GeminiShell, False],[Eac.GrantSendOnBehalfToForSharedMailbox, False],[Eac.HoldForModernGroups, False],[Eac.InactiveMailboxForCaseHold, False],[Eac.InactiveMailboxSearch, False],[Eac.IsDedicatedTenant, False],[Eac.ManageMailboxAuditing, False],[Eac.ModernGroupCreateOnBehalfOf, False],[Eac.ModernGroupDelegatedUserSupport, False],[Eac.ModernGroupDomainSelectionSupport, False],[Eac.ModernGroupEnableDeliveryManagement, False],[Eac.ModernGroupManagement, False],[Eac.ModernGroupMoreEditOptions, False],[Eac.ModernGroupNonMailboxUserSupport, False],[Eac.ModernGroups, False],[Eac.ModernGroupsAllowCreationByNonAADAdmin, False],[Eac.ModernGroupsPromotion, False],[Eac.ModernGroupsSendOnBehalfOf, False],[Eac.NewAuditingOptInUIOptIn, True],[Eac.NewAuditingReportUIOptIn, True],[Eac.NonExchangeWorkloadsUI, False],[Eac.Office365DIcon, False],[Eac.OrgIdADSeverSettings, False],[Eac.PreviewQuarantineMessage, False],[Eac.PreviewQuarantineMessageAdvanced, False],[Eac.PreviewSnapshotSearchUI, False],[Eac.PromoteProtectionCenter, False],[Eac.ProtectionCenterForceRedirect, False],[Eac.ProtectionCenterOptIn, False],[Eac.ProtectionCenterOptOut, False],[Eac.PublicFolderHoldManagement, False],[Eac.RemoteDomain, False],[Eac.SafeAttachments, False],[Eac.SafeAttachmentsDynamicDelivery, False],[Eac.SafeLinks, False],[Eac.SafeLinksScanUrls, False],[Eac.ShowExternalStorageWarningInGCC, False],[Eac.SingleFolderExport, False],[Eac.SPOPickerSearchAllTenantContent, False],[Eac.SupervisoryReview, False],[Eac.SupportAdfsIdentityInEcpProxy, False],[Eac.TestTransferToE164Extension, False],[Eac.ToggleABQWarning, False],[Eac.UCCAlertsReportingUI, False],[Eac.UCCAuditReports, False],[Eac.UCCIngestionUI, False],[Eac.UCCPermissions, False],[Eac.UCCTestProbeUI, False],[Eac.UnifiedAuditPolicy, False],[Eac.UnifiedAuditReportUI, False],[Eac.UnifiedComplianceCenter, False],[Eac.UnifiedDlpGA, False],[Eac.UnifiedPolicy, True],[Eac.UnifiedRetention, False],[Eac.UnlistedServices, True],], Flights:[], Constraints:[[MACHINE, EX02],[MODE, ENTERPRISE],[PROCESS, MSEXCHANGEECPAPPPOOL],], IsGlobalSnapshot: True

Log Name: Application

Source: MSExchange Configuration Core

Date: 08/23/2012 8:57:12

Task Category: (1)

I can not find a description for event ID 1 from the MSExchange Configuration Core source. The component that triggers this event is not installed on this local computer or is corrupt. Install or restore the component on the local computer.

If the event occurred on another computer, you might need to save the displayed information along with the event.

The following information was added to the event:

Exception from CmdletHealthCountersModule.Task_Release: System.TypeInitializationException: An initializer of type «Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor» threw an exception. —> System.InvalidOperationException: The counter name data could not be loaded because an invalid index «» was found in the registry.

In System.Diagnostics.PerformanceCounterLib.GetStringTable (Boolean isHelp)

In System.Diagnostics.PerformanceCounterLib.CategoryExists (String machine, String category)

In System.Diagnostics.PerformanceCounterCategory.Exists (String categoryName, String machineName)

— End of internal stack trace of exceptions —

In Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor.LogActivity (CounterType counterType, String organizationName)

In Microsoft.Exchange.ProvisioningMonitoring.PerTenantCmdletHealthCounters.UpdateSuccessCount (ErrorRecord errorRecord)

In Microsoft.Exchange.Configuration.Tasks.CmdletHealthCountersModule.IncrementSuccessCount (ErrorRecord errorRecord)

In Microsoft.Exchange.Configuration.Tasks.CmdletHealthCountersModule.Task_Release (Object sender, EventArgs e)

In Microsoft.Exchange.Configuration.Tasks.CriticalFeatureHelper.Execute (ICriticalFeature feature, Action action, TaskContext taskContext, String methodNameInLog)

A message resource exists, but the message was not found in the row table and message table

In the output of some commands, there was also an error, for example:

[PS] C: Windows system32> get-mailbox-Arbitration

Name Alias ​​ServerName ProhibitSendQuota

Migration.8f3e7716-201 . Migration.8f3e771 . ex02 300 MB (314,572,800 bytes)

FederatedEmail.4c1f4d8 . FederatedEmail.4c . ex02 1 MB (1,048,576 bytes)

OAB Mailbox oabmbx3 ex02 Unlimited

WARNING: The task module «CmdletHealthCountersModule.Task_IterateCompleted» failed with the exception «Type initializer

«Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor» threw an exception. «This module will be skipped.

The result of the task will not be violated.

WARNING: The task module module «CmdletHealthCountersModule.Task_Release» failed with the exception «Type initializer

«Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor» threw an exception. «This module will be skipped.

The result of the task will not be violated.

Источник

Http error 500 exchange 2016

Вопрос

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 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.

Thanks a lot for your help.

Все ответы

According to your description, I know that you failed login ECP with 500 error if install MDaemon and Exchange server on same server, however OWA works fine.

To narrow down your issue, please ensure:
1. All Exchange services work fine.s
2. Ensure all Exchange server components work fine:
Get-ServerComponentstate -Identity «servername»
If the state is Inactive, please run below command to active relevant component:
Set-ServerComponentState -Component «component name» -Requester HealthAPI -State Active

Then, open IIS manager then switch to Application Pools, right-click MSExchangeECPAppPool and select View Applications, then check the path for «/ECP».
Meanwhile, check the Binding and Path for Default Web Site and Exchange Back End site.

Otherwise, open Event Viewer and check whether there’s any error message about Exchange server, post the details for further assistance.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Hi Allen, thank you for your reply.

I just went thru the steps that you provided and these are the results:

After run Get-ServerComponentstate -Identity » » command I found that two services were inactive:

ForwardSyncDaemon Inactive
ProvisioningRps Inactive

So I ran the commands as you described:

Set-ServerComponentState Server -Component «ProvisioningRps» -Requester HealthAPI -State Active

Set-ServerComponentState Server -Component «ForwardSyncDaemon» -Requester HealthAPI -State Active

After this I was able to check that all services were active.

I tried to logon in the ECP but still getting the same error (erro 500).

I have checked all the information on IIS and everything was exactly as displayed in the pictures that you provided. Paths, binding, Application pool, everything was there!

About EventViewer: When trying to find the issue I have saved all previous events and clean the logs at «Applications and Services Logs > MSExchange Management» so now, after trying the steps that you have provided the only events that are available are the informational ones about the commands to active the services «ForwardSyncDaemon» and «ProvisioningRps» as you can see below:

Cmdlet suceeded. Cmdlet Set-ServerComponentState, parameters -Component «ForwardSyncDaemon» -Requester «HealthAPI» -State «Active» -Identity «Server».

Cmdlet suceeded. Cmdlet Set-ServerComponentState, parameters -Component «ProvisioningRps» -Requester «HealthAPI» -State «Active» -Identity «Server».

Any other suggestion?

Thanks again for your help and time. Have a nice week!

However, for Exchange testing, (Autodiscover and Connectivity) you can use Microsoft’s TestConnectivity site to help troubleshoot your issues: https://testconnectivity.microsoft.com

Also get help from below earlier thread:

Hope this helps!

Migrate mailboxes, Public Folders, Outlook profiles and rules and GAL etc. to-and-fro Exchange Servers and Office 365 with LepideMigrator for Exchange

Hi Allen and Eduardo,

According to the description I strugel with the same error, also is my setup the same.

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

During the installation process noting went wrong the installation completed successfully.

Hope you have any suggestion?

Thanks a lot for help

Thanks for your cooperation.

The previous Event log is more helpful to troubleshooting this issue. Can you open those saved log in Event Viewer, then check the error?

Meanwhile, please open IIS log (default location: C:inetpublogsLogFilesW3SVC1) then find more information about this error.

Furthermore, try to recreate ECP VD for testing:
1. Run below command to list all ECP VD：
Get-EcpVirtualDirectory -ShowMailboxVirtualDirectories | FL Identity,*Site*,*URL*,*Auth*

2. Then remove and recreate:
Remove-EcpVirtualDirectory -Identity «MYSERVERecp (Default web site)»
New-EcpVirtualDirectory -Server SERVER01 -ExternalURL https://mail.contoso.com/ecp -InternalURL https://mail.contoso.com/ecp

@Jeroen, do you experience same situation as Eduardo?
In order to avoid confusion and keep track of troubleshooting steps, I recommend create your own thread. Glad for your cooperation.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

I just import the previous logs again. I have errors there related to the previous installations issue that I have mentioned when I have created this thread so. What should I try to look for ? I have tried to search using the keywords «500» and «ecp» but nothing was found. Any suggestion?

I tried to run the command Get-EcpVirtualDirectory -ShowMailboxVirtualDirectories | FL Identity,*Site*,*URL*,*Auth* and below you have the results:

Shoul I still try to Remove and Recreate the ECP Virtual directories?

Finally, bellow you have the IIS logs but I also didn’t find anything related to the erro (at least it is not clear for me that is something related to the error so, I will wait the final word from the Expert 😉 )

Note: For security reasons my manager asked me to remove the server name so, I have replace it with in the log bellow

Источник

After doing a new install of Exchange 2016 on Windows Server 2016 I go to https://ex1/ecp, attempt to log in and get:

This page isn’t working ex1 is currently unable to handle this request.
HTTP ERROR 500

I have removed and create a new OwaVirtualDirectory, I have checked to make sure the groups that EX1 is a part of is not a part of Domain Admins, Schema Admins, Enterprise Admins, Organization Admins.

Running Get-OwaVirtualDirectory | FL Identity,auth,URL returns:

Identity                      : EX1owa (Default Web Site)
ClientAuthCleanupLevel        : High
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           : {}
InternalSPMySiteHostURL       :
ExternalSPMySiteHostURL       :
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
ExternalUrl                   :

I can see that no internal or external URLs are showing which I think may be related to the problem, but don’t know what to do for sure.

The only oddities in the install were:

1. During the first install there were errors that I had to fix (Windows Updates), after updates and reboot I attempted to reinstall through the GUI but it erred thinking it was already installed and I had to reinstall using cmd.
2. I manually added the domain administrator account (as well as my other admin account) to schema admins and enterprise admin groups for the install.
3. I unfortunately don’t remember the error, but during install through cmd, there was some message that popped up saying that something in IIS wasn’t setup, like a * http redirect I think? I don’t know and I’ve since rebooted so can’t scroll back to see it again. I feel like this is causing the issue.

EDIT:

I have now also tried running UpdateCas.ps1 with no success as well as the following:

Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -FormsAuthentication $False -BasicAuthentication $True
Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -FormsAuthentication $True -BasicAuthentication $True
Get-EcpVirtualDirectory | Set-EcpVirtualDirectory -FormsAuthentication $false -BasicAuthentication $true
Get-EcpVirtualDirectory | Set-EcpVirtualDirectory -FormsAuthentication $true -BasicAuthentication $true
iisreset

As well as:

Get-EcpVirtualDirectory | Set-EcpVirtualDirectory -FormsAuthentication $false -BasicAuthentication $true -WindowsAuthentication $true
Get-OWAVirtualDirectory | Set-OWAVirtualDirectory -FormsAuthentication $false -BasicAuthentication $true -WindowsAuthentication $true
iisreset
Recycle MSExchangeECPAppPool
Recycle MSExchangeOWAAppPool

Event Viewer shows Event ID 1023:

Exchange ActiveSync tried to access a mailbox on Mailbox server "EX1.mydomain". It could not access the mailbox because the Mailbox server is offline.

I feel that this must be the answer, I haven’t had a chance to configure any mailbox datastores so the administrator would be in the default one. I cannot however locate how to find and mount this. Any ideas?