Microsoft KB Archive/286356

= Exchange Recipient Update Service does not stamp proxy addresses in Exchange 2000 Server and in Exchange Server 2003 =

Article ID: 286356

Article Last Modified on 10/25/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Standard Edition
 * Microsoft Exchange Server 2003 Enterprise Edition
 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q286356



This article is a consolidation of the following previously available articles: 286356, 283134





SYMPTOMS
The Microsoft Exchange 2000 Server or Microsoft Exchange Server 2003 Recipient Update Service does not create proxy addresses (e-mail addresses) for newly mail-enabled users or public folders when the computer that is running Exchange is in an Exchange mixed-mode environment. An Exchange mixed-mode environment includes Exchange Server 5.5 and Exchange 2000 Server or Exchange Server 2003. Additionally, the following events may be logged in the Event Viewer Application log when you start the Microsoft Exchange System Attendant service.

Event 1
Event Type: Error

Event Source: MSExchangeSA

Event Category: General

Event ID: 2035

Description:

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

Event 2
Event Type: Error

Event Source: MSExchangeSA

Event Category: General

Event ID: 2037

Description:

The file version of 'Address\ \I386\ .dll' installed on the local server is not current. Unable to locate a correct version on any server in the site.

Event 3
Event Type: Error

Event Source: MSExchangeSA

Event Category: General

Event ID: 2027

Description:

Unable to generate the e-mail address. Unable to load address module 'C:\Exchsrvr\Address\ \I386\ .dll' for address type ' '. Error 0xc007007e.

Event 4
Event Type: Error

Event Source: MSExchangeAL

Event Category: Service Controller

Event ID: 8231

Description:

Permanent failure reported by policy group provider for 'CN=Recipient Policies,CN=Name,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=Name,DC=com':'MAD.EXE', error=8000ffff. Taking provider offline.



CAUSE
The issue can occur because of an invalid or missing third-party e-mail address generator. When the Microsoft Exchange System Attendant service starts, it tries to load an address generation .dll file for each address type that the Recipient Update Service requires to generate the third-party proxy address. If the System Attendant cannot load the .dll file for any address type, the Recipient Update Service does not process the accounts. Additionally, the events that are mentioned in the &quot;Symptoms&quot; section are logged in the Event Viewer Application log.

The generator may be present on any recipient policy. If you do not find the address generator in a recipient policy, check remote sites/administrative groups for the invalid or missing e-mail address generator. If such an invalid e-mail address is added to the gatewayProxy attribute of a Recipient Update Service, the Recipient Update Service no longer updates objects.



RESOLUTION
To resolve this issue, either manually copy the missing .dll file from an existing Exchange Server 5.5 computer, or disable that particular address type so that the Recipient Update Service no longer tries to load the .dll file.

Note Every server that is running Exchange that has a Recipient Update Service must have the correct address generation .dll files.

Option 1: Copy the third-party address generation .dll files

 * 1) Note the name of the required .dll files that are mentioned in the MSExchangeSA event ID 2027 or 2037.
 * 2) On an existing Exchange Server 5.5 computer, locate the .dll file that is specified in step 1.
 * 3) Create the folder structure that is listed in the MSExchangeSA event ID 2027 or 2037.
 * 4) Copy the .dll file into the location that is specified in the MSExchangeSA event ID 2027 on the Exchange computer that is running the Recipient Update Service.
 * 5) Restart the Microsoft Exchange System Attendant service on the Exchange computer.
 * 6) Monitor the Event Viewer Application log to make sure that the error messages are no longer logged.
 * 7) Right-click a Recipient Update Service in the right pane, and then click Update Now to trigger the Recipient Update Service to update objects. Do this step for each Recipient Update Service that is listed in the right pane.

Option 2: Remove the invalid or unwanted address type from all recipient policies
 Find the policy that has the improper or unwanted e-mail address generator. To do this, follow these steps:  In Exchange System Manager, expand Recipients. Click Recipient Policies, and then examine each recipient policy that is listed in the right pane for the e-mail type that is experiencing this issue.

Note The e-mail type that is experiencing the issue is listed in the event ID 2035, 2027, and 2037 error messages that are mentioned in the &quot;Symptoms&quot; section, where  is the e-mail type that is experiencing the issue. If you cannot find the address type that is experiencing this issue in a recipient policy, check site addressing and e-mail address generators at remote sites/administrative groups. When you identify the address type that is experiencing this issue, click to clear the check box for the problem address type from the recipient policy, and then click OK to close the policy properties.</li></ol> </li> Use ADSI Edit or the LDP utility to examine each Recipient Update Service for the address type that is experiencing this issue. To do this, follow these steps.

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 Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. 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. <ol style="list-style-type: lower-alpha;"> Start ADSI Edit.</li> Expand the Configuration container.</li> Expand Services, click Microsoft Exchange, click  , and then click Address Lists Container.</li> Click Recipient Update Services.</li> In the right pane, right-click a Recipient Update Service, and then click Properties.</li> In the Select a property to view box, click gatewayProxy.</li> In the Values box, click the address type that is experiencing this issue, and then click Remove.</li> Click OK, and then quit ADSI Edit.</li></ol> </li> In Exchange System Manager, click Recipient Update Services under Recipients.</li> Right-click a Recipient Update Service in the right pane, and then click Update Now to trigger the Recipient Update Service to update objects. Do this for each Recipient Update Service in the right pane.</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
The MSExchangeSA event ID 2035 may be logged when the AddrType attribute does not replicate from the Exchange Server 5.5 directory to the Active Directory directory service.

For additional information about how to troubleshoot replication of the AddrType attribute, click the following article number to view the article in the Microsoft Knowledge Base:

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

Additional query words: RUS third-party 3rd party fax connector RG AG DC

Keywords: kbprb KB286356

-

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

© Microsoft Corporation. All rights reserved.