A route to Mailbox server %1 could not be found for store %2 in routing tables with timestamp %3. Recipients will not be routed to this store.

Details
Product: Exchange
Event ID: 5006
Source: MSExchangeTransport
Version: 8.0
Symbolic Name: RoutingNoOwningServerForMdb
Message: A route to Mailbox server %1 could not be found for store %2 in routing tables with timestamp %3. Recipients will not be routed to this store.
   
Explanation

This Error event indicates that the Microsoft Exchange Server 2007 transport routing engine can’t find the route to the specified information store on the specified Mailbox server. Therefore, routing is unable to deliver messages to recipients with mailboxes located in this store. This error may be caused by Active Directory directory service replication latency.

   
User Action

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

  • Use the Get-ExchangeServer cmdlet in the Exchange Management Shell to verify that the specified server exists.

  • Take no action. The messages will be routed to the Unreachable queue and delivery will be retried when routing configuration changes. When the server information is updated in routing tables, the messages will automatically be routed to the destination server.

  • If you have been granted the correct permissions, you can force Active Directory replication to occur immediately. An Active Directory notification will cause the routing tables to be updated and any affected messages in the Unreachable queue will be resubmitted and routed to the destination server.

  • Verify that the Microsoft Information Store service is started on the Mailbox server that is specified in the error message text.

  • Verify that the databases within the information store that is specified in the error message text are mounted. For more information, see How to Mount a Database.

  • Verify that the Exchange server specified in the error message text is functional and available on the network. For example, 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, How to troubleshoot network connectivity problems.

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

  • 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.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Leave a Reply