Home > Event Id > Event Id 2114

Event Id 2114

Contents

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 Steps: Option I - Re-enable IPV6 on the server's active network interface (NIC). Exchange server software Mobility & Wireless Outlook Addons OWA Addons POP3 Downloaders PST Management Reporting Security & Encryption SMS & Paging Tips & Tricks Webinars White Papers Featured Products Featured Book Please try again later. http://seforum.net/event-id/event-id-7036-not-showing-in-event-viewer.html

Forum Software © ASPPlayground.NET Advanced Edition Niroshanezra's Exchange 2010 Blog Just another Exchange Guy Home About Me Contact Me Home > Topology discovery failed, error 0x80040a02 (DSC_E_NO_S > Topology discovery failed, Related Categories: Topology discovery failed, error 0x80040a02 (DSC_E_NO_S Comments (0) Trackbacks (1) Leave a comment Trackback No comments yet. Feedback: Send comments or solutions - Notify me when updated Printer friendly Subscribe Subscribe to EventID.Net now!Already a subscriber? Many components depend on IPv6 as listed on TechNet.

Topology Discovery Failed, Error 0x80040a02 (dsc_e_no_suitable_cdc).

A successful result returns information that resembles the following:Local domain is"" (EXAMPLE) Account is"EXAMPLE\Exchange Enterprise Servers" ======================== DC ="" In site ="" Right found:"SeSecurityPrivilege"Note A successful result shows that the Manage Use Policytest.exe to determine whether the Manage auditing and security logs permission for the Exchange Enterprise Servers group is missing on any of the domain controllers. x 333 Marty Check that the "Exchange servers" group has the rights to "manage audit and security logs".

Re-enabling it fixed the problem. See ME919089 to solve this problem. For some reason the Computer account of the member server was not allowd to login in to the domain, changing this GPO solved the problem Thanks (in reply to [email protected]) Post Exchange Topology Discovery Failed The Exchange Enterprise Servers group must be defined in the default domain controller’s policy under Manage Auditing and Security Log.

Explanation:This problem occurs because the Exchange security groups do no have the appropriate user rights to enable the Directory Service Access (DSAccess) component to communicate with Active Directory.Resolution:Verify that the default Event Id 2114 Exchange 2010 Yes No Send us feedback Feedback shows invalid character, not accepted special characters are <> () \ Send Feedback Sorry, our feedback system is currently down. Exchange 2010 RTM Edge Server Installation andConfiguring Sorry Access denied you don't have permission to open this page inOWA RSS feed Google Youdao Xian Guo Zhua Xia My Yahoo! http://www.eventid.net/display-eventid-2114-source-MSExchangeDSAccess-eventno-2458-phase-1.htm After we uninstalled it, the Exchange Server worked again.

Thank you for searching on this message; your search helps us identify those areas for which we need to provide more information. Event Id 2080 English: This information is only available to subscribers. To solve it we activated the MSExchangeDSAccess diagnostic logging. read more...

Event Id 2114 Exchange 2010

Solution: Internet Protocol Version 6 (IPV6) has been improperly disabled on the server. here United States Country Selector Afghanistan Albania Algeria Angola Anguilla Antigua & Barbuda Argentina Armenia Aruba Asia Pacific Australia Austria Azerbaijan Bahamas Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bermuda Bhutan Bolivia Topology Discovery Failed, Error 0x80040a02 (dsc_e_no_suitable_cdc). Article ID: SLN290567 Last Date Modified: 10/20/2014 09:59 AM Rate this article Accurate Useful Easy to understand Was this article helpful? Microsoft Knowledge Base Article 218185 MS Exchange Transport Service also kept crashing and restarting.

I was then able to start our Exchange Services. his comment is here This command adds the Exchange Enterprise Servers group to the domain together with default permissions.Run Policytest.exe, and then note which domain controllers return the following successful result: Right found:"SeSecurityPrivilege"If all the MSPAnswers.com Resource site for Managed Service Providers. Event ID: 2114 Source: MSExchangeDSAccess Source: MSExchangeDSAccess Type: Error Description:Process INETINFO.EXE (PID=241).Topology Discovery failed, error 0x80040a02. Error 0x96f Connecting To Active Directory.

Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). As such Quick Tips have not been reviewed, validated or approved by Dell and should be used with appropriate caution. Then, wait for this change to replicate to all other domain controllers.Run the setup /domainprep command from the Exchange Server 2003 or Exchange 2000 Server CD or from a network installation this contact form You must have domain administrator rights to run Policytest.exe successfully.

From a support forum: - Corrected OWA and IIS configuration based on the following articles. - Troubleshooting Outlook Web Access logon failures in Exchange 2000 and in Exchange 2003 (ME327843) - Msexchange Adaccess 2102 Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. Vincent & Grenadines Suriname Swaziland Sweden Switzerland Taiwan Tajikistan Tanzania Thailand Togo Trinidad & Tobago Tunisia Turkey Turkmenistan Turks & Caicos Islands Uganda Ukraine United Arab Emirates United Kingdom United States

The PID (process ID) is irrelevant as it is specific to that running session of Exchange.

Option II - Fully disable IPV6 using the steps listed in Dell Support Article 644856. In our case, all of our servers have a secondary NIC that is used for tape backup traffic. Kitts & Nevis St. See example of private comment Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (1) - More links...

Enabling IPv6 on a network adapter solved the issue. This problem appeared because our TCP/IP local configuration included two internal DNS servers and two public DNS and the exchange topology discovery engine took the list and used it in the You can verify this with the setspn utility (Windows 2003 resource Kit). navigate here See also the suggestions on EV100330 (MSExchange ADAccess (DSAccess) errors and the “Manage auditing and security” right).

Dell shall not be liable for any loss, including but not limited to loss of data, loss of profit or loss of revenue, which customers may incur by following any procedure This process makes the addition of the Exchange Enterprise Servers group by the setup /domainprep command persist across all domain controllers.Restart the Exchange services.Source: http://support.microsoft.com/kb/919089 Labels: exchange, exchange 2000, exchange 2003 Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Additional Information: Exchange Server versions 2007 and later versions need IPv6 in order to run on Windows Server 2008 and later versions (unless IPv6 is completely disabled ).

Event ID: 2114 Source: MSExchange ADAccess Source: MSExchange ADAccess Maintenance: Recommended maintenance tasks for Exchange servers Type: Error Description:Process MAD.EXE (PID=).