Process (PID=). DSAccess is unable to connect to any domain controller in domain althoughDNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for that domain.The query was for the SRV record for The following domain controllers were identified by the query:Common causes of this error include:- Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses.- Domain controllers registered in DNS are not connected to the network or are not running.For information about correcting this problem,

Details
Product: Exchange
Event ID: 2121
Source: MSExchangeDSAccess
Version: 6.5.6940.0
Component: Microsoft Exchange Directory Access Cache
Message: Process <process name> (PID=<process id>). DSAccess is unable to connect to any domain controller in domain <name> althoughDNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for that domain.The query was for the SRV record for <name>The following domain controllers were identified by the query:<distinguished name>Common causes of this error include:- Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses.- Domain controllers registered in DNS are not connected to the network or are not running.For information about correcting this problem, <text><text>
   
Explanation

This event occurs if Diagnostics Logging on the Topology category of DSAccess is set to Minimum for the server. This event means that the domain controllers from the specified domain will not be used by DSAccess. As long as there is sufficient capacity in suitable domain controllers in other domains, it will not cause mail flow interruption. However, it is recommended that this event be investigated and fixed as soon as possible. If the event contains the name of the local domain, topology discovery cannot be completed, and this will cause mail flow interruption. The following are the possible causes:

  • The required A (address) resource records that map the name of the domain controllers to their IP address do not exist in DNS.
  • The domain controllers advertised in DNS might not be connected to the network or are connected to the network but are not running
   
User Action

Verify that the required A resource records exist in DNS by using the Nslookup command-line tool.

Verify connectivity to the domain controller and then verify that the domain controller is running.

Related:

Leave a Reply