Monday, March 14, 2011

Exchange 2010 Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC)

Strange issue today with an Exchange 2010 CAS/HUB/MBX Server. Event Viewer:
  • Unable to initialize the Microsoft Exchange Information Store service.   - Error 0x96f.)
  • MSExchange ADAccess 2114 Error: Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1360). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC).
Solution:

Default Domain Controllers Policy:
Computer Configuration/Windows Settings/Security Settings/Local Policies/User Rights Assignment: Manage Auditing and Security Log

Manage Auditing and Security Log contained only BUILTIN\Administrators

Manage Auditing and Security Log should contain at least:
AD-NetBIOS-Name\Exchange Servers, BUILTIN\Administrators

2 comments:

  1. The solution given in this post is not applicable to an exchange server that has already been installed into a domain that was prepped for 2012. If your exchange is reporting this error please check your IPV6 settings first. It has to be enabled and ticket. The issue will be resolved.

    ReplyDelete
  2. Excellent write up! In my limited experience, however, I’ve found out that to Convert edb to pst - EdbMails is the best option as it can handle most exchange recovery tasks gracefully. It supports export of mailboxes to PSTs and also has an extensive range of filtering options. It is a forensic recovery that can extract most data from even corrupt or inaccessible exchange databases.It supports public, private folder recovery along with migration to Live exchange and Office 365. Archive mailbox migration is also supported by edbmails

    ReplyDelete