Case Studies Event ID 2114

Chicago Area Laptop for rent: $35 per day plus $10 for additional day

Case Studies Event ID 2114

Event ID: 2114 MSExchangeDSAccess with other Exchange Event ID.

Symptoms: You may receive the following Event ID in your Exchange server:

1) Event ID: 2114 MSExchangeDSAccess

2) Event ID: 2102 MSExchangeDSAccess

3) Event ID: 2103 MSExchangeDSAccess

4) Event ID: 7200 MSExchangeIS Public Store

5) Event ID: 8026 MSExchangeAL

Resolutions: 1) It can be DNS or Active Directory issues (see below).

2) It can be third-party software such as Anti-virus and anti-spam software cause the problem.

3) This event can be caused by the evaluation version of SharePoint Portal Server.

Active Directory issue with Event ID: 2114, Event ID 1042, Event ID 8213 and Event ID 9098

1) It can be DNS issue. Make sure primary DNS and 2nd DNS servers point to each other as primary and themselves as secondary if both DNS servers are in the LAN.

2) You may try to run: dcdiag /v, netdiag /v and search for the.

3) It can be TCP/IP settings issue. Make sure you use internal DNS instead of ISP DNS. Never add the ISP DNS as secondary DNS.

4. One of our client had a similar case. They have SBS 2008 running Exchange 2007. They can't start Exchange Information service with the Event ID 2114:
Process MAD.EXE (PID=5380). 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.

Troubleshooting: We found out that if the client disabled IPv6 that causes this error. After re-enabling IPv6 and the information store service would start again.. Exchange 2007 requires IPv6 be enabled even if you are not using it

5. It can be the server or client can't locate Domain Controllers for Directory Access.