Topic Last Modified: 2010-02-15
The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.
To learn more about this alert, in Operations Manager, do one or more of the following:
- From the Operations Console, double-click this alert, and then
click the General tab. Review the description of the alert
that includes the variables specific to your environment.
- From the Operations Console, double-click this alert, and then
click the Alert Context tab. Review the logged events that
meet the criteria of this Operations Manager alert.
Details
Product Name |
Exchange |
Product Version |
14.0 (Exchange 2010) |
Event ID |
2122 |
Event Source |
MSExchange ADAccess |
Alert Type |
Warning |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Active Directory Access |
Rule Name |
An error occurred when the Domain Name System (DNS) was queried for domain entries. |
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, How to troubleshoot network connectivity problems..
- 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 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, improve mail flow, and better manage disaster recovery scenarios. 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.