lesterw2
asked on
How do I fix an Exchange 2007 Topology discovery failure error 0x80040a02 (DSC_E_NO_SUITABLE_CDC)?
When I start the Exchange 2007 Active Directory Topology Service, I get the following three events in my Application Event Log:
-------------------------- ---------- ---------- -------
ERROR 10/19/2009 2:09:25 PM MSExchange ADAccess 2114 Topology
"Process MSEXCHANGEADTOPOLOGYSERVIC E.EXE (PID=4948). 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. 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."
-------------------------- ---------- ---------- -------
INFORMATION 10/19/2009 2:09:25 PM MSExchange ADAccess 2080 Topology
"Process MSEXCHANGEADTOPOLOGYSERVIC E.EXE (PID=4948). 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.MYDOMAON.local CDG 1 0 0 1 0 0 0 0 0
Out-of-site:
-------------------------- ---------- ---------- -------
INFORMATION 10/19/2009 2:09:25 PM MSExchange ADAccess 2081 Topology
"Process MSEXCHANGEADTOPOLOGYSERVIC E.EXE (PID=4948). Exchange Active Directory Provider will use the servers from the following list:
Domain Controllers:
Global Catalogs:
The Configuration Domain Controller is set to <None>. "
-------------------------- ---------- ---------- -------
The Question: https://www.experts-exchange.com/questions/23048451/Exchange-2007-The-Exchange-topology-service-did-not-return-a-suitable-domain-controller.html discusses this issue, but the answer provided eludes me. I checked all my DNS entries and they appear to be correct (including the RDNS PTR entry). However, the solution says that "a good DSAccess should look like: server1.domain.com CDG 1 7 7 1 0 1 1 7 1". How do I get my server to look like this?
ntdsutil reports for select operation target: list roles for connected server:
Server "dc1" knows about 5 roles:
Schema - CN=NTDS Settings,CN=DC1,CN=Servers ,CN=Defaul t-First-Si te-Name,CN =Sites,CN= Configurat ion,DC=MYD OMAIN,DC=l ocal
Naming Master - CN=NTDS Settings,CN=DC1,CN=Servers ,CN=Defaul t-First-Si te-Name,CN =Sites,CN= Configurat ion,DC=MYD OMAIN,DC=l ocal
PDC - CN=NTDS Settings,CN=DC1,CN=Servers ,CN=Defaul t-First-Si te-Name,CN =Sites,CN= Configurat ion,DC=MYD OMAIN,DC=l ocal
RID - CN=NTDS Settings,CN=DC1,CN=Servers ,CN=Defaul t-First-Si te-Name,CN =Sites,CN= Configurat ion,DC=MYD OMAIN,DC=l ocal
Infrastructure - CN=NTDS Settings,CN=DC1,CN=Servers ,CN=Defaul t-First-Si te-Name,CN =Sites,CN= Configurat ion,DC=MYD OMAIN,DC=l ocal
I am running Windows 2003 Server as a single Domain Controller with Exchange Server 2007 on it as well. Yes, all on the same server. There is no separate Edge server or even a backup DC (at the moment). How do I fix this topology discovery error? (Step-by-step answers are very much appreciated!). Thanks in advance.
--------------------------
ERROR 10/19/2009 2:09:25 PM MSExchange ADAccess 2114 Topology
"Process MSEXCHANGEADTOPOLOGYSERVIC
--------------------------
INFORMATION 10/19/2009 2:09:25 PM MSExchange ADAccess 2080 Topology
"Process MSEXCHANGEADTOPOLOGYSERVIC
(Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:
dc1.MYDOMAON.local CDG 1 0 0 1 0 0 0 0 0
Out-of-site:
--------------------------
INFORMATION 10/19/2009 2:09:25 PM MSExchange ADAccess 2081 Topology
"Process MSEXCHANGEADTOPOLOGYSERVIC
Domain Controllers:
Global Catalogs:
The Configuration Domain Controller is set to <None>. "
--------------------------
The Question: https://www.experts-exchange.com/questions/23048451/Exchange-2007-The-Exchange-topology-service-did-not-return-a-suitable-domain-controller.html discusses this issue, but the answer provided eludes me. I checked all my DNS entries and they appear to be correct (including the RDNS PTR entry). However, the solution says that "a good DSAccess should look like: server1.domain.com CDG 1 7 7 1 0 1 1 7 1". How do I get my server to look like this?
ntdsutil reports for select operation target: list roles for connected server:
Server "dc1" knows about 5 roles:
Schema - CN=NTDS Settings,CN=DC1,CN=Servers
Naming Master - CN=NTDS Settings,CN=DC1,CN=Servers
PDC - CN=NTDS Settings,CN=DC1,CN=Servers
RID - CN=NTDS Settings,CN=DC1,CN=Servers
Infrastructure - CN=NTDS Settings,CN=DC1,CN=Servers
I am running Windows 2003 Server as a single Domain Controller with Exchange Server 2007 on it as well. Yes, all on the same server. There is no separate Edge server or even a backup DC (at the moment). How do I fix this topology discovery error? (Step-by-step answers are very much appreciated!). Thanks in advance.
Is the server a global catalog? Exchange will only talk to itself and it must be a global catalog.
Ensure that the DNS is pointing to itself for the primary DNS - no external DNS should be configured.
Simon.
Ensure that the DNS is pointing to itself for the primary DNS - no external DNS should be configured.
Simon.
ASKER
The server is indeed configured as a Global Catalog. No external DNS is configured. I also added DC1 as a member of the Domain Admins Group. I ran a Get-ExchangeServer command from the Exchange Shell and after a long delay, it responded as follows (note the essentially empty results):
[PS] C:\Users\Administrator\Des ktop>Get-E xchangeSer ver -id dc1 -Status | fl name,current*
WARNING: An error occurred while accessing the MSExchangeADTopology service on the specified server "dc1.MYDOMAIN.local".
The error message: "The Exchange Topology service on server dc1.MYDOMAIN.local did not return a suitabledomain controller.".
Name : DC1
CurrentDomainControllers : {}
CurrentGlobalCatalogs : {}
CurrentConfigDomainControl ler :
[PS] C:\Users\Administrator\Des
WARNING: An error occurred while accessing the MSExchangeADTopology service on the specified server "dc1.MYDOMAIN.local".
The error message: "The Exchange Topology service on server dc1.MYDOMAIN.local did not return a suitabledomain controller.".
Name : DC1
CurrentDomainControllers : {}
CurrentGlobalCatalogs : {}
CurrentConfigDomainControl
Run the policytest.exe utility to find any Permission related issues
how to run policy test :
http://technet.microsoft.com/en-us/library/bb218747.aspx
how to run policy test :
http://technet.microsoft.com/en-us/library/bb218747.aspx
what about rebooting the server ........try rebooting the server
ASKER
PolicyTest.exe was a good suggestion. Rebooting the server was obvious but did not solve the problem. PolicyTest reported an error:
========================== ========== ========== =
Local domain is "mydomain.local" (MYDOMAIN)
LookupAccountName returned error 1332
Abnormal exit from PolicyTest
This seems to emphasize that for some reason Exchange is not able to figure out the domain controller, even though it is running on the same server (yes, it is a Global Catalog). Pretty much nothing runs right now so my Exchange Server is dead in the water. :-(
==========================
Local domain is "mydomain.local" (MYDOMAIN)
LookupAccountName returned error 1332
Abnormal exit from PolicyTest
This seems to emphasize that for some reason Exchange is not able to figure out the domain controller, even though it is running on the same server (yes, it is a Global Catalog). Pretty much nothing runs right now so my Exchange Server is dead in the water. :-(
looks like some network or permission issue
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Saved me.. That IPv6, what r we going 2 do.. I had it disabled also..
IP V6, I had the same problem. Thank you very much
Thank you for that insight. When the cause doesn't match the solution it is a problem MS needs to address better.
This fixed my problem too. Strangely, IPV6 has been off for years and is on most of my SBS2008 servers. But this one stopped working today and that fixed it.
I had the very same problem and this has fixed the problem. Extragely enough, the problem came after a bad system shutdown, while everyone were on hollydays, so there isn't a chance that someone could untick the IPv6 protocol from the Network Team. That means that the IPv6 protocol wasn't working before we had the issue with the exchange, and the exchange was working fine.
you might need to reboot the server