EdgeSync MSERV synchronization critical failures
Applies to: Operations Manager Management Pack for Exchange 2010
Topic Last Modified: 2011-11-01
The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager runs Exchange Management Shell cmdlets to monitor your Exchange organization. Running cmdlets triggers one or more Operations Manager alerts if a problem is detected.
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 events that have been logged that meet the criteria of this Operations Manager alert.
Details
Product Name |
Exchange |
Product Version |
14.0 (Exchange 2010) |
Event ID |
^(1000|1006)$ |
Event Source |
MSExchange Monitoring EdgeSyncMServ |
Category |
KHI |
Alert Type |
Error |
Server Role |
Ex14. Hub Transport |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Hub Transport/EdgeSync |
Rule Name |
EdgeSync MSERV synchronization critical failures. |
Explanation
This Error event indicates that the Microsoft Exchange EdgeSync service encountered a critical error when it tried to synchronize an address to MSERV. The exception that is specified in the event description provides more information about this failure.
User Action
To resolve this problem, 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, Advanced network adapter troubleshooting for Windows workstations.
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 server that is running Microsoft Exchange. Use the output of Dcdiag to determine 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 cause of this event.
For More Information
If you are not already doing so, consider running the Exchange tools, which have been 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 and improve mail flow. 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.