An Active Directory object for local Exchange server is not found or is invalid
Topic Last Modified: 2007-11-16
The Microsoft Exchange Server 2007 Management Pack for Operations Manager monitors the Windows Application log on computers that are running Exchange Server 2007 and generates this alert when the event or events specified in the following Details table are logged.
To learn more about this event, do one or more of the following:
Review the description of the event that includes the variables specific to your environment. From the Operator Console, select this alert, and then click the Properties tab.
Review all events that have been logged that meet the criteria of this Operations Manager alert. From the Operator Console, click the Events tab, and then double-click the event in the list for which you want to review the event description.
Details
Product Name |
Exchange |
Product Version |
8.0 (Exchange Server 2007) |
Event ID |
1016 |
Event Source |
MSExchangeFDS |
Alert Type |
Critical Error |
MOM Rule Path |
Microsoft Exchange Server/Exchange 2007/Common Components/File Distribution Service |
MOM Rule Name |
An Active Directory object for local Exchange server is not found or is invalid. |
Explanation
This Error event indicates that the Microsoft Exchange File Distribution service could not find the local server object in the Active Directory directory service to replicate a Unified Messaging Dial Plan. The File Distribution service is used to distribute offline address book files and Unified Messaging prompts. It also replicates Unified Messaging Dial Plans. Unified Messaging Dial Plans are an integral component of the Exchange 2007 Unified Messaging system. For more information about Unified Messaging Dial Plans, see Understanding Unified Messaging Dial Plans.
User Action
No user action is required. The File Distribution service will continue to try to complete the replication process on an interval of one hour. However, if this event frequently occurs, 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, How to troubleshoot network connectivity problems.
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 the Microsoft Exchange server that is experiencing the event. 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 the Application log for related events. Events that occur immediately before and after this event may provide more information about the root cause of this Error event.
If this event seems to be causing mail flow interruptions or other problems in your Exchange environment, contact Microsoft Customer Support. For more information about how to contact support, visit Microsoft Help and Support.
For More Information
To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Search the Support Knowledge Base (KB) Web site.
To review Exchange 2007 event message articles that may not be represented by Exchange 2007 alerts, see the Events and Errors Message Center.
If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.