XCON: X.400 Connector Ignores OU2 During Routing (273945)



The information in this article applies to:

  • Microsoft Exchange Server 5.5
  • Microsoft Exchange Server 5.5 SP1
  • Microsoft Exchange Server 5.5 SP2
  • Microsoft Exchange Server 5.5 SP3

This article was previously published under Q273945

SYMPTOMS

The Exchange Server message transfer agent (MTA) may choose a wrong route when connections have an address space that is defined using an Organizational Unit 2 (OU2). Messages may bounce, and non-delivery reports (NDRs) may be created.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.5 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.


The fix needs to be installed in all routing calculation servers in the organization.

For customers that are routing on OUs and that do not upgrade all their routing ID servers together, the following problems will occur:
  • This present problem will appear on the messages that get routed by the MTAs that do not have the fix applied.
  • When one of the servers with the fixed Gateway Address Resolution Table (GWART) replicates the GWART over to other servers, the other server without the fix generates a different GWART, and replicates its version of the GWART, creating a "ping-pong" effect in replication. The servers with the fix and the server without will generate a different GWART for the same data and connectors, and duel over whose copy of the GWART is correct. The bare minimum requirement is that all the routing ID servers be updated together.
The English version of this fix should have the following file attributes or later:

Component: MTA

File nameVersion
Emsmta.exe5.5.2654.21
Ems_rid.dll5.5.2654.21
MTacheck.exe5.5.2654.21
Mtamsg.dll5.5.2654.21
X400om.dll5.5.2654.21
Mtaperf.dll5.5.2654.21
P2.xv2n/a
P772.tpln/a
P42.tpln/a
Dbserver.schn/a
Dcprods.catn/a

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5.

Modification Type:MinorLast Reviewed:10/6/2005
Keywords:kbHotfixServer kbQFE kbbug kbExchange550preSP5fix kbfix kbQFE KB273945