Microsoft KB Archive/294222

= XADM: Recipient Update Service Does Not Process Users in Remote Windows 2000 Domains =

PSS ID Number: 294222

Article Last Modified on 6/6/2003

-

The information in this article applies to:


 * Microsoft Exchange 2000 Server

-



This article was previously published under Q294222



SYMPTOMS
The Exchange 2000 Recipient Update Service may not be able to process users who are in a &quot;remote&quot; Microsoft Windows 2000 domain (where a remote domain is a domain that the Exchange 2000 Recipient Update Service server is not a member of). For example, if your Exchange 2000 server (which also runs the Recipient Update Service) resides in a domain that is called domain A, and users reside in a domain called domain B, domain B is considered a remote domain, and you must manually create a Recipient Update Service for this remote domain by using Exchange System Manager.

If Diagnostic Logging is turned up to Medium on the Service Controller diagnostic logging object under MSExchangeAL, the following events may be logged in the Event Viewer Application log:

Event Type: Error

Event Source: MSExchangeAL

Event Category: Service Controller

Event ID: 8247

Date: 2/2/2001

Time: 2:30:23 PM

User: N/A

Computer: EXCHANGESERVER

Description:

Address List Service is restarting this instance because policy group provider

'CN=Recipient Policies,CN=Exchange Organization,CN=Microsoft

Exchange,CN=Services,CN=Configuration,DC=DOMAIN-A,DC=com':'MAD.EXE' returned a

fatal error. Recipient Update Service (EXCHANGESERVER)

Event Type: Error

Event Source: MSExchangeAL

Event Category: Service Controller

Event ID: 8231

Date: 2/2/2001

Time: 2:30:23 PM

User: N/A

Computer: RootServer

Description:

Permanent failure reported by policy group provider for 'CN=Recipient

Policies,CN=Exchange Organization,CN=Microsoft

Exchange,CN=Services,CN=Configuration,DC=DOMAIN-A,DC=com':'MAD.EXE',

error=8000ffff. Taking provider offline.



CAUSE
This issue can occur if Domain Name System (DNS) name resolution between the Exchange 2000 server that is running the Recipient Update Service and the target domain controller that is in the remote domain is malfunctioning. Or this can happen if the Short Name for the remote domain DC is not resolvable, even if the FQDN is able to be resolved. The Recipient Update Service may not be able to process users in the remote Windows 2000 domain.



RESOLUTION
To resolve this issue, add an A record on the DNS server for the target domain controller that is in the remote domain.

For example, if the Recipient Update Service is set up as follows

Recipient Update Service (DOMAIN-A)

Exchange Server: [EXCHANGESERVER]

Domain Controller: [DOMAIN-B-DC]

Add an A record on the DNS server for the DOMAIN-B-DC domain controller.

Add the appropriate DNS suffixes for the child domain and ensure the shortname can now be resolved.



WORKAROUND
To work around this issue, manually create an entry in the Hosts file in the following location:

Winnt\System32\Drivers\Etc\Hosts

For example, if the Recipient Update Service is set up as follows

Recipient Update Service (DOMAIN-A)

Exchange Server: [EXCHANGESERVER]

Domain Controller: [DOMAIN-B-DC]

and DOMAIN-B-DC has an IP address of 192.168.1.2, create the following entry in the Hosts file:

127.0.0.1 localhost

192.168.1.2 DOMAIN-B-DC

Additional query words: RUS

Keywords: kbprb KB294222

Technology: kbExchange2000Search kbExchange2000Serv kbExchange2000ServSearch kbExchangeSearch

-

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

© 2004 Microsoft Corporation. All rights reserved.