Topic Last Modified: 2010-02-22
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 |
5011 |
Event Source |
MSExchangeTransport |
Alert Type |
Error |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Transport |
Rule Name |
No source routing group was found in the routing tables for the specified connector. Therefore, the connector has been skipped. |
Explanation
This Error event indicates that the specified routing group connector is configured to use the specified routing group as the source 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. For more information, see Understanding Message Routing.
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 the Application log and System log on your Exchange 2010
servers for related events. For example, events that occur
immediately before and after this event may provide more
information about the root cause of this error.
- Resolve your issue by using self-support options, assisted
support options, and other resources. You can access these
resources from the Exchange Server Solutions Center. From this page,
click Self-Support Options in the navigation pane to use
self-help options. Self-help options include searching the
Microsoft Knowledge Base, posting a question at the Exchange Server
forums, and others. Alternatively, in the navigation pane, you can
click Assisted Support Options to contact a Microsoft
support professional. Because your organization may have a specific
procedure for directly contacting Microsoft Technical Support, be
sure to review your organization's guidelines first.
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.