Exchange 07: Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC)
Environment for this issue: Exchg 2007 Win2008 SP1 & 2 Domain controllers Win2003 SP2
If your exchange installation was working and then suddenly stopped working with the error below.( Try this if your having an installation issue to, allthough this specific issue appeared after it was working fine for a few months).
(Some services won’t start ??)
Microsoft Exchange Active Directory Topology Service
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=3268). 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.
Goto Active directory on your domain Controller and add your exchange server as a 'Computer' on the 'Domain Admins Group'. Thanks to cchalmer on this aswell.
This worked fantastically for me with a reboot.
Also you can ref:
Please use this at your discretion as its not an official solution only a different suggestion to address your problem and not ideal from a privacy point of view. I have other alternatives in this blog which may address your problem without going down this road.
Comments
Anonymous
January 06, 2009
PingBack from http://www.codedstyle.com/exchange-07-topology-discovery-failed-error-0x80040a02-dsc_e_no_suitable_cdc/Anonymous
January 24, 2009
I also received this error, and found that it was the result of disabling IPV6 on my server's only NIC. When I reenabled IPV6 on the NIC and rebooted, the services started normally and re-running the installation worked perfectly. This is the article that helped me determine this... http://msmvps.com/blogs/ehlo/archive/2008/06/12/1634433.aspx BTW, this article also references a way to complete disable IPV6 to resolve the issue, but I just enabled IPV6 on my NIC and allowed a dynamic IP address (not recommended - but I am not using IPV6, so the resolvability of the address is not a big concern for me).Anonymous
April 27, 2009
It works for me thanks. I would only know why!?! Maybe a policy problem? I would remove this entry from domain admins...is not "clean"...Anonymous
May 12, 2009
For Paul Martin, thank you very much for your input, I wasted a lot of time to search on Microsoft web site, MS is not as good as your simple answer, great work!Anonymous
July 07, 2009
The comment has been removedAnonymous
July 07, 2009
Yes thanks Mike for the comment, I agree, this is 'not' recommended or official and has possible issues with privacy, I have listed elsewhere in this blog other ways to address the problem which manifests in different forms. This is a suggestion and use it at your discretion. Thanks again KeithAnonymous
July 28, 2009
I agree, adding the computer to the Domain Admins is not the best solution, but it's the only one I was able to get to work. (Server 2008 STD SP2, Exchange 2007SP1 w/Rollup9) I first started seeing this after installing Server 2008 Service Pack 2. I have IPV6 implemented, but tried disabling/re-enabling IPV6 to no avail. I also tried: http://support.microsoft.com/kb/919089 (troubleshooting 2114 errors) with no luck either, all policy settings were as they should be. I am now successfully using IPV4 and IPV6 with no errors. It's an ugly fix, but something M$ should have addressed by now. Thanks again for the tipAnonymous
July 29, 2009
Delighted it helped Gordon;-)Anonymous
August 19, 2009
I think by enabling IPV6 in the network properties will fix the problem. Give that a goAnonymous
September 01, 2009
Re-Enabling IPV6 worked for us.Anonymous
September 09, 2009
I found that the Exchange Server was not a member of the "Exchange Servers" security group on the DC. Added it, rebooted the Exchange Server. Working!!!! Perhaps this is better than adding to the Domain Admins group??? Thanks for the tip.Anonymous
September 28, 2009
Same Happened to me... Windows 2008 SP2 with Exchange 2007 SP2. Reenabled IPv6 and it didn't worked... I had to put the computer accounts in the domain admins group and restart the servers. Any new solution for this? I think that my costumer won't like that solution... :( ThanksAnonymous
September 28, 2009
I made again a setup.exe /preparead and all worked fine (without having the machine accounts in the domain admins group) Greetings!Anonymous
October 08, 2009
The comment has been removedAnonymous
October 19, 2009
Win2008 SP1 and Exch 2007 sp1 (32 bit) Same error was occouring..... I tried adding the computer account to Domain admins group but no luck atleast for my scenario. Then I enabled IPV6 and tried the same..... It worked Thanks a lot :)Anonymous
November 13, 2009
Enabling IPV6 and a reboot worked for me. I was installing Exchange 2007 SP1 on Windows 2008.Anonymous
November 23, 2009
on my case, I had the Topology discovery failed error, I ran setup.com /preparedomain on the 2007 exchange server and it corrected the AD permissions again. It worked all right!Anonymous
February 25, 2010
I recently took over management of an Exchange 2007 on Windows 2008 environment and was having this issue after I applied SP2 and RU2. Placing the servers in the domain admins group did fix the problem short term, but I wanted the correct fix. I tried enabling IPv6 and still had the topology load issue. Exchange 2007 on Server 2008 uses IPv6 so having it on is probably a good idea anyway so I left it on. To correct the permission failure that caued the topology load error, I added the exchange servers security group to the "Manage auditing and security log" group through the local security policy editor. This process is provided for information only, if you choose to follow it, it is at your own risk. Start > run > secpol.msc Expand Local Policies Click User Rights Assignment Locate "Manage auditing and security log" Add "exchange Servers" to this group. You should now be able to bring your mail database online. The correct fix for this is probably to re-run setup.com /adprep from one of your exchange servers. But this fix worked for me withou re-running /adprep.Anonymous
March 17, 2010
I was recovering a deleted Server, got the same message during setup. I just had to put the server back in AD Group "Install Exchange Domain Servers" and reboot.Anonymous
March 22, 2010
Enabling IPV6 and a reboot worked for us. I was installing Exchange 2007 SP1 on Windows 2008 SP2.Anonymous
March 22, 2010
Adding the computer account to domain admins worked great! Thanks!Anonymous
March 28, 2010
The comment has been removedAnonymous
June 21, 2010
The Exchange 2010 servers (All Roles) should be in the Exchange Trusted SubSystem group. This group is in turn a member of the Administrators group. This way you dont need to add them to Domain Admins group. -Same issue, all was working well as we upgraded from Exchange 2003 to 2010. As soon as the Exchange 2003 uninstall was complete, we started getting the same errors. I found this blog, and it got me looking into the security group issues. The uninstall process must have removed all exchange objects from the correct security groups. I checked another migration from 2007 - 2010 that we had done, and sure enough all Exchange 2010 servers were in the Exchange Trusted Subsystem Group, and that was a member of Administartors group. Added the group nesting in our broken scenario and rebooted - Bingo..! Thx allAnonymous
July 05, 2010
IPV6 and Domain Admins Fixed my issueAnonymous
August 08, 2010
The comment has been removedAnonymous
August 09, 2010
Thanks, I find the good information for Microsoft Exchange Active Directory Topology Service.Anonymous
September 20, 2010
Hey! Enabling of IPV6 only helped me as a magic! ...It was very frustrating, trying to fix the problem, came from "nowhere"! Thanks!Anonymous
October 01, 2010
i have server 2008 32Bit snd had the same eror. i jost enable ipV6 and it work properly. thaneks!Anonymous
October 14, 2010
same problem was after windows updates. Excellent!! Enabled IPv6 worked!! Adding computer to Domain Admins didnt help for me. Thanks! I've spent a lot of time before founded this good post.Anonymous
November 23, 2010
This problem may occur if you use MS ISA. Open the 'flood migration "and enter the name of your exchange server to the list of exceptions. Best regards.Anonymous
December 25, 2010
Thanks for this tip. I just started having this issue today after backing up my Exchange 2007 Vmware image. I was thinking there was something that had corrupted my Vmware image. Adding the computer to Domain Admins seems to have solved it.Anonymous
June 26, 2011
Thanks a lot!! It got fixed when I enabled the IPv6 protocol back on the nic.Anonymous
July 20, 2011
You can fix this issue by granting READ permissions on Domain Controller objects in Active Directory for group "Exchange Servers", or by executing /preparedomain setup command. "Domain Admins" is too much for Exchange Servers, certainly. Also, IPv6 is totally unrelated to this issue.Anonymous
August 14, 2012
Thank You, I appriciate this very helpful article! Enabling IPV6 solved the problem.Anonymous
September 24, 2012
Hi Martin.....i waste lots of time...and finally ur blog is worked on my exchange alsoAnonymous
December 03, 2012
This worked for me! Thank you so much! I am not sure if it was re-enabling IPv6 or adding DC to the domain admins group. Either way, both of those worked for me. Thank you for contributing.Anonymous
January 16, 2013
Hey Gents, Enabling IPv6 did it again. Thank you so much ofr the people who contributed to this blog.Anonymous
March 23, 2013
The comment has been removedAnonymous
March 23, 2013
The comment has been removedAnonymous
June 15, 2013
Re-enabling IPv6 worked for me!Anonymous
October 25, 2013
I had disabled three NIC cards i the offending server. after reading comments, I re-enabled them. I cleared the messages and for the last 50 minutes have had no topology messages. Thanks for the suggestions.Anonymous
November 02, 2013
Thank you for this. It worked as soon as I added the computer to the group. Saved the day. Gratitude.Anonymous
November 19, 2013
Just wanted to say a BIG THANKS for turning my attention to the IPv6! I had sh*tloads of errors, and the exchange transport service wouldn't start. I've been at it for 9 hours more or less, and it's now 4am. I just enabled IPv6 (still wonder why/when it got disabled) and everything got back to normal, and I can finally sleep!!!!! Many, many, many thanks!!!! /UffeAnonymous
December 09, 2013
You are the man! worked a treat. I renabled IPv6 and added server to Domain Admins Group.Anonymous
December 29, 2013
Thx a lot Celtic-Guy ! You really saved my life.Anonymous
February 10, 2014
Idem pour moi réactivation de L'ipv6 j'y ai passé la journée dessus, avec de plus en plus de pression, des erreurs dans tout les sens dans l'observateur d'évènement ! Merci BcpAnonymous
September 24, 2014
+1 for adding Exchange server to domain admin group to resolve topology error.Anonymous
November 04, 2014
Make sure that the exchange server is member of "Exchange Servers" and "Exchange trusted Subsystems" exchange security group in active directory. This scenario may occur when you reset the exchange server computer account in active directory (May be in DR situation)Anonymous
February 18, 2015
- Paul Martin I was well into my sixth our of searching when I found your resolution. Thanks!
Anonymous
February 22, 2015
Hi Guys, Enabling the IPV6 worked for me too. ThanksAnonymous
March 18, 2015
I met same problem with exchange 2010, no solution above work I started disjoin and rejoin exhange to domain, the exchange start fineAnonymous
April 16, 2015
I was able to resolve the issue by enabling IPV6 as explained in the following article www.grishbi.com/.../sbs-2008-exchange-services-down-with-event-id-2114-error-0x80040a02-dsc_e_no_suitable_cdcAnonymous
April 23, 2015
+2 for adding Exchange server to domain admin group to resolve topology error. this got us up and running we are now trying to figure out what happened..Anonymous
June 11, 2015
The comment has been removedAnonymous
June 29, 2015
The comment has been removedAnonymous
September 22, 2015
This worked perfect for me after spending 4 hours scouring the web for unrelated issues with the Transport service be stuck in the starting state. Thank you.Anonymous
December 16, 2015
We had the same problem and running Exchange Best Practices Analyzer informed us: "ADAccess configuration is hard-coded Server: EXCH11. The AD Topology service on server EXCH11 is hard-coded to use Active Directory domain controller server(s) dc1.mycorp.com. This configuration isn't recommended because it has limited fail-over options." Exchange DSAccess is configured for static domain controllers Unless the hard-coding of directory servers for DSAccess was performed for a specific reason, you should remove the list of servers and revert to automatically discover domain controllers. support.microsoft.com/.../2619379