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 Path Ping command-line tools to test network connectivity to local domain controllers.
Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents ( in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
The Exchange Active Directory Topology service will continue with limited permissions.
Event Type: Error Event Source: MSExchange ADAccess Event Category: General Event ID: 2501 Description: Process MSEXCHANGEADTOPOLOGY (PID=4600).
3: Also we can run on the DC as well as from Exchange.Note: if you have multiple DC while running /s:dcname In this case, if we had an environment of Exchange 2003, 2007, and 2010.The Exchange 20 servers, with the exception of one Exchange 2007 mailbox server, were throwing errors such as these: Event Type: Error Event Source: MSExchange ADAccess Event Category: Topology Event ID: 2114 Description: Process MSEXCHANGEADTOPOLOGYSERVICE. Topology discovery failed, error 0x80040952 (LDAP_LOCAL_ERROR (Client-side internal error or bad LDAP message)).Some of these errors include: Log Name: Application Source: MSExchange ADAccess Date: 13/08/2012 AMEvent ID: 2114Task Category: Topology Level: Error Keywords: Classic User: N/AComputer: Exchange2010.domain.local Description: Process STORE. Topology discovery failed, error 0x80040952 (LDAP_LOCAL_ERROR (Client-side internal error or bad LDAP message)).Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description.