MSExchange ADAccess 2122
This article provides an explanation and possible resolutions for a specific Exchange event. If you don't find what you’re looking for here, try searching Exchange 2010 Help.
Details
Product Name |
Exchange |
Product Version |
14.0 |
Event ID |
2122 |
Category |
Topology |
Symbolic Name |
DSC_EVENT_DNS_OTHER |
Message Text |
Process %1 (PID=%2). Error 0x%3 occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain %4%n The query was for the SRV record for %5%n For information about correcting this problem, %6%7 |
Explanation
This event indicates that an error occurred when Domain Name System (DNS) was queried for service resource (SRV) records for the specified domain. The domain controllers from the specified domain will not be used by DSAccess. You should investigate the issue and fix it. As long as there is sufficient capacity in usable domain controllers in other domains, there will not be mail flow interruption. If the event contains the name of the local domain, topology discovery cannot be completed and mail flow will be interrupted.
This behavior may occur if the required resource records in DNS are missing or incorrect.
User Action
To resolve this event, do one or more of the following:
Verify that the required SRV and A resource records exist in DNS by using the Nslookup command-line tool. For more information about how to use Nslookup, see Microsoft Knowledge Base article 200525, Using NSlookup.exe.
Verify connectivity, and then verify that the domain controller is running.
Use the
Ping
orPathPing
command-line tools to test basic connectivity. UsePing
to isolate network hardware problems and incompatible configurations. UsePathPing
to detect packet loss over multiple-hop trips. For more information, see Microsoft Knowledge Base article 325487, Advanced network adapter troubleshooting for Windows workstations..Run the
Dcdiag
command-line tool to test domain controller health. To do this, rundcdiag /s:[Domain Controller Name]
at a command prompt on the Exchange server. Use the output ofDcdiag
to discover the root cause of any failures or warnings that it reports. For more information, see Dcdiag Overview at the Windows Server TechCenter..
For More Information
If you are not already doing so, consider running the Exchange tools, which have been created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues and improve mail flow. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.