Home > Event Id > 0x80040a02 Dsc_e_no_suitable_cdc

0x80040a02 Dsc_e_no_suitable_cdc

Contents

When this issue was occuring I verified that the Exchange 2010 server was successfully talking to a domain controller in the same Active Directory site by issuing the following command from The problem may resolve itself in a while. Kjell Blomberg says: April 2, 2013 at 9:06 am Thanks !! Cindy - It sounds really weird, but it sounds more like somehow the DC policy is not properly getting applied to the DC's after reboot, or are you going to the have a peek here

However in my case i noticed that the Default Domain Controller policy was not modified. I had one of the guys on my team P2V a CAS\HUB then delete it out of AD. Dear all, Hello there. Topology discovery failed due to LDAP_SERVER_DOWN error".

0x80040a02 Dsc_e_no_suitable_cdc

All rights reserved. At this point, the next step is to look for a recent 2080 event and see what the Exchange server was seeing as far as domain controllers were concerned. Thanks < Message edited by bonadio -- 4.Aug.2008 12:06:26 PM > Post #: 1 Featured Links* RE: event id 2114 adding second server with mailbox role - 1.Aug.2008 6:59:49 PM You're not manually adding the Exchange Servers group to the right in the DC's local policy are you?

Reset Backup Exec 2012 to Factory Defaults View Mailbox Sizes for Exchange 2003 and Exchange ... It has been most helpful.Strangely I encountered a similar issue in my test environment (I was doing some testing on Active Directory Privilege Escalation) and was at a loss to figure good information ds acseess errors . Exchange Topology Discovery Failed Ron Jack says: June 5, 2012 at 5:14 am If one DC had errors with the SACL would this cause event ID’s 2114, 2103, 2604, 2102, 1005?

Frank Wang Friday, October 21, 2011 1:49 AM Reply | Quote 0 Sign in to vote Hi PGrama, Any updates? Microsoft Knowledge Base Article 218185 are not responding: 2114 (MSExcahnge ADAccess) - Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1408). Vielen Dank. PeanutButter Administrator says: November 15, 2013 at 3:36 am This fixed my issue, someone linked another GPO to the DC ou.

Did you find the fix?   0 Pimiento OP knelson312 Jan 24, 2014 at 3:37 UTC 1st Post I just started experiencing variations of this problem about the All Global Catalog Servers In Forest Are Not Responding Thank you again! I am active on Experts Exchange & TechNet forums and I am a technical author for SearchExchange.Follow me on Twitter, LinkedIn, Facebook, or Google+ for the latest updates. To Isolate such scenarios below are the steps that have to checked. 1: Check the network or DNS issues. 2: Obviously they must all be pointing to an internal DNS server,

Microsoft Knowledge Base Article 218185

MSPAnswers.com Resource site for Managed Service Providers. look at this web-site RE-ENABLING IPV6 on the nic instantly fixed everything. 0x80040a02 Dsc_e_no_suitable_cdc When you run RSOP.msc on a DC when the problem occurs, does it show the correct policy was applied to the DC? Event Id 2114 Exchange 2007 Solution : Whenever we get one of these cases, the first thing we need to do is go to one of the Domain Controllers -> Click Administrative tools -> local Security

Please make sure "Exchange Enterprise Servers","Exchange Servers","Administrators" are assigned Manage auditing and security log right(Default ControllerSecurity Policy->Local Policies->User Rights Assignment). If this event occurs frequently, check network connectivity using PING or PingPath. Going to group policy, default domain controllers we could see Exchange Servers group had been removed from manage auditing and security log. It was Exchange Mail-Box server itself as we had already diagnosed. Msexchange Adaccess 2102

Please read our Privacy Policy and Terms & Conditions. And in his Default Domain Policy, the Exchange Enterprise Servers (EES) group (Exchange 2003 group) had been granted the right. Hope this post has been helpful. Check This Out Then everything was fine, we could apply updates & reboot the DCs with no problem.

I get the message "The name limit for the local computer network adapter card was exceeded". Msexchange Adaccess 2114 Post to Cancel %d bloggers like this: Have a very nice time out there. 0 Chipotle OP Winner8466 Mar 23, 2015 at 3:24 UTC I KNOW this is old, but it comes up a lot

Event Type: Error Event Source: MSExchange ADAccess Event Category: General Event ID: 2501 Description: Process MSEXCHANGEADTOPOLOGY (PID=4600).

In Case if we are getting only Event ID 2080 apart from any other event Event Type: Information Event Source: MSExchange ADAccess Event Category: Topology Event ID: 2080 Description: Process MSEXCHANGEADTOPOLOGYSERVICE.EXE When updating security for a remote procedure call (RPC) access for the Exchange Active Directory Topology service, Exchange could not retrieve the security descriptor for Exchange server object SERVER - Error i mean create a static DNS host record entry for Exchange .  Any other thoughts ? 0 Pimiento OP Technicality Feb 28, 2013 at 6:34 UTC We're using Event Id 2102 Frank Wang Monday, October 24, 2011 1:52 AM Reply | Quote Microsoft is conducting an online survey to understand your opinion of the Technet Web site.

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. Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions. By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks.

If this event occurs infrequently, no user action is required. However all the settings has been disabled ..but our exchange server still randomly loss connectivity to AD . Option II - Fully disable IPV6 using the steps listed in Dell Support Article 644856. Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password?

Exchange Active Directory Provider has discovered the following servers with the following characteristics: (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right We then drill down to the User Rights Assignment, as seen below. You can use the links in the Support area to determine whether any additional information might be available elsewhere. All Global Catalog Servers in forest ...