MSExchange AD toplogy service errors after installing CAS

I installed CAS into the exchange 2007 organization and the installation failed with "Microsoft Exchange Active Directory Topology Service" service start up error. Event viewer is continuously throwing below errors.

 Event Type:      Error
Event Source:      MSExchange ADAccess
Event Category:      Topology
Event ID:      2114
Date:            7/7/2009
Time:            7:04:22 PM
User:            N/A
Computer:      MYCAS1
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1340). 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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I did a little bit of googling and few blogs/forums are suggesting to add exchange server account o "Domain Admins" computer group and look like this worked for most of the people.

I am trying to install Exchange 2007 on Windows 2008 SP2 R2 server.
LVL 1
deshawAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Wonko_the_SaneCommented:
Do not put the account in the Domain Admins group.

You are running Windows 2008 R2? Are you sure?

I would first make sure DNS settings etc are all correct and no firewall etc. is blocking communications to your DCs/GCs. Also I have heard about a similar issue on Windows 2008 if IPv6 is disabled. If you have disabled IPv6, re-enable and try again, just to make sure (and don't ask me for an explanation why this should possible make a difference, I don't have one).
0
deshawAuthor Commented:
I am sorry. I am not using windows 2008. It's windows *2003*-SP2-R2

Sorry for the trouble again.
0
Wonko_the_SaneCommented:
In this case you can safely ignore the IPv6 comment :)

It's hard to tell with only this error message. Are there any other errors related to your domain? E.g. netlogon error messages? If you logon to the machine, do you get a logon server that makes sense (e.g. an in-site Global catalog - check with running "set l" from a command prompt")

Did you try to run "netdiag" on your Exchange server to see if it return any erros?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
deshawAuthor Commented:
thnaks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.