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	1025
Event Source	MSExchange EdgeSync
Alert Type	Warning
Rule Path	Microsoft Exchange Server/Exchange 2010/Hub Transport/EdgeSync
Rule Name	An exception occurred when the Hub Transport server tried to load the Exchange topology configuration data.

Explanation

This Warning event indicates that an exception occurred when the computer that is running the Hub Transport server role tried to load the Exchange topology configuration data from Active Directory. EdgeSync must be able to acquire current Exchange topology data from Active Directory to correctly operate. The exception specified in the event description provides more information about this failure.

This event may be logged in the following circumstances:

If there are network connectivity issues between the Hub Transport server and a domain controller. For example, a cable may be damaged, or a computer may be experiencing high volume of network traffic.
If a domain controller is not correctly functioning.

User Action

To resolve this warning, do one or more of the following:

Check network connectivity between the Hub Transport server and Active Directory. 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 Exchange server. Use the output of Dcdiag to discover the root cause of any failures or warnings that it reports. For more information, see Dcdiag Overview at the Windows Server TechCenter.
Review the Application log for MSExchangeADAccess and MSExchange Topology events that could provide more information about the root cause of this event.

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.