Control Panel Errors and Events
Applies to: Exchange Server 2010 SP3
Microsoft Exchange Server 2010 generates MSExchange Control Panel events in Event Viewer so that you can troubleshoot and verify the Exchange Control Panel features and services. Event Viewer tracks the following kinds of events in the given order based on importance:
Error events
Warning events
Informational events
MSExchange Control Panel Errors and Events
The following table provides a list of the MSExchange Control Panel errors and events.
Event ID | Category | Event type | Value or description |
---|---|---|---|
General |
Error |
The Web management interface couldn't find a mailbox for user '%1' and will let the user continue to site '%2'. This is expected for objects of type MailUser. |
|
Proxy |
Error |
Current User: '%1'Client Access server "%2" tried to proxy Web management traffic to Client Access server "%3" and received the following error for "%4":%5 |
|
Proxy |
Error |
Current User: '%1'Client Access server "%2" tried to proxy Web management traffic to Client Access server "%3". This failed because the Outlook Web App registry key "AllowInternalUntrustedCerts" is set to "0", but no certificate trusted by "%2" was available for the Secure Sockets Layer (SSL) encryption of the proxy connection. |
|
Proxy |
Error |
Current User: '%1'Client Access server "%2" tried to proxy Web management traffic to Client Access server "%3". This failed because one of the following configuration problems was encountered:1. "%3" has been set to use "http://" (not using SSL) instead of "https://" (using SSL). You can modify this by setting the InternalUrl parameter of the Web management virtual directory that this proxy traffic is going to. You can set that parameter using the Set-EcpVirtualDirectory cmdlet in the Exchange Management Shell.2. The destination virtual directory returned an HTTP 403 error code. This usually means it's not configured to accept SSL access. You can change this configuration by using Internet Services Manager on the Client Access server "%3".If you don't want this proxy connection to use SSL, set the registry key "AllowProxyingWithoutSSL" on this Client Access server and set the InternalUrl and SSL settings for the Web management virtual directory that this proxy traffic is going to accordingly. |
|
General |
Warning |
Current user: '%1'Request for URL '%2' failed with the following error:%3 |
|
Redirect |
Error |
The Web management interface couldn't redirect user '%1' from site '%2' to site '%3' and will let the user continue to the original site. The possible causes are: There are no Client Access servers on the destination site with major version equal to '%4' or the Client Access server doesn't have an external URL. |
|
General |
Warning |
Current user: '%1'Web service call '%2' failed with the following error:%3 |
|
General |
Error |
Can't determine if the current user "%1" is enabled for the RBAC role "%2". Error: "%3" |
|
Proxy |
Error |
Current User: '%1'Client Access server "%2" tried to proxy Web management traffic to Client Access server "%3". This failed because "%3" couldn't verify that the Active Directory account "%2" used to authenticate has the necessary access rights to send Web management proxy traffic. Verify in the IIS Manager that Windows Authentication is enabled in the internal 'ECP' virtual directory and that 'Get-EcpVirtualDirectory' reports 'WindowsAuthentication' as 'True' in the internal server '%3'. |
|
Proxy |
Error |
Current User: '%1'Client Access server "%2" tried to proxy Web management traffic to Client Access server "%3" but the target service wasn't available. Verify that "%2" has network connectivity with "%3", "%3" has the HTTP driver, the IIS service and IIS sites started, the "MSExchangeECPAppPool" is running, and firewall settings aren't blocking Web traffic. |
© 2010 Microsoft Corporation. All rights reserved.