XADM: Routing Information Is Not Propagated Across an Exchange 2000 Organization

Article translations Article translations
Article ID: 318491 - View products that this article applies to.
This article was previously published under Q318491
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

In certain situations, routing information may not be dynamically propagated across servers throughout an Exchange 2000 organization. For example, if you add or modify a Simple Mail Transfer Protocol (SMTP) connector in the routing group, that information may not be available for use by the rest of the organization until every Exchange 2000 Server computer in the organization has been restarted.

Additional symptoms of this issue include the following:
  • The major version number in the routing group constantly increases. This can be monitored by using the Winroute.exe tool.

    For additional information about the Winroute tool, click the article number below to view the article in the Microsoft Knowledge Base:
    281382 XCON: How to Use the WinRoute Tool
    To view this information, expand the Version Info node in the Winroute tree. Refresh the view periodically, and then note any changes.

    The major version number should change only if there is a change in the Connections container -- for example, if you add, delete, or modify a connector. If there has not been a topology change and the major version number increases after you refresh, you are experiencing this issue.
  • None of the Routing Group members appear to be connected to the Routing Group master in Winroute.exe (that is, there is a red X next to each server). To see this, expand the RG Members' in Winroute node.

CAUSE

This behavior occurs if there is a missing Servers container in the administration group that contains the Routing Groups container. You can see the Servers container only by using the LDP or ADSI Edit tools (if there are no servers in the administration group).

RESOLUTION

To resolve this issue, make sure that your Exchange organization is in native mode, and then follow these steps:
  1. Create a new administration group.
  2. Create a new Routing Groups container in the new administration group.
  3. Drag the existing routing groups from the old Routing Groups container into the new one.
  4. Restart all Exchange services.
Winroute now shows that the members of the routing group have successfully connected to the routing group master (a green tick appears against the server), and routing information can now be transferred between servers.

Properties

Article ID: 318491 - Last Review: October 24, 2013 - Revision: 1.4
APPLIES TO
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kbnosurvey kbarchive kbprb KB318491

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com