Solved

MSExchange AD toplogy service errors after installing CAS

Posted on 2009-07-07
4
501 Views
Last Modified: 2012-05-07
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.
0
Comment
Question by:deshaw
  • 2
  • 2
4 Comments
 
LVL 14

Expert Comment

by:Wonko_the_Sane
Comment Utility
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
 
LVL 1

Author Comment

by:deshaw
Comment Utility
I am sorry. I am not using windows 2008. It's windows *2003*-SP2-R2

Sorry for the trouble again.
0
 
LVL 14

Accepted Solution

by:
Wonko_the_Sane earned 500 total points
Comment Utility
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
 
LVL 1

Author Closing Comment

by:deshaw
Comment Utility
thnaks
0

Featured Post

Wish Marketing would stop bothering you?

Is your marketing department constantly asking for new email signature updates? Are they requesting a different design for every department? Do they need yet another banner added? Don’t let it get you down! There is an easy way to manage all of these requests...

Join & Write a Comment

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
how to add IIS SMTP to handle application/Scanner relays into office 365.

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now