Topic Last Modified: 2010-01-27
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 |
4014 |
Event Source |
MSExchange Availability |
Alert Type |
Warning |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Client Access/Information Worker |
Rule Name |
Unable to retrieve the local server object from Active Directory. |
Explanation
This Error event indicates that the Availability service could not contact Active Directory to obtain the local server object. The Availability service retrieves the Schedule+ Free Busy and Out-Of-Office (OOF) data for a set of mailboxes that reside on the computer that is running Microsoft Exchange Server 2007 or Exchange Server 2010. The local server object can help the Availability service locate the mailbox required for the retrieval of Schedule+ Free Busy or OOF data. This event may occur when one or more of the following conditions are true:
- The Exchange server that logged this event is trying to
connect to a domain controller that is not working correctly.
- Network issues interfere with attempts to connect to the domain
controller.
User Action
To resolve this error, follow one or more of these steps:
- Use the Ping or PathPing command-line tools to
test basic connectivity. Use Ping to isolate network
hardware problems and incompatible configurations. Use
PathPing to detect packet loss over multiple-hop trips. For
more information, see Microsoft Knowledge Base article 325487,
Advanced network adapter troubleshooting for
Windows workstations.
- Make sure that the Exchange server that logged this event
is registered correctly on the Domain Name System (DNS) server. For
more information about how to troubleshoot DNS issues, see DNS Troubleshooting.
- Run the Dcdiag command line tool to test domain controller
health. To do this, run dcdiag /s:<Domain Controller
Name> at a command prompt on Microsoft Exchange. Use
the output of Dcdiag to discover the root cause of any
failures or warnings that it reports. For more information, see
Dcdiag Overview.
- Review related Error and Warning events in the Application log.
These related events may help you find 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.