XADM: Exchange 2000 Active Directory Connector Does Not Create Proxy Addresses for Custom Recipients in Exchange Server 5.5 (273612)

SYMPTOMS

New custom recipients that are created by the Exchange 2000 Active Directory Connector (ADC) may be missing expected proxy addresses. A warning message that is similar to the following is logged in the application event log:

Event ID: 8040
Type: Warning
Source: MSADC
Category: Replication
Description:

Server 'TARGETSERVER' could not generate e-mail addresses for entry 'cn=USER,ou=SITE,o=ORG'. Was unsuccessful with error:[0xc354]. (Connection Agreement 'To ORG' #2448)

For more information, click http://search.support.microsoft.com/search/?adv=1.

The user that is mentioned in the preceding warning message (USER in this example) as well as all new users that were created after that user did not generate e-mail addresses (even though this error is listed only for the first user that did not generate an e-mail address).

CAUSE

This problem can occur if the user that produced the warning message that contains event ID 8040 contains a proxy address that is in use on the target server already. This event ID warning message simply reports this problem. However, after this error, proxy generation of addresses does not work for all subsequent objects as well because of an error in processing by the Exchange 2000 ADC.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack

The English version of this fix should have the following file attributes or later:

Component: ADC

File name	Version
Msadc.exe	6.0.4418.5

WORKAROUND

To work around this problem, ensure that no proxy addresses that will be imported into Microsoft Exchange Server version 5.5 by the Exchange 2000 ADC are in conflict with an existing address.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 1.