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 |
2075 |
Event Source |
MSExchange ADAccess |
Alert Type |
Warning |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Active Directory Access |
Rule Name |
Exchange failed to retrieve the local server. It's possible that the DNS name of the server has changed. |
Explanation
This Error event indicates that the Fully Qualified Domain Name (FQDN) of the local computer could not be discovered. This event generally occurs when the Exchange server that logged this event runs on a domain controller. This event occurs if one or more of the following conditions are true:
- The DNS server is not correctly configured.
- The name of the computer that logged this event was changed;
however, DNS records were not updated to reflect that change.
User Action
To resolve this error, do one or more of the following:
- Make sure that the server that logged this event is correctly
registered on the DNS server. For more information about how to
troubleshoot DNS issues, see Troubleshooting DNS servers in the Microsoft
Windows Server TechCenter.
- If the name of the computer that logged this event was changed,
make sure that the computer was restarted.
- Review other related events in the Application log and System
log for Warning events and Error events. These related events may
provide more information about the root cause of this error.
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.