Exchange 2010 error

NAMEWITHELD12
NAMEWITHELD12 used Ask the Experts™
on
this was working fine and then i cant mount the DB

Log Name:      Application
Source:        MSExchange ADAccess
Date:          5/13/2011 7:34:44 PM
Event ID:      2114
Task Category: Topology
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      eff
Description:
Process STORE.EXE (PID=7544). 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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchange ADAccess" />
    <EventID Qualifiers="49156">2114</EventID>
    <Level>2</Level>
    <Task>3</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-05-13T23:34:44.000000000Z" />
    <EventRecordID>8104</EventRecordID>
    <Channel>Application</Channel>
    <Computer>BDCVA.tmgva1.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>STORE.EXE</Data>
    <Data>7544</Data>
    <Data>80040a02</Data>
    <Data>DSC_E_NO_SUITABLE_CDC</Data>
  </EventData>
</Event>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.
Event Xm
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
This is an issue from your connectivity with the DC.
First of all check if you are able to ping the dc with the name and ip from the exchange server and viceversa
Secondly make sure that the NIC card settings and bindings are correct on the Exchange server
Also make sure that the IPV6 is enabled on the exchange 2010 even though you are not using it and then reboot the server.

Author

Commented:
enable the V6 do you have a link ?

thanks !
Success in ‘20 With a Profitable Pricing Strategy

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

To enable IPV6, go to the properties of the NIC card and ensure that the check mark beside IPV6 is checked.
ERP System Manager
Commented:
Agree that it is a Domain controller connectivity problem.  Every 15 mins your Exchange Server will report event ID 2080 in the event log.  Please locate the last entry for this event id, and post the result here.

Here is a link to a page which explains event 2080.  It will show whether DCs are capable of serving Exchange.

Author

Commented:
What happened here: AD got all messed up due to having external DNS in the DC and the exchange servers for more info on this see my other posts , this info will be helpful to anyone installing or upgrading exchange

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial