500 unexpected error exchange

Today we faced an issue in accessing ECP through an admin delegated account and got the below error. we thought of writing up a blog with few general checklists that can be performed if you come across this kind of issue.

Below are the troubleshooting steps that can be performed in this order if you come across issues with accessing the ECP virtual directory.

1) Check if there is any issue with the XAML file type.

Find the file located in:

C:Program FilesMicrosoftExchange ServerV15ClientAccessecpDDIRemoteDomains.XAML

If you have any staging servers with the same version where it is working, just copy this XML file or if you could find this file from the setup just replace with the existing one. Do an IIS Reset and see the results.

2) Check on the Application Pools to view whether OWA and ECP Application Pool is running on .NET Framework v4.0. It may be an incomplete or corrupted installation of Framework that causes this error.

You might come across the above if you recently made any recent upgrade or it’s a fresh installation.

If that’s the case try to run the following command as Administrator:

%windir%Microsoft.NETFrameworkv4.0.30319aspnet_regiis.exe -i

Change the MSExchangeECPAppPool from .NET Framework from v4.0 to v2.0. Then restart IIS and check the results.

3) Check the bindings of the default website to confirm to Microsoft recommended settings:

({http port 80 *}{http port 80 127.0.0.1}
{https port 443 *}{https port 443 127.0.0.1})

4) If none of the above steps works try recreating the ecpvirtualdirectory and see the results.

In EMS, please run the following command:

Remove-Ecpvirtualdirectory –Identity “CASAutodiscover (xxxxx)”

New-Ecpvirtualdirectory –Identity “CASAutodiscover (xxxxx)”

There are more cases where even recreating the ECP virtual directory or any virtual directory will still cause this same error 500 unexpected error.

This is because of the stale entries present in the ECP objects as well as in the IIS metabase.

If recreating corresponding affected VD doesn’t help you then try the below steps.

Remove the newly created ECP virtual directory:

Remove-Ecpvirtualdirectory –Identity “CASAutodiscover (xxxxx)”

5)  Remove the ECP objects in AD container.

a. Open ADSIEDIT.msc, locate:

Configuration–>CN=Services–>CN=Microsoft Exchange–>CN=Organization–>CN=Administrative Groups–>CN=Exchange Administrative Groups–>CN=Servers–>CN=Exchange–>CN=Protocols–>CN=HTTP

b. In the right pane, please check whether the CN=ECP(xxx) is present. If it’s present you can remove it.

6. Delete the AutoDiscover in metabase.

a. Download the IIS 6.0 Resource Kit Tools from the following link:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628-ade629c89499&displaylang=en

b. Install it on the CAS server. Open the “Metabase Explorer” (Open it in elevated mode).

c. Locate: Exchange -> LM -> W3SVC -> 1 -> ROOT.

d. Check if you are able to find ECP virtual directory is present. If so, remove it.

7. After that, try recreating the ECP virtual directory and see the results:

New-Ecpvirtualdirectory –Identity “CASAutodiscover (xxxxx)”

Most likely after following the above troubleshooting steps the affected ECP VD should start working. You can also follow the same troubleshooting steps if in case you are getting the same error in accessing the OWA, EAC, Autodiscover and PowerShell Virtual
Directories.

Hope this article is helpful.

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.

«500 Unexpected Error» when trying to create a user mailbox in Exchange admin center

Symptoms

When users who have the Recipient Management role use the Exchange admin center to create user mailboxes, they receive the following error message:

An error occurred and your request couldn’t be completed. Please try again.

Membership in the Recipient Management role group enables users to do administrative tasks, such as creating and modifying Exchange recipient objects.

Cause

This problem is caused by an internal change that was applied in Microsoft Exchange Server 2019 Cumulative Update 9 (CU9) and Microsoft Exchange Server 2016 Cumulative Update 20 (CU20).

Resolution

This issue is fixed in Microsoft Exchange Server 2019 CU10 and Microsoft Exchange Server 2016 CU21. Update your servers to one of these CUs or a later CU to fix the issue.

If you cannot upgrade to the current CU, use one of the methods in the «Workaround» section.

Workaround

To work around this problem, use one of the following methods.

Method 1

Add the affected users to the following additional management role group:

View-Only Organization Management

Method 2

Create a new management role that’s based on the «View-Only Configuration» management role. To do this, run the following command:

New-ManagementRole -Name VOC1 -Parent «View-Only Configuration»

Remove all other management role entries, and keep only «Get-RemoteDomain»:

Get-ManagementRoleEntry VOC1* | Where-Object <$_.Name -ne «Get-RemoteDomain»>| Remove-ManagementRoleEntry

Assign the new role to all users who are members of the «Recipient Management» management role group:

New-ManagementRoleAssignment -User John.Doe -Role VOC1

Method 3

Have users use the Exchange Management Shell (EMS) to run the New-Mailbox and Enable-Mailbox operations.

Источник

Microsoft Exchange Server Made Easy

Exchange Guide is the complete encyclopedia for all the possible queries related to MS Exchange Server . Contains expert solutions , tips , tricks and explanations to frequently asked terms/questions.

Label overview

Total Pageviews

Blog Archive

Wednesday, October 17, 2018

Fixed Exchange Server HTTP 500 Internal Error — 2016 | 2013 | 2010

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.

Источник

Internal error exchange server

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.

Источник

Today i faced an issue in accessing ecp  through an admin delegated account and got the below error. I thought of writing up a blog with few general checklists that can be performed if we come across this kind of issues.

Below are the troubleshooting  steps that can be performed in this order if we come across  issues with accessing the ECP virtual directory.

1) Check if there is any issue with the XAML file type

Find the file located in

C:Program FilesMicrosoftExchange ServerV15ClientAccessecpDDIRemoteDomains.XAML

If you have any staging servers with the same version where it is working just copy this XML file or if you could find this file from the setup just replace with the existing one do an iis reset and see the results

2) Check on the Application Pools to view whether OWA and ECP Application Pool is running on .NET Framework v4.0. It maybe the incompletely or corrupted installation of Framework that causes this error.

You might come across the above if you recently made any recent upgrade or its a new fresh installation.

If that’s the case try to run the following command as Administrator:

%windir%Microsoft.NETFrameworkv4.0.30319aspnet_regiis.exe -i

Change the MSExchangeECPAppPool from .NET Framework from v4.0 to v2.0. Then restart IIS and check the results.

3) Check the bindings of the default website to confirm to Microsoft recommended settings:

({http port 80 *}{http port 80 127.0.0.1}
{https port 443 *}{https port 443 127.0.0.1})

4) If none of the above steps works try recreating the ecpvirtualdirectory and see the results

 In EMS, please run the following command:

Remove-Ecpvirtualdirectory –Identity “CASAutodiscover (xxxxx)”

New-Ecpvirtualdirectory –Identity “CASAutodiscover (xxxxx)”

There are more cases where even recreating the ECP virtual directory or any virtual directory will still cause this same error 500 unexpected error

This is because of the stale entries present in the ecp objects as well as in the IIS metabase.

If recreating corresponding affected VD doesn’t help you then  try the below steps

Remove the newly created ECP virtual directory

Remove-Ecpvirtualdirectory –Identity “CASECP(xxxxx)”

5)  Remove the ecp objects in AD container

a. Open ADSIEDIT.msc, locate:

Configuration–>CN=Services–>CN=Microsoft Exchange–>CN=Organization–>CN=Administrative Groups–>CN=Exchange Administrative Groups–>CN=Servers–>CN=Exchange–>CN=Protocols–>CN=HTTP

b. In the right pane, please check whether the CN=ECP(xxx) is present. If its present you can remove it.

6. Delete the autodsicover in metabase

a. Download the IIS 6.0 Resource Kit Tools from the following link:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628-ade629c89499&displaylang=en

b. Install it on the CAS server. Open the “Metabase Explorer” (Open it in elevated mode)

c. Locate: Exchange -> LM -> W3SVC -> 1 -> ROOT.

d. Check if you are able to find ECP virtual directory  is present, if so, remove it.

7. After that, try recreating the ECP virtual directory and see the results

New-Ecpvirtualdirectory –Identity “CASAutodiscover (xxxxx)”

Most likely after following the above troubleshooting steps the affected ECP VD should start working. You can also follow the same troubleshooting steps if in case  you are getting the same error in accessing the OWA,EAC ,Autodiscover and PowerShell Virtual Directories.

Hope this article is helpful

Thanks 

Sathish Veerapandian

MVP – Exchange Server