Thanks for this! Investigating now.
From: [email protected] [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: June-17-14 1:46 PM To: [email protected] Subject: [Exchange] RE: Event ID 2114 Right. Because the newer DFL has stronger constraints. Are all your subnets defined? Are all your Exchange servers in a defined subnet? Are all your DCs in a defined subnet? Are the DCs in either the same subnet or a covering subnet of your Exchange servers? Does Exchange determine a DynamicSiteName on boot? Do you have a sitename defined in the registry? When you do a "Get-ExchangeServer -status" are the proper DCs located? Are any DCs identified statically? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Tammy George Sent: Tuesday, June 17, 2014 12:28 PM To: '[email protected]' Subject: [Exchange] RE: Event ID 2114 Thanks. We did follow a similar process in 2011 when we setup the DCs. Unfortunately, nothing stands out in this article as something we missed at that time. Exchange just recently started having this issue (past 2 weeks). From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: June-17-14 12:42 PM To: [email protected]<mailto:[email protected]> Subject: [Exchange] RE: Event ID 2114 No... more like the first part of this: http://windows-scripting.org/2011/06/22/how-to-configure-active-directory-sites-and-replication/ although PLEASE ignore everything in this article from "Configuring Active Directory Replication" to the end of the article. Those recommendations do not follow best practices. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Tammy George Sent: Tuesday, June 17, 2014 11:23 AM To: '[email protected]' Subject: [Exchange] RE: Event ID 2114 Thank you. By verify AD site configuration, should I follow this article http://support.microsoft.com/kb/298143? I ask because our AD servers were installed/configured in 2011. We raised the domain functional level to 2008 R2 recently as we just noticed a month ago that it was still 2003. We're running Exchange 2010 (since June 2010). From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: June-17-14 12:12 PM To: [email protected]<mailto:[email protected]> Subject: [Exchange] RE: Event ID 2114 I would recommend that you verify your AD site configuration. Strongly recommend. You don't say your Exchange version. But I can tell you that no testing is done with Exchange 2010 or Exchange 2013 with IPv6 disabled. There are a couple of situations in which IPv6 needs to be disabled for Exchange 2007, but it should be disabled in the registry, not on the NIC. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Tammy George Sent: Tuesday, June 17, 2014 11:05 AM To: '[email protected]' Subject: [Exchange] Event ID 2114 Hi all. We recently raised our domain functional level to Windows 2008 R2. On June 3, 11 and 15, our Exchange server was inaccessible to users. A reboot resolved the problem. The following events were logged on each of those days - Event 2114 Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1504). 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. 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. Event 2130 Process w3wp.exe () (PID=2644). Exchange Active Directory Provider could not find an available domain controller in domain xyz. 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. Event 2102 Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1504). All Domain Controller Servers in use are not responding: dc1.xyz dc2.xyz Searching found hits for 2114 but with other errors and not 2130 and 2102. Any suggestions or pointers would be greatly appreciated! BTW - Today I discovered IPv6 was disabled on the network adapter but not in the registry. Since it doesn't need to be disabled, I've re-enabled. Any chance this is related? Thanks!
