Exchange
United States (English) Sign in
Home Online 2013 2010 Other Versions Library Forums Gallery EHLO Blog
TechNet Library
Exchange
Exchange Server Tools Documentation
Operations Manager Management Pack for Exchange 2010
Common Components
Active Directory Access
Site monitor failed to start.
The configuration domain controller specified in a call to SetConfigDCName wasn't found in the Sites container in Active Directory.
Couldn't discover the Active Directory topology in a timely manner.
Collect: MSExchange ADAccess Domain Controllers: LDAP Search Time.
The Preload Filter for the DN could not be parsed. This filter will not be used.
The 'PreloadBaseDNs' and 'PreloadFilters' registry keys don't contain the same number of entries.
An RPC request to the Microsoft Exchange Active Directory Topology service failed.
An asynchronous LDAP call failed. In the absence of other events, you can ignore this one.
The Exchange topology couldn't be generated.
DSAccess failed to register an Active Directory shutdown notification with the local server.
Collect: MSExchange ADAccess Domain Controllers: LDAP long running operations/Min.
An internal error occurred. Restart the Microsoft Exchange Active Directory Topology service.
Topology discovery failed due to a LDAP error. Check the Event log for more details.
LDAP notify call failed. In the absence of other events, this event shouldn't impact mail flow. Review the Application log for related events.
The domain controller isn't running Windows Server 2003 Service Pack 1 or later.
The cache or hash table ran out of memory. Restart the Microsoft Exchange Active Directory Topology service.
Couldn't find SRV records for specified domain controller. Records may not contain correct root hints. Use Dcdiag to verify DNS server config and health.
Didn't find suitable domain controllers in local site. Check that you configured enough global catalogs. Check the Application log for ADAccess events.
LDAP Search Timeouts - sustained for 5 minutes - Yellow(>10)
LDAP Search Time - sustained for 5 minutes - Red(>100msec)
The Exchange Active Directory Provider couldn't bind to Active Directory.
A LDAP search call failed. Ignore this error if there are no related events. Review the Application log and check for network connectivity issues.
A search request that was sent to the server running Active Directory didn't provide a result within a reasonable time period.
Collect: MSExchange ADAccess Domain Controllers: LDAP Searches timed out per minute.
The Exchange Active Directory Provider didn't find any domain controllers.
Couldn't find SRV records for domain controller. The records may not be registered in DNS. Use Dcdiag to verify the DNS server configuration and health.
LDAP long running operations - sustained for 5 minutes - Red(>100)
Couldn't find SRV records for domain controller. An SRV record may be configured incorrectly in DNS. Use Dcdiag to check domain controller and DNS health.
RPC could not start.
There was an invalid configuration object found in Active Directory. The object was removed from the result set.
The maximum number of allowed processes are using DSAccess. No additional processes can use the API. Restart the Active Directory Topology service.
An error occurred when the Domain Name System (DNS) was queried for domain entries.
The Exchange Active Directory Provider failed to obtain an IP address for an Active Directory server.
The server doesn't have the Audit Security privilege on a domain controller. This privilege is used by ADAccess. Run policytest.exe. See KB 314294.
The Exchange Active Directory Provider couldn't find an available domain controller in the domain.
LDAP Search Timeouts - sustained for 5 minutes - Red(>20)
The Configuration Domain Controller specified in the registry wasn't found in the Sites container in Active Directory.
The Exchange Active Directory Provider didn't find any global catalog servers.
The Exchange Active Directory Provider couldn't contact a domain controller in the domain, but it could resolve the name.
Couldn't connect to domain controller. It won't be used by ADAccess. Check for connectivity to the domain controller and that DNS is configured correctly.
The configuration domain controller specified in a call to SetConfigDCName is unreachable.
The New Topology couldn't be generated. Make sure that the local domain controllers are reachable and running.
A request to establish a connection between the Exchange Active Directory Provider and a domain controller failed. The domain controller isn't available.
A recipient object in Active Directory isn't valid. It has been removed from the result set.
A recipient object in Active Directory isn't valid. Review the exception in MSExchange ADAccess 2156 for the cause.
Exchange failed to retrieve the local server. It's possible that the DNS name of the server has changed.
The DNS servers for the specified domain aren't responding.
LDAP Search Time - sustained for 5 minutes - Yellow(>50msec)
Site monitor failed to update the msExchServerSite attribute in AD.
The directory server specified in the registry wasn't found in the Sites container in Active Directory, so the AD Provider won't use this server.
Internal cache error. Hash table value is incorrect. Restart Active Directory Topology service or restart server. Check System log for hardware errors.
A configuration object in Active Directory isn't valid so an exception occurred.
Couldn't create the shared memory heap. This could result from internal Epoxy (ExIPC) failures or the system may be running out of memory.
A general Active Directory error occured. Review the error code in the event description to determine the cause of this error.
Consolidate: A general Active Directory error occured.
The Configuration Domain Controller specified in the registry is not available.
The Exchange Information Store cannot contact Active Directory
No global catalog server was found in the local site. Make sure that the local site has enough global catalog servers for Exchange.
Consolidate: An LDAP search call failed.
The site monitor failed in its attempt to check the current site name.
An incorrect record was used with the cache hash table.
Exchange couldn't get the SID for an account. The Exchange Active Directory Topology service will continue starting with limited permissions.
The Exchange Active Directory Provider failed to obtain DNS records for the specified domain or forest.
The Exchange Active Directory Provider couldn't read an attribute from the root DSE of the Active Directory server.
The 'Manage auditing and security log' permission is removed from the Exchange Servers group on one or more domain controllers
One or more Objects properties are pointing to Active Directory deleted objects
Related Help Topics
Loading
No resources found.
Related Blog Articles
Loading
No resources found.
Ask a question
Related Forum Discussions
Expand Minimize
This topic has not yet been rated - Rate this topic

Couldn't discover the Active Directory topology in a timely manner.

 

Topic Last Modified: 2011-08-02

The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.

To learn more about this alert, in Operations Manager, do one or more of the following:

  • From the Operations Console, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.
  • From the Operations Console, double-click this alert, and then click the Alert Context tab. Review the logged events that meet the criteria of this Operations Manager alert.

 

Product Name

Exchange

Product Version

14.0 (Exchange 2010)

Event ID

2139

Event Source

MSExchange ADAccess

Alert Type

Error

Rule Path

Microsoft Exchange Server/Exchange 2010/Common Components/Active Directory Access

Rule Name

Couldn't discover the Active Directory topology in a timely manner.

This Error event indicates that the Active Directory provider could not establish an LDAP connection to any domain controller or global catalog server in the domain within 60 seconds. This event may be logged for the following reasons:

  • Network connectivity issues
  • RPC communication issues
  • Domain controller or global catalog servers not operational

To resolve this error, do one or more of the following:

  • Use the Ping or PathPing command-line tools to test basic connectivity. Use Ping to isolate network hardware problems and incompatible configurations. Use PathPing to detect packet loss over multiple-hop trips. For more information, see Microsoft Knowledge Base article 325487, Advanced network adapter troubleshooting for Windows workstations.
  • Run the Dcdiag command-line tool to test domain controller health. To do this, run dcdiag /s:[Domain Controller Name] at a command prompt on the Exchange server. Use the output of Dcdiag to discover the root cause of any failures or warnings that it reports. For more information, see Dcdiag Overview at the Windows Server TechCenter.
  • Review the Application log for related Warning events and Error events. These related events may provide more information about the root cause of this error. For example, if MSExchangeADAccess Event ID 2152 is logged, there may be RPC communications issues.

If you are not already doing so, consider running the Exchange tools, which have been created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues and improve mail flow. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.

 
Did you find this helpful?
(1500 characters remaining)
© 2013 Microsoft
|
Site Feedback
© 2013 Microsoft. All rights reserved.