Friday, September 4, 2009

Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=916). Topology discovery failed, error SBS 2008

Problem: Exchange information store and SA is not coming up, event logs are showing topology errors, Event ID: 2114

Log Name: Application
Source: MSExchange ADAccess
Date: 9/4/2009 3:39:41 PM
Event ID: 2114
Task Category: Topology
Level: Error
Keywords: Classic
User: N/A
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=916). Topology discovery failed,
error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol
(LDAP) error code specified in the event description.

Cause :

Disabling IPV6 on the TCP/IP properties of the NIC Card will create this problem on SBS 2008 installation



Enable IPV6 on the NIC Interface



Issues After Disabling IPv6 on Your NIC on SBS 2008
Properly Disabling IPv6

SBS 2008 is designed to fully support IPv6 and has IPv6 enabled by default. Most users should never need to disable IPv6, however if you must disable IPv6 here is how to disable it properly:

Important: This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 (

  • Uncheck Internet Protocol Version 6 (TCP/IPv6) on your Network Card.
    In Registry Editor, locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\
    Double-click DisabledComponents to modify the DisabledComponents entry.
    Note If the DisabledComponents entry is unavailable, you must create it. To do this, follow these steps:
    In the Edit menu, point to New, and then click DWORD (32-bit) Value.
    Type DisabledComponents, and then press ENTER.
    Double-click DisabledComponents.
    Enter "ffffffff" (eight f’s), and then click OK:

  • Reboot the SBS 2008 server

oz Casey Dedeal,

MVP (Exchange)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +

Http:// (Blog)

Http:// (Blog)

Http:// (Blog

image image


Anonymous said...

Why disable ipv6 in the first place?

VA's RHD Hachi Roku said...

Also this can cause CAS failures during install if IPv6 is disabled.

As for WHY, well some places such as where I'm at want it off if its not in use. Policy!! that is why.

Oz Casey Dedeal said...

I don’t like having domain controller with two NIC, and therefore I used to disable, unchecked “register this connection into DNS “option on the second NIC Card on standard installation of Windows. The SBS is different animal (against best practices if you really think so) gives you Dc/Exchange/ bunch of other stuff on the same box with many limitations.
Anyways disabling NIC is not preventing DC to register dynamic records in DNS for the disabled interface anyways, and somehow this is conflicting scenario when it is SBS.
I will actually post soon why DC’s do not like more than one NIC Reasons and so forth. Back to you question it is obvious DS access is using IPV6 to access AD topology information, when IPV4 is enabled, and to be honest, I personally think it makes no sense, the process should have been smarter ( DSAccess) in Exchange 2007 and if the TCP/IP stack IPV6 is not preferred to use, it should see and not get crazy, I have to say it but I am going to conclude as poor design and not having enough simple smartness build into the process


Anonymous said...

IPv6 was Disabled. After Enableing the IPv6 the services started instantly! after restarting the transport service and information store, everything worked again.

Thank you so much!