Topic Last Modified: 2010-01-27

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:


Product Name


Product Version

14.0 (Exchange 2010)

Event ID


Event Source


Alert Type


Rule Path

Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Transport

Rule Name

The topology doesn't have a route to an Exchange 2003 server from the Routing Group in the routing tables. The recipients will not be routed to this server.


This Warning event indicates that the specified routing table does not have route information to the routing group where the specified server resides. Therefore, routing is unable to route messages to any servers in this routing group. This error can occur in the following situations:

  • Exchange Server 2003 routing groups are removed and routing group connectors are removed, leaving an Exchange 2003 routing group disconnected from the rest of the organization.

  • A routing group connector was not created between an Exchange Server 2010 and an Exchange 2003 routing group during setup of the first Hub Transport server.

  • A routing group connector is misconfigured.

  • Because of Active Directory replication latency, the route information is not yet available to the server that registered this event.

For more information, see the following topics:

  • Understanding Message Routing

  • Internal Message Routing

User Action

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

  • Verify that the indicated routing group has at least one routing group connector to another valid routing group.

  • Verify that a routing group connector exists between the Exchange Routing Group (DWBGZMFD01QNBJR) and at least one Exchange 2003 routing group.

  • Verify the routing group connector configuration.

  • If your configuration is correct, this event may be caused by replication latency. You can take no action and the routing tables will be updated when configuration changes are received. If you have been granted the correct permissions, you can force Active Directory replication to immediately occur.

  • Verify that the Exchange server that logged this event can communicate with one or more Active Directory servers available in the organization.

  • <rte:EEM_ReviewApplicationLog>

  • <rte:EEM_TrySelfHelpOrAssistedSupport>

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.