The gatewayProxy attribute on the Recipient Update Service object is not cleared

The gatewayProxy attribute of the Recipient Update Service object is not cleared after a recipient policy is applied. The gatewayProxy attribute stays populated with proxy entries from a specific recipient policy that was previously applied.

This issue may occur if any of the following conditions are true:

• There are problems with the Microsoft Active Directory directory service replication. If Exchange System Manager uses a different domain controller than the domain controller that is used by the Exchange 2000 computer that runs the Recipient Update Service, there may be latency issues or other issues with Active Directory replication.
• There are non-transaction timing issues that cause changes to be lost. This behavior may occur when both Exchange System Manager and the system attendant (Mad.exe) access the gatewayProxy attribute at the same time. Both Exchange System Manager and Mad.exe try to read the attribute, make changes, and then write the attribute back.
  
  The following scenario helps to illustrate this issue:
  
  Note In this example, Mad.exe tries to remove the address2 value from the gatewayProxy attribute, and Exchange System Manager tries to add the address4 value to the gatewayProxy attribute.
  1. The gatewayProxy attribute contains the address1 value, the address2 value, and the address3 value.
  2. Mad.exe and Exchange System Manager both read the address1 value, the address2 value, and the address3 value.
  3. Mad.exe writes the address1 value and the address3 value.
  4. Exchange System Manager writes the address1 value, the address2 value, address3, and the address4 value.
• You apply a recipient policy, and then the Recipient Update Service or the Mad.exe process is killed, stops responding, or is stopped. In this scenario, the gatewayProxy attribute is not cleared because it has not completed processing the objects that apply to the policy. When you restart the Recipient Update Service or the Microsoft Exchange System Attendant service, the Mad.exe process does not remove or clear the gatewayProxy attribute. Specifically, the hrEndTransaction function is not called.

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. To resolve this issue:

1. Set the Recipient Update Services to never run. To do so:
   
   Note Before you change the Recipient Update Services setting, note its current value, because you must change it back to its original setting later.
   1. Start Exchange System Manager.
   2. Click Recipients.
   3. Click Recipient Update Services.
   4. In the right pane, right-click a Recipient Update Service, and then click Properties.
   5. On the General tab, in the Update interval list, click Never run.
2. Wait approximately one to two minutes.
3. Use ADSI Edit or the LDP tool (both tools are included in the Microsoft Windows 2000 Support Tools on the Microsoft Windows 2000 CD-ROM) to manually clear the gatewayProxy attribute. To use ADSI Edit to clear the attribute:
   1. Click Start, point to Programs, point to Windows 2000 Support Tools, click Tools, and then click ADSI Edit.
   2. Click the Configuration container.
   3. Click CN=Configuration,DC=Domain Components.
   4. Click CN=Services, click CN=Microsoft Exchange, click CN=Organization Name, and then click CN=Address Lists Container.
   5. Click CN=Recipient Update Services.
   6. In the right pane, right-click the domain Recipient Update Service, and then click Properties.
   7. In the Select a property to view list, click gatewayProxy.
   8. In the Value(s) box, click any address type that remains populated, and then click Remove.
   9. Click OK, and then quit ADSI Edit.
4. Force a directory replication to occur after you clear the gatewayProxy attribute. Make sure that replication occurs before you let the domain Recipient Update Service run again.
5. Set the domain Recipient Update Service schedule back to its previous required schedule setting.
6. If you have to, reapply the specific recipient policies.

The Mad.exe process removes the completed entries from the gatewayProxy attribute. If you view the list that is contained in the gatewayProxy attribute, you cannot determine if any particular entry has been completely applied and can be removed. The Exadmin.dll file contains the code that adds entries to the list.

For additional information about how the Recipient Update Service applies recipient policies, click the following article number to view the article in the Microsoft Knowledge Base:
ADSI Edit and the LDP tool are included with the Windows 2000 Support Tools.

For additional information about how to install the Windows 2000 Support Tools, click the following article number to view the article in the Microsoft Knowledge Base: