Home > Articole IT > Topology discovery failed, error 0x80040a02

Topology discovery failed, error 0x80040a02


I needed a new test bench for testing the Exchange 2007 for someone and I did not wanted to use some of the enw hwrdware so I installed Windows 2008 on an old HP ML350 server , patched everything promoted the machine to a DC and started installing Exchange 2007.

Well , first thing it will start bitching over that you are running with a dynamic IP configuration so I went and double checked but I remembered correctly. The IP was set to static.
Went and started the setup again and again started bitching about dynamic IP.
Well , it was only one way to make it stop , as on the IPV4 was running static , I just DISABLED the IPV6 Protocol as I was not using it.

Started Exchange installation and after performing the pre installation test it installed the management tools and started the Hub Transport role.
After a few minutes the installation stopped with an error but nothing was actually specified.
Started digging trough events and I discovered this error :

Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=3608). 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. 

Checked all the configurations , checked DNS , checked the LDAP , everything was actually ok.
Tried to reboot the server and re-start the installation process but still the same error.

After hours of debugging and checking configuration , changing DNS and all kind of stuff I found an article that suggested enabling IPV6.

I did  so and the error is gone. After rebooting the machine I was able to install the rest of the server roles and everything was ok.

So question is : Why in the bloody hell will MS have IPV6 installed by default and why would Exchange start bitching about Dynamic IP allocation on IPV6 if I don’t use it ? Why would an Exchange installation STOP without the damn IPV6 ??
MS Works in misterious ways.

So if you guys are trying to install Ex2k7 on 2008 remember to have IPV6 enabled !!

  1. Andrew
    March 29, 2009 at 1:34 pm

    Nice fix. I had the same problem. I had disabled ipv6 and the error messages were useless.

    Thanks for the find.

  2. April 8, 2009 at 2:25 am

    dear boss can we get an rss feed pleeze?🙂

  3. Mohammed
    May 23, 2009 at 6:00 am

    Really appreciate your blog, I was struggling for hours to resolve this issue,Now it works cool Dude.

    Thanks

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: