Once we did this, all of the Exchange Servers now worked properly.
Heres another interesting Exchange case that I came across recently. Topology discovery failed, error 0x80040952 (LDAP_LOCAL_ERROR (Client-side internal error or bad LDAP message)).
At this point, the next thing done was to look for a recent 2080 event and see what the Exchange server was seeing as far as domain controllers were concerned. So, then the question was why is it missing, and this is what trips up many people, and is the reason I decided to write this.
The 2080 looked like this: Event Type: Information Event Source: MSExchange ADAccess Event Category: Topology Event ID: 2080 Description: Process MSEXCHANGEADTOPOLOGYSERVICE. Exchange Active Directory Provider has discovered the following servers with the following characteristics: (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version) In-site: dc1.domain. Whenever I get one of these cases, the first thing I like to do is go to one of the Domain Controllers and run Resultant Set of Policy (RSOP. We then drill down to the User Rights Assignment, as seen below.
Use the Ping or Path Ping command-line tools to test network connectivity to local domain controllers.
The above event may have the following error instead: Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC).
Status Bar = "" End Sub You can suppress the Waning alerts by disabling the display alerts.
This was because the Default Domain Controllers Policy link had been removed from the OU and the Default Domain Policy was being applied instead.The site monitor API was unable to verify the site name for this Exchange computer - Call=Hr Search Error code=80040a01.Make sure that Exchange server is correctly registered on the DNS server. COM CDG 1 7 7 1 0 0 1 7 1 For well-versed Exchange folks, the problem in this 2080 is fairly obvious, the Exchange server is missing the SACL (Manage auditing and security log) right on the DC’s.Calculation = xl Calculation Automatic Application. If this does happen, you may need to repeat the line: Application.Here are the example codes to control the Events, Screen Updating, Progress Bar, Display Alerts and other Application Objects.In this case, the customer 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)).Screen Updating property is useful when running macros that jump from cell to cell, sheet to sheet, and workbook to workbook.Screen Updating to False stops your screen from flickering (refreshing) as your macro runs.(Edited 8/8/2011 to add additional error that might be found in the 2114 description.This is something I’ve ended up having to resolve multiple times with customers, so I felt it would be good to get a post out about it.