MSExchange EdgeSync 1013

  • Article

 

This article provides an explanation and possible resolutions for a specific Exchange event. If you don't find what you’re looking for here, try searching Exchange 2010 Help.

Details

Product Name

Exchange

Product Version

14.0

Event ID

1013

Event Source

MSExchange EdgeSync

Category

Synchronization

Symbolic Name

FailedToReadEntriesFromAD

Message Text

Synchronization failed because it could not read replication data from the Active Directory server %1, port %2 with exception: %3. Check network connectivity, and test the health of the domain controller.

Explanation

This Warning event indicates that the computer that is running the Hub Transport server role was unable to successfully synchronize Edge-relevant configuration data to the computer that is running the Edge Transport server role. EdgeSync will try to synchronize with the server specified in the event description again. This behavior may occur if the Hub Transport server is unable to collect the appropriate data from Active Directory. The exception specified in the event description provides more information about this failure.

This may be caused by one of the following:

  • Network connectivity issues between the Hub Transport server and the Edge Transport server. For example, a cable may be damaged, or a computer may be experiencing high volume of network traffic.

  • A domain controller is not correctly functioning.

  • The domain controller is too busy responding to other processes.

  • The CPU on the Edge Transport server is busy responding to other processes.

User Action

No user action is required if this event is not logged frequently. If this event frequently occurs:

  • Check network connectivity between the Hub Transport server and the Edge Transport server. 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 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.

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.