Microsoft KB Archive/326962

= Event ID 2035 message occurs when system attendant tries to initialize the Recipient Update Service =

Article ID: 326962

Article Last Modified on 2/28/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q326962



SYMPTOMS
On Exchange 2000 servers, the system attendant cannot initialize the Recipient Update Service, and the following event ID message is logged in the Application event log:

Event Type: Error

Event Source: MSExchangeSA

Event ID: 2035

Description:

The e-mail address description object in the Microsoft Exchange directory for the 'FAX_PROGRAM' address type on 'i386' machines is missing.

If this event ID message is logged, the Recipient Update Service does not continue its operation and does not stamp e-mail attributes or addresses on mail-enabled objects in the Active Directory directory service.



CAUSE
This issue occurs because the address type object for a third-party program, such as a fax program, cannot be located in Active Directory.

When the system attendant starts, it tries to load an address generation .dll file for each address type that the Recipient Update Service must stamp. These address types are specified in a recipient policy or in the gatewayProxy attribute of the Recipient Update Service.

Note Recipient policies include mailbox manager policies and e-mail address policies.

The system attendant then checks Active Directory for the address type object (AddrType) to obtain the information that the system attendant must have to load the appropriate .dll files. If the address type object is missing, the system attendant cannot load the .dll file, even if the .dll file is installed on the Exchange 2000 server.



RESOLUTION
To resolve this issue, determine if the AddrType object is missing from Active Directory, and then troubleshoot the replication of the AddrType object.

Determine whether the AddrType object is missing from Active Directory
WARNING: If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Exchange 2000 Server, or both. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.
 * 1) Start ADSI Edit, and then connect to the domain controller that the Recipient Update Service is configured to use.

Note Use an account that has administrative privileges.
 * 1) Expand Configuration Container, expand CN=Configuration, expand CN=Microsoft Exchange, and then expand CN=OrganizationName.
 * 2) Expand CN=Addressing, and then expand CN=AddressTypes.
 * 3) Click the CN=AddressTypes object. The address type objects that are currently in Active Directory are listed in the right pane.
 * 4) See if the address type object in the event ID 2035 message is listed. In the example in the &quot;Symptoms&quot; section, 'FAX_PROGRAM' is the AddrType object that the system attendant is trying to locate.
 * 5) If the address type is listed under the CN=AddressTypes object, continue to the &quot;More Information&quot; section of this article. If the address type is not listed, continue to the &quot;Troubleshoot the replication of the AddrType object&quot; section.

Troubleshoot the replication of the AddrType object
Generally, the third-party address type is homed in an Exchange Server 5.5 site as an e-mail address generator. In this scenario, the AddrType object is added to Active Directory through Active Directory Connector (ADC) replication. If the AddrType object is not present in Active Directory, this indicates that replication was not successful.

To determine whether the AddrType object was replicated, follow these steps:  In Exchange System Manager, locate the recipient policy that has the  address enabled, where   is the name of the third-party address type that is referenced by the event ID 2035 message. Use the recipient policy that you located in step 1 to determine which Exchange Server site has the e-mail address generator. Start ADC Manager on the ADC server, and then determine which ADC recipient Connection Agreement is responsible for the Exchange Server site. The Connection Agreement tells you which Exchange Server computer is replicating the  and the domain controller to which the ADC replicates. Run the Microsoft Exchange Administrator program against the Exchange Server 5.5 computer, and then expand the following containers:    Configuration</li> Addressing</li> E-Mail Address Generators</li></ul> </li> Verify that the  is listed in the right pane.

If it is listed, it was replicated to the Exchange 2000 Site Replication Service (SRS) server during ADC replication and you can continue to step 6. If it is not listed, a configuration problem that requires troubleshooting exists on the Exchange Server site. This article does not address configuration problems.</li> Run the Microsoft Exchange Administrator program against the SRS database on the Exchange 2000 SRS server, and then expand the following containers: <ul>  </li> Configuration</li> Addressing</li> E-Mail Address Generators</li></ul> </li> Verify that the  is listed in the right pane.

If it is listed, it was successfully replicated from Exchange Server to the SRS database by using ADC replication. If it is not listed, troubleshoot the replication between Exchange Server and the SRS database.</li> In ADC Manager, right-click the Active Directory Connector object, and then click Properties.</li> Click the Diagnostics Logging tab, set the logging level to Maximum for Replication, LDAP Operations, and Service Control.</li> Start Event Viewer, and then set the size of the Application event log to at least 10 MB.</li> On the Exchange Server computer, change the display name of the  address generator so that it will be included in the replication test.</li> In ADC Manager, right-click the recipient Connection Agreement for the Exchange Server site, and then click Replicate now to force ADC replication.</li> Track the replication progress from Exchange Server to the SRS database by using the information in step 6.

If the  replicated to the SRS database successfully, the new display name appears. If the replication was successful, continue to step 14. If the replication was not successful, check the Application event log for warnings or errors.</li> Track the replication progress from the SRS database to Active Directory by using the information in the &quot;Determine if the AddrType Object Is Missing from Active Directory&quot; section. Make sure to connect ADSI Edit to the domain controller to which the ADC server is replicating.

If the  replicated to Active Directory, it is listed in the CN=AddressTypes list. If the replication was successful, continue to step 16. If the replication was not successful, check the Application event log for warnings or errors.</li> <li>After the  appears in Active Directory on the domain controller, permit it to replicate to the other domain controllers.</li> <li>After the object replicates to Active Directory on the domain controller that the Recipient Update Service server uses, restart the system attendant service on the Recipient Update Service server. For more information about how to troubleshoot ADC replication, click the following article number to view the article in the Microsoft Knowledge Base:

253841 Troubleshooting Active Directory Connector replication issues

</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
For more information about how third-party address types can contribute to problems with the Recipient Update Service, click the following article number to view the article in the Microsoft Knowledge Base:

286356 Recipient Update Service does not stamp proxy addresses

Additional query words: SA, E2K, DC, FAXSR, FASTFAX, FAX,RUS XADM

Keywords: kbprb KB326962

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.