ADAccess Errors and Events
Applies to: Exchange Server 2010 SP3
Microsoft Exchange Server 2010 generates MSExchange ADAccess events in Event Viewer so that you can troubleshoot and verify the ADAccessfeatures, and services. Event Viewer tracks the following kinds of events in the given order, based on importance:
Error events
Warning events
Informational events
ADAccessfeatures Errors and Events
The following table provides a list of the ADAccessfeatures errors and events.
| Event ID | Category | Event type | Value or description |
|---|---|---|---|
Topology |
Warning |
Process %1 (PID=%2). Exchange Active Directory Provider could not find any domain controller servers in either the local site '%3' or the following sites: %4 |
|
General |
Warning |
Process %1 (PID=%2). DSAccess performed disaster cleanup for the lock %3. |
|
LDAP |
Warning |
Process %1 (PID=%2). A request to Directory Server %3 did not return a result within %4 seconds and is being abandoned. The search will be retried if possible. The search that failed has the following characteristics: Base DN=%5, Filter=%6, Scope=%7. |
|
LDAP |
Warning |
Process %1 (PID=%2). DSAccess did not register an Active Directory shutdown notification with the local server, error 0x%3 (%4). To speed up the shutdown process, manually stop the Exchange services before you shut down the server. |
|
General |
Warning |
Process %1 (PID=%2). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account %3 - Error code=%4. The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions. |
|
Topology |
Warning |
Process %1 (PID=%2). Exchange Active Directory Provider failed to obtain DNS records for forest %3. DNS Priority and Weight for the Global Catalog servers in this forest will be set to the default values %4 (priority) and %5 (weight). |
|
Topology |
Warning |
Process %1 (PID=%2). Domain controller %3 was not found when DNS was queried for the service location (SRV) resource records for domain %4 The query was for the SRV record for %5 The following domain controllers were identified by the query:%6 Common causes of this error include the following: - The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller at set intervals. This computer is configured to use DNS servers with following IP addresses:%7 - One or more of the following zones do not include delegation to its child zone:%8 For information about correcting this problem, %9%10 |
|
Topology |
Error |
Process %1 (PID=%2). Topology discovery failed, error 0x%3 (%4). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers. |
|
Site Update |
Error |
Process %1 (PID=%2). The site monitor API could not start - Call=%3 Error code=%4. Try to resolve this event by restarting the computer that is running Exchange. If this event reoccurs, review the Application log and System log for any corresponding Warning or Error events. |
|
Configuration |
Warning |
Process %1 (PID=%2). The configuration domain controller specified in the registry (%3) was not found in the Sites container in the Active Directory. Exchange Active Directory Provider will select the configuration domain controller from the list of available domain controllers. |
|
Topology |
Warning |
Process %1 (PID=%2). Exchange Active Directory Provider is unable to connect to the Domain Controller %3 although its service location (SRV) resource record was found in the DNS The query was for the SRV record for %4 The following domain controllers were identified by the query:%5 Common causes of this error include: - Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses. - Domain controllers registered in DNS are not connected to the network or are not running. For information about correcting this problem, %6%7 |
|
Topology |
Error |
Process %1 (PID=%2). Active Directory topology could not be discovered in {0} seconds. Review the Application log for related Warning or Error events. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers. Run the Dcdiag command line tool to test domain controller health. |
|
Validation |
Error |
Process %1 (PID=%2). Recipient object %3 read from %4 failed validation. A data validation exception will be given. Set event logging level for Validation category to Expert to get additional events about each failure. |
|
Topology |
Warning |
Process %1 (PID=%2). No Global Catalog server was found in the local site %3. Exchange Active Directory Provider will try to find Global Catalog servers in other sites. |
|
LDAP |
Warning |
Process %1 (PID=%2). An asynchronous LDAP call failed - Server=%3 Error code=%4 (%8). Base DN=%5, Filter=%6, Scope=%7. |
|
Topology |
Error |
Process %1 (PID=%2). Error DNS_ERROR_RCODE_SERVER_FAILURE (0x%3) occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain %4 The query was for the SRV record for %5 Common causes of this error include the following: - The DNS servers used by this computer contain incorrect root hints. This computer is configured to use DNS servers with following IP addresses:%6 - One or more of the following zones contains incorrect delegation:%7 For information about correcting this problem, %8%9 |
|
Configuration |
Warning |
Process %1 (PID=%2). The configuration domain controller specified in the registry (%3) is unreachable. Exchange Active Directory Provider will select the configuration domain controller from the list of available domain controllers. |
|
Topology |
Warning |
Process %1 (PID=%2). The Exchange computer %3 does not have Audit Security Privilege on the domain controller %4. This domain controller will not be used by Exchange Active Directory Provider. |
|
Configuration |
Error |
Process %1 (PID=%2). Exchange Active Directory Provider received a request to connection to domain controller %3 but that domain controller is not available. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers. Run the Dcdiag command line tool to test domain controller health. |
|
Cache |
Error |
Process %1 (PID=%2). Internal error - A hash table that stores DSAccess information is damaged and cannot be used. This event may be caused because of internal memory issues. You may be able to resolve this event by restarting the Microsoft Exchange Active Directory Topology service. If the error persists, restart the Exchange server that logged this event. |
|
configuration |
Error |
Process %1 (PID=%2). Exchange Active Directory Provider could not read attribute %3 from Root DSE of server %4. This issue must be resolved in order to allow Exchange Active Directory Provider to correctly operate. |
|
LDAP |
Warning |
Process %1 (PID=%2). An LDAP Notify call failed - Server=%3 Error code=%4 (%8). Base DN=%5, Filter=%6, Scope=%7. |
|
Topology |
Warning |
Process %1 (PID=%2). Exchange Active Directory Provider is unable to connect to any domain controller in domain %3 although DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for that domain. The query was for the SRV record for %4 The following domain controllers were identified by the query:%5 Common causes of this error include: - Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses. - Domain controllers registered in DNS are not connected to the network or are not running. For information about correcting this problem, %6%7 |
|
Validation |
Error |
Process %1 (PID=%2). Configuration object %3 read from %4 failed validation and will be excluded from the result set. Set event logging level for Validation category to Expert to get additional events about each failure. |
|
Cache |
Error |
Process %1 (PID=%2). A cache hash table that stores DSAccess information ran out of memory. This event can be caused by internal memory issues. You may be able to resolve this event by restarting the Microsoft Exchange Active Directory Topology service. If the error persists, restart the Exchange server that logged this event. |
|
General |
Error |
Process %1 (PID=%2). An remote procedure call (RPC) request to the Microsoft Exchange Active Directory Topology service failed with error %3 (%4). Make sure that the Remote Procedure Call (RPC) service is running. In addition, make sure that the network ports that are used by RPC are not blocked by a firewall. |
|
Topology |
Error |
Process %1 (PID=%2). Exchange Active Directory Provider could not find an available domain controller in domain %3. This event may be caused by network connectivity issues or configured incorrectly DNS server. This event may also occur if you have not configured correctly your multiple Active Directory sites. |
|
topology |
Warning |
Process %1 (PID=%2). The configuration domain controller specified in a call to SetConfigDCName (%3) is unreachable. Exchange Active Directory Provider will select the configuration domain controller from the list of available domain controllers. |
|
Topology |
Warning |
Process %1 (PID=%2). The configuration domain controller specified in a call to SetConfigDCName (%3) was not found in the Sites container in the Active Directory. Exchange Active Directory Provider will select the configuration domain controller from the list of available domain controllers. |
|
General |
Error |
Process %1 (PID=%2). DSAccess could not initiate a remote procedure call (RPC) - Call=%3 Error code=%4. |
|
General |
Error |
Process %1 (PID=%2). The shared memory heap could not be created. This may be caused if physical memory limits have been exceeded. It may also be caused if too many other processes are running DSAccess. You may be able to resolve this error by restarting the Exchange server that logged this event. |
|
Topology |
Error |
Process %1 (PID=%2). Exchange Active Directory Provider couldn't find any Global Catalog servers in either the local site '%3' or the following sites: %4 |
|
Site Update |
Error |
Process %1 (PID=%2). The site monitor API could not update the msExchServerSite attribute in Active Directory. You must update this attribute to reflect new site name where this Exchange server is installed - Call=%3 Error code=%4. |
|
Configuration |
Error |
Process %1 (PID=%2). DSAccess could not discover the Fully Qualified Domain Name (FQDN) of local server with Exception %3. The local name that was used to look up the server is %4. This event may be caused by an incorrectly configured DNS server. It may also occur if the local server was renamed but DNS records were not updated. To resolve this error, see "Troubleshooting DNS servers" in the Microsoft Windows Server TechCenter. In addition, if the name of the server that logged this event was changed, make sure that the computer was restarted. |
|
Configuration |
Warning |
Process %1 (PID=%2). The domain controller specified in the registry (%3) was not found in the Sites container in Active Directory. Exchange Active Directory Provider will not use this server as a domain controller or global catalog. |
|
Topology |
Error |
Process %1 (PID=%2). Topology discovery failed due to LDAP_SERVER_DOWN error. This event can occur if one or more domain controllers in local or all domains become unreachable because of network problems. Use the Ping or PathPing command line tools to test network connectivity to local domain controllers. Run the Dcdiag command line tool to test domain controller health. |
|
Topology |
Warning |
Process %1 (PID=%2). No Domain Controller server was found in the local site %3. Exchange Active Directory Provider will try to find Domain Controller servers in other sites. |
|
Validation |
Error |
Process %1 (PID=%2). Configuration object %3 read from %4 failed validation. DataValidationException will be thrown. Set event logging level for Validation category to Expert to get additional events about each failure. |
|
Topology |
Warning |
Process %1 (PID=%2). Exchange Active Directory Provider failed to obtain DNS records for domain %3. DNS Priority and Weight for the Domain Controllers in this domain will be set to the default values %4 (priority) and %5 (weight). |
|
Cache |
Error |
Process %1 (PID=%2). An internal memory cache error occurred. A record that was not valid was used with the cache hash table. This event can be caused by internal memory issues. You may be able to resolve this event by restarting the Microsoft Exchange Active Directory Topology service. If the error persists, restart the Exchange server that logged this event. |
|
Topology |
Error |
Process %1 (PID=%2). Exchange Active Directory Provider failed to obtain an IP address for DS server %3, error %4 (%5). This host will not be used as a DS server by Exchange Active Directory Provider. |
|
Topology |
Error |
Process %1 (PID=%2). Error DNS_ERROR_RCODE_NAME_ERROR (0x%3) occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain %4 The query was for the SRV record for %5 Common causes of this error include the following: - The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller at set intervals. This computer is configured to use DNS servers with following IP addresses:%6 - One or more of the following zones do not include delegation to its child zone:%7 For information about correcting this problem, %8%9 |
|
Site update |
Error |
Process %1 (PID=%2). The site monitor API was unable to verify the site name for this Exchange computer - Call=%3 Error code=%4. Make sure that Exchange server is correctly registered on the DNS server. |
|
Configuration |
Error |
Process %1 (PID=%2). The 'PreloadBaseDNs' and 'PreloadFilters' registry keys do not contain the same number of entries. 'PreloadBaseDNs' contains %3 strings and 'PreloadFilters' contains %4 strings. Only the first %5 preload filters will be used. Each entry in PreloadBaseDNs registry key must match an entry in PreloadFilters registry key. To resolve this error, make sure that number of entries in PreloadBaseDNs registry key equals the number of entries in PreloadFilters registry key. |
|
Topology |
Error |
Process %1 (PID=%2). Error 0x%3 occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain %4 The query was for the SRV record for %5 For information about correcting this problem, %6%7 |
|
LDAP |
Error |
Process %1 (PID=%2). Could not bind to DS server %3, error %4 (%6) at port %5. |
|
General |
Error |
Process %1 (PID=%2). Error %3 occurred, code 0x%4. Callstack 0x%5 0x%6 0x%7 0x%8 0x%9 0x%10 0x%11 0x%12 |
|
General |
Error |
Process %1 (PID=%2). The Preload Filters registry key '%3' for the DN '%4' could not be parsed. The error is %5 (%6). This filter will not be used. To resolve this error, make sure that filter specified in PreloadFilters registry key is valid. For more information, see Microsoft Knowledge Base article 250572, "XCON: Preloading and the DSAccess Cache." |
|
Validation |
Warning |
Process %1 (PID=%2). Recipient object %3 read from %4 failed validation and will be excluded from the result set. Set event logging level for Validation category to Expert to get additional events about each failure. |
|
Cache |
Error |
Process %1 (PID=%2). An internal memory cache error occurred. A hash table iterator is no valid. This event can be caused by internal memory issues. You may be able to resolve this event by restarting the Microsoft Exchange Active Directory Topology service. If the error persists, restart the Exchange server that logged this event. |
|
LDAP |
Warning |
Process %1 (PID=%2). An LDAP search call to Directory Server %3 failed - Error code=%4 (%8). Base DN=%5, Filter=%6, Scope=%7. |
|
Topology |
Warning |
Process %1 (PID=%2). The domain controller %3 is running Windows %4 %5. Exchange Active Directory Provider requires that domain controllers are running Windows Server 2003 Service Pack 1 or later versions of Windows. |
|
Topology |
Error |
Process %1 (PID=%2). Exchange Topology could not be discovered. Reason: %3. |
|
General |
Error |
Process %1 (PID=%2). The maximum allowed number of processes are using the DSAccess memory cache. No more processes can use the API. Try to resolve this event by restarting the Microsoft Exchange Active Directory Topology service. If the error persists, restart the Exchange server that logged this event. |
|
Topology |
Warning |
Process %1 (PID=%2). Error ERROR_TIMEOUT (0x%3) occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain %4 The query was for the SRV record for %5. The DNS servers used by this computer for name resolution are not responding. This computer is configured to use DNS servers with the following IP addresses:%6. Verify that this computer is connected to the network, that these are the correct DNS server IP addresses, and that at least one of the DNS servers is running. For information about correcting this problem, %7%8 |
|
Cache |
Information |
Process %1 (PID=%2). The specified record key does not exist in the cache hash table. |
|
Cache |
Warning |
Process %1 (PID=%2). The last record in the cache hash table was found. |
|
General |
Information |
Process %1 (PID=%2). DSAccess initialized successfully. |
|
Topology |
Information |
Process %1 (PID=%2). Exchange Active Directory Provider lost contact with domain controller %3. Error was 0x%4 (%6) (%5). Exchange Active Directory Provider will attempt to reconnect with this domain controller when it is reachable. |
|
LDAP |
Information |
Process %1 (PID=%2). A search or read to Directory Server %3 returned object '%4' which has attribute '%5' with too many values to return in a single search. If possible, reduce the number of values in this attribute to allow normal operation. |
|
General |
Information |
Process %1 (PID=%2). DSAccess is shutting down. |
|
Topology |
Information |
Process %1 (PID=%2). Exchange Active Directory Provider will use the servers from the following list: Domain Controllers:%3 Global Catalogs:%4 The Configuration Domain Controller is set to %5. |
|
Topology |
Information |
Process %1 (PID=%2). Exchange Active Directory Provider has detected that the following Domain Controller servers in the local site '%3' became reachable and is using them: %4 |
|
Topology |
Information |
Process %1 (PID=%2). Exchange Active Directory Provider has detected that the following Global Catalog servers in the local site '%3' became reachable and is using them: %4 |
|
Topology |
Warning |
Process %1 (PID=%2). No Domain Controller server is up in the local site '%3'. Exchange Active Directory Provider will use the following out of site Domain Controller servers: %4 |
|
Topology |
Information |
Process %1 (PID=%2). No Global Catalog server is up in the local site '%3'. Exchange Active Directory Provider will use the following out of site global catalog servers: %4 |
|
Configuration |
Information |
Process %1 (PID=%2). The value of %3 specified in the registry must be in the range of %4 - %5, and it was %6. Using the default value of %7. |
|
Configuration |
Information |
Process %1 (PID=%2). Exchange Active Directory Provider will use Domain Controllers specified in the registry. |
|
Configuration |
Information |
Process %1 (PID=%2). Registry key 'SYSTEM\CurrentControlSet\Services\MSExchange ADAccess\Diagnostics' is missing. Exchange Active Directory Provider cannot get a list of event log categories. Only events of level 'None' will be logged. |
|
Topology |
Information |
Process %1 (PID=%2). The Configuration Domain Controller has been changed from %3 to %4. |
|
Configuration |
Information |
Process %1 (PID=%2). Exchange Active Directory Provider will use the Configuration Domain Controller (%3) specified in the registry. |
|
Topology |
Error |
Process %1 (PID=%2). All Domain Controller Servers in use are not responding: %3 |
|
Topology |
Warning |
Process %1 (PID=%2). All Global Catalog Servers in forest %3 are not responding: %4 |
|
Configuration |
Information |
Process %1 (PID=%2). Exchange Active Directory Provider will use Global Catalogs specified in the registry. |
|
Topology |
Information |
Process %1 (PID=%2). Exchange Active Directory Provider will use the Configuration Domain Controller (%3) specified in a call to SetConfigDCName. |
|
LDAP |
Error |
Process %1 (PID=%2). Received LDAP error 0x%3 (%5) from Directory Server %4 due to Kerberos ticket timeout. |
|
Topology |
Information |
Process %1 (PID=%2). Exchange Server %3 now has Audit Security Privilege on Domain Controller %4. |
|
LDAP |
Error |
Process %1 (PID=%2). Exchange Active Directory Provider needs to close a connection to the Domain Controller %3 due to error 0x%4 (%5). |
|
General |
Information |
Process %1 (PID=%2). Impersonated account %3 is calling into Exchange Active Directory Provider with the following callstack: %4 %5 %6 %7 %8 %9 %10 %11 |
|
Cache |
Warning |
Process %1 (PID=%2). An attribute on object %3 is too large to be cached. Requested size was %4, maximum cacheable is %5. Performance may be degraded. |
|
Topology |
Information |
Process %1 (PID=%2). Exchange Active Directory Provider detected that Active Directory server %3 is reachable again via port %4. |
|
Configuration |
Information |
Process %1 (PID=%2). Object %3 was not found on the Domain Controller %4. This may indicate a replication or permission issue. |
|
Topology |
Information |
Process %1 (PID=%2). Exchange Active Directory Provider needs a Domain Controller in domain %3. Found server %4. |
|
LDAP |
Information |
Process %1 (PID=%2). Opening new connection to server %3 at port %4. Connection pool: %5. |
|
LDAP |
Information |
Process %1 (PID=%2). Closing connection to the server %3 at port %4. |
|
LDAP |
Warning |
Process %1 (PID=%2). An LDAP %3 operation succeeded but took %4 milliseconds - Server=%5. Base DN=%6, Filter=%7, Scope=%8. |
|
LDAP |
Information |
Process %1 (PID=%2). Exchange Active Directory Provider received change notification for '%3'. |
|
Configuration |
Information |
Process %1 (PID=%2). Exchange Active Directory Provider found multiple records for %3. Locate and fix the affected recipients to resume mail flow. |
|
General |
Information |
Process %1 (PID=%2). Process preferred topology changed. Preferred Domain Controllers: %3 Preferred Global Catalog: %4 Preferred Configuration Domain Controller: %5 |
|
Topology |
Error |
Process %1 (PID=%2). Topology discovery failed, error 0x%3. |
|
Topology |
Warning |
Process %1 (PID=%2). Error occurred when getting server from domain Distinguished Name: %3. ADAM topology provider is not available. Please make sure Microsoft Exchange ADAM service is started. |
|
Topology |
Information |
Process %1 (PID=%2). The following Active Directory servers are going to be used in connection pools of this process: Domain Controllers: %3 Global Catalogs: %4 Configuration Domain Controller: %5. Topology Version %6, Topology provider: %7. |
|
General |
Information |
Process %1 (PID=%2). Microsoft.Exchange.Data.Directory.dll is loaded successfully. |
|
LDAP |
Information |
Process %1 (PID=%2). Attribute %3 of '%4' had %5 values and required ranged read operations on Directory Server %6. |
|
Validation |
Warning |
Process %1 (PID=%2). Configuration object %3 read from %4 failed validation. A partially valid object will be returned. Set the event logging level for Validation category to Expert to get additional events about each failure. |
|
Validation |
Information |
Process %1 (PID=%2). Recipient object %3 read from %4 failed validation. A partially valid object will be returned. Set event logging level for Validation category to Expert to get additional events about each failure. |
|
Exchange Topology |
Information |
Process %1 (PID=%2). Two servers with the same fully qualified domain name have been detected. Only %3 will be considered and %4 will be ignored. |
|
LDAP |
Information |
Process %1 (PID=%2). DSAccess registered an Active Directory shutdown notification on the local server. |
|
LDAP |
Information |
Process %1 (PID=%2). DSAccess failed to register an Active Directory shutdown notification with the local server because the local server does not support shutdown notifications. To expedite the shutdown process, manually shut down Exchange services before shutting down the server. |
|
LDAP |
Error |
Process %1 (PID=%2). An LDAP search call returned a referral - Server=%3 Error code=%4 (%8). Base DN=%5, Filter=%6, Scope=%7. |
|
Exchange Topology |
Information |
Process %1 (PID=%2). Server %3 is not assigned to any site. This can be caused by incorrect configuration of subnets or sites or by replication latency. Server will not be used. |
|
General |
Information |
Process %1 (PID=%2). Impersonated account %3 is calling into Exchange Active Directory Provider and allowed. |
|
General |
Information |
Process %1 (PID=%2). Function %3 failed indicating that the remote procedure call (RPC) server is temporarily unavailable - Error code=%4. |
|
Site update |
Information |
Process %1 (PID=%2). Site monitor updated msExchServerSite in Active Directory. New site: %3 Old site: %4 |
|
General |
Error |
Process %1 (PID=%2). Failed to flush Kerberos ticket for local system account - Error code=%3. Microsoft Exchange Active Directory Topology service could not update token to have Exchange Servers group membership (SID: %4). This may be caused by replication latency. Wait for replication to complete and try again. |
|
General |
Information |
Process %1 (PID=%2). The Microsoft Exchange Active Directory Topology Service has started successfully. |
|
General |
Information |
Process %1 (PID=%2). The Microsoft Exchange Active Directory Topology Service has stopped successfully. |
|
Topology |
Information |
Process %1 (PID=%2). %3 is a read-only domain controller. Exchange Active Directory Provider requires that domain controllers are not read-only. |
|
General |
Information |
Process %1 (PID=%2). Default throttling policy for organization '%3' is missing. |
|
General |
Information |
Process %1 (PID=%2). Multiple default throttling policies found for organization '%3'. |
|
General |
Information |
Process %1 (PID=%2). Unable to initialize throttling performance counters. The exception was: '%3' |
|
General |
Information |
Process %1 (PID=%2). Failed to read throttling policy with ID '%3'. The exception was: '%4' |
|
General |
Information |
Process %1 (PID=%2). Dynamic distribution group %3 read from %4 is not valid.%5. |
|
General |
Information |
Process %1 (PID=%2). Coudn't find a global address list for user '%3' (SID='%4') |
|
General |
Information |
Process %1 (PID=%2). Deleted throttling policy was referenced. Id: '%3'. |
|
General |
Information |
Process %1 (PID=%2). Component: %3. Unable to initialize resource health performance counters. Exception: '%4' |
|
General |
Information |
Process %1 (PID=%2).The concurrency controller for resource '%3' detected that a thread stayed in the overflow queue for more than %4 milliseconds, which is a warning that the resource might be unhealthy. |
|
General |
Information |
Process %1 (PID=%2).The concurrency controller for resource '%3' detected that the overflow queue has reached its warning limit of %4. |
|
General |
Information |
Process %1 (PID=%2). The recipient full sync page token for tenant '%3' has been cleared from storage. |
|
General |
Information |
Process %1 (PID=%2) Component %3. Encountered a timeout while trying to access remote performance counter '%4'. Remote server might be unresponsive. |
|
General |
Information |
Process %1 (PID=%2) Component %3. Encountered an exception while trying to read remote performance counter '%4'. Exception: '%5'. |
|
Validation |
Information |
Process %1 (PID=%2). Object [%3]. Property [%4] is set to value [%5], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible. |
|
General |
Information |
Process %1 (PID=%2).The Concurrency controller detected that Resource '%3' reached its concurrency limit and therefore the resource is set to unhealthy |
|
General |
Information |
Process %1 (PID=%2). Unable to find UM Allowed CountryList. Id: '%3'. |
© 2010 Microsoft Corporation. All rights reserved.