Topic Last Modified: 2010-02-18

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	5012
Event Source	MSExchangeTransport
Alert Type	Error
Rule Path	Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Transport
Rule Name	The target routing group wasn't found for this routing group connector in the routing tables. The connector will be skipped.

Explanation

This Error event indicates that the specified routing group connector is configured to use the specified routing group as the target routing group. However, that routing group does not exist in the referenced routing table. Microsoft Exchange will not include this connector in server route information. This error may be caused by Active Directory replication latency.

User Action

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

Verify the routing group connector configuration and make sure that the source and target servers configured for the routing group connector are valid.
Take no action. When the Active Directory notification is received, the routing tables will be updated to include this routing group connector.
If you have been granted the correct permissions, you can force Active Directory replication to occur immediately.
Review other related Error and Warning events in the Application log. These related events may help you find the root cause of this error.
If the recommended steps do not resolve this error, contact Microsoft Customer Support Services. For more information about how to contact support, visit the Microsoft Help and Support Web site.

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.