Mad.exe Error 2102
Contents |
Monitor an unlimited number of servers with $49/year With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago all domain controller servers in use are not responding exchange 2010 it was still common to see an entire company using just one server, these
Event Id 2102
days that's no longer the case. New computers are added to the network with the understanding that they will be taken care
Event Id 2114 Exchange 2010
of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers. read more... Event ID: 2102 Source: MSExchangeDSAccess Source: MSExchangeDSAccess Type: Error Description:Process MAD.EXE (PID=792). All Domain Controller Servers in use are not responding: dc1.company.com dc2.company.com dc3.company.com English: This information is only available to subscribers. An example of English, please! Concepts to understand: What is the role of the Microsoft Exchange Directory service? What is MAD.EXE? Comments: EventID.Net From newsgroup postings it appears that this event can be safely ignored. Apparently, Microsoft PSS confirmed that this error code is a benign error and is a result of running in a single GC/DC environment. Also, as per ME328646, this issue may occur if the Exchange Enterprise Servers security group does not have "Manage auditing and security logs" permissions on the domain controller. x 30 EventID.Net See "Cisco Support Document ID: 43640" for information about this event. x 34 Ajay Kulshreshtha In our case, this error was followed by other errors: 2114, 1042, 1047, 8213 and 9098, while we were installing the first Exchange 2003 on a site which had an Exchange 5.5 server. (Installation stalled without giving any on-screen errors) The problem was a non-default LDAP port being used by the old Exchange 5.5 server. When we changed the port to 389 and restarted the services, the errors were gone. By the way, we also had to change port in the Connection Agreements of ADC. x 43 EventID.Net As per Microsoft: "This issue may occur if the Exchange Enterprise Servers security group does not have Manage auditing and security logs permissions on the domain controller. The Exchange Enterprise Servers group must have Manage auditing and security logs permissions on all the
360 games PC games Windows games Windows phone games Entertainment All Entertainment Movies & TV Music Business & Education Business Students & educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet http://www.eventid.net/display-eventid-2102-source-MSExchangeDSAccess-eventno-1362-phase-1.htm Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All https://support.microsoft.com/en-us/kb/310896 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My https://social.technet.microsoft.com/Forums/en-US/bf586bac-a7f3-431d-8e3d-a1fa755bd474/topology-discovery-failed-errors-in-event-log?forum=smallbusinessserver Forums Answered by: Topology discovery failed errors in event log. http://forums.msexchange.org/m_140134600/printable.htm Windows Small Business Server > Small Business Server Question 0 Sign in to vote I have a client with a SBS2011 server, that has been working fine for about 5 months. Recently we have found multiple errors in the exchange 2010 application log indicating that the exchange cannot communicate correctly with the DC. Event ID 2102 - process MAD.exe. All domain controllers are not responding Event ID: 2102 - process STORE.exe. All domain controllers are not responding. Event ID: 2102 - process MSEXCHANGEADTOPOLOGYSERVICE.EXE. All domain controllers are not responding. mad.exe error 2102 Event ID: 2080 - process MAD\STORE Exchange active directory provider has discovered the following servers sbs-srv.domain.local CDG 100100000 Event ID: 2114 - process MAD\STORE. Topology discover failed error 0x80040a02 DSC_E_NO_ SUITABLE_CDC Nothing changed on the server before these errors occurred. The exchange seems to be working fine, but the backup of the database now fails. I have checked and the exchange server & exchange enterprise server are in the correct group for permissions. I have added the computer account to the domain admin IPv6 is enabled DCDIAG shows no errors I have rerun setup.com /preparedomain from exchange. Please does anyone have any other ideas as to what I can check next? Monday, September 02, 2013 11:39 AM Reply | Quote Answers 0 Sign in to vote Hi, This issue may occur if the Exchange Enterprise Servers security group does not have "Manage auditing
after logging these error messages. The exchange services somehow fizzle out as well, and everything stops. then it all comes up again.I have 2 GCs, 3 DCs, and they are all in the same site. My exchange is a member server. All Servers run Windows 2003has anyone seen this error before, and what is the way round it.Thanks rytmehans -> RE: MSExchangeDSAccess Error (23.Jan.2005 9:43:00 PM) Hi,This might help: http://www.eventid.net/display.asp?eventid=2107&eventno=3120&source=MSExchangeDSAccess&phase=1If it doesn't please post full text of the events. exchangerock -> RE: MSExchangeDSAccess Error (23.Jan.2005 11:18:00 PM) Hi,Please check the following :1. Check if DNS is resolving the names. Nslookup.2. Reboot the GCs and then reboot exchange.3. Open ESM and properties of Server and goto DSAccess tab and check if it is filled with server names, DC, GC and Working DCs.4. These are only communication errors with DCs.Reply with any errors.Exchange Rock rkenny -> RE: MSExchangeDSAccess Error (24.Jan.2005 2:46:00 PM) Thanks for the prompt reply. i checked my registry,and noticed that i already have my there DCs (including 2 GCs) listed here. but my the isGC entery says 0x0, which i changed to 0x1. It seem like it was going to work, but then the errors came up again...Event Type: ErrorEvent Source: MSExchangeDSAccessEvent Category: Topology Event ID: 2103Date: 1/24/2005Time: 2:32:37 PMUser: N/AComputer: XXXXXXDescription:Process MAD.EXE (PID=2388). All Global Catalog Servers in use are not responding: gc01.cmydomain.com gc02.mydomain.com Event Type: InformationEvent Source: MSExchangeDSAccessEvent Category: Topology Event ID: 2080Date: 1/24/2005Time: 2:32:34 PMUser: N/AComputer: xxxxxxDescription:Process WMIPRVSE.EXE -EMBEDDING (PID=3876). DSAccess has discovered the following servers with the following characteristics: (Server name | Roles | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version) In-site:dc01.mydomain.com CDG 0 0 1 0 0 0 0 0gc02.mydomain.com CD- 6 6 0 0 1 1 6 1gc01.mydomain.com C-G 0 0 1 0 0 0 0 0 Out-of-site: Event Type: WarningEvent Source: MSExchangeDSAccessEvent Category: Configuration Event ID: 2090Date: 1/24/2005Time: 2:32:34 PMUser: N/AComputer: xxxxxxDescription:Process WMIPRVSE.EXE -EMBEDDING (PID=3876). The Configuration Domain Controller specified in the registry (gc01.mydomain.com) is unreachable. DSAccess will choose the Configuration Domain Controller from the list of available Domain Controllers. Event Type: WarningEvent Source: MSExchangeDSAccessEvent Category: Topo