An exception occured while loading the required EdgeSync credentials. Run the Test-EdgeSynchronization cmdlet on the Hub Transport server
Applies to: Operations Manager Management Pack for Exchange 2010
Topic Last Modified: 2011-08-02
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 |
1033 |
Event Source |
MSExchange EdgeSync |
Alert Type |
Warning |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Hub Transport/EdgeSync |
Rule Name |
An exception occured while loading the required EdgeSync credentials. Run the Test-EdgeSynchronization cmdlet on the Hub Transport server. |
Explanation
This Error event indicates that an error occurred when the Microsoft Exchange EdgeSync credentials were loaded. This error typically occurs if EdgeSync credentials are not found for the Edge Transport server or if the EdgeSync service cannot decrypt the credentials that are used for the Edge Transport server.
User Action
To resolve this warning, do one or more of the following:
To determine the cause of this error, you must run the Test-EdgeSynchronization cmdlet on the Hub Transport server.
Resubscribe the Edge Transport server that is specified in the event description. For more information, see the following topics:
Run the
Dcdiag
command-line tool to test domain controller health. To do this, rundcdiag /s:[Domain Controller Name]
at a command prompt on the Exchange server. Use the output ofDcdiag
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 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.