Error message when you try to install an Exchange 2007 mailbox role: "The Exchange server address list service failed to respond"

When you try to install a Microsoft Exchange Server 2007 mailbox server role in an existing Microsoft Exchange Server 2003 organization, the operation fails. Additionally, you may also experience the following symptoms:

• You receive the following error message:
  The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error.
• The following events are logged in the Application log:

  Event ID: 1002
  Event Category: Microsoft Exchange Setup
  Event Source: MSExchangeSetup
  Event Type: Error
  Date: 5/1/2007
  Time: 1:46:43 PM
  Description: Exchange Server component Mailbox Role failed. Error: The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error.

  Event ID: 8325
  Event Category: Address List Synchronization
  Event Source: MSExchangeAL
  Event Type: Error
  Date: 5/1/2007
  Time: 1:52:04 PM
  Description: The service can't work properly because Email Address Policy 'CN=XXXX,CN=Recipient Policies,CN=corpPT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=XXX,DC=com' has an invalid filter rule (PurportedSearch). The error is 'Invalid token.'. Use the Exchange Management Console to correct this problem. New users, contacts, and groups won't be fully provisioned until this is fixed.

• The following entries are recorded in the ExchangeSetup.log file:

  [5/18/2007 2:21:49 PM] [2] Applying RUS policy to the given recipient 
  "MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e" with the home domain controller 
  "COMPUTERNAME.domain.com".
  

  [5/18/2007 2:21:49 PM] [2] [ERROR] The Exchange server address list service failed 
  to respond. This could be because of an address list or email address policy 
  configuration error.
  

  [5/18/2007 2:21:49 PM] [1] Exception : 
  Microsoft.Exchange.Configuration.MonadDataProvider.MonadDataAdapterInvocationExcepti
  on: The Exchange server address list service failed to respond. This could be 
  because of an address list or email address policy configuration error. It was 
  running command '$error.Clear(); $count=0; $ExchangeServers = Get-ExchangeServer 
  -DomainController $RoleDomainController; foreach($server in $ExchangeServers) { 
  if(($server.AdminDisplayVersion.Build -gt 641) -and ($server.IsMailboxServer -eq 
  $true)) { $count++; } } if( $count -eq 1) { Set-OrganizationConfig 
  -DomainController $RoleDomainController; }'. ---> 
  Microsoft.Exchange.Data.Directory.RusServerUnavailableException: The Exchange 
  server address list service failed to respond. This could be because of an address 
  list or email address policy configuration error.
  at 
  Microsoft.Exchange.Data.Directory.Recipient.RecipientUpdateService.LocateServer()
  at 
  Microsoft.Exchange.Configuration.Tasks.RecipientTaskHelper.ApplyRusPolicy(ADSystemCo
  nfigurationSession configurationSession, ADRecipientSession recipientSession, 
  ADRecipient recipient, Fqdn domainController, String serverName, 
  TaskVerboseLoggingDelegate logHandler, TaskWarningLoggingDelegate writeWarning)
  at 
  Microsoft.Exchange.Configuration.Tasks.RecipientTaskHelper.ApplyRusPolicy(ADSystemCo
  nfigurationSession configurationSession, ADRecipientSession recipientSession, 
  ADRecipient recipient, Fqdn domainController, String serverName, 
  TaskVerboseLoggingDelegate logHandler, TaskErrorLoggingDelegate writeError, 
  TaskErrorLoggingDelegate throwTerminatingError, TaskWarningLoggingDelegate 
  writeWarning)
  --- End of inner exception stack trace ---
  at 
  Microsoft.Exchange.Configuration.MonadDataProvider.MonadCommand.ClosePipeline(MonadA
  syncResult asyncResult)
  at 
  Microsoft.Exchange.Configuration.MonadDataProvider.MonadCommand.EndExecute(MonadAsyn
  cResult asyncResult)
  at 
  Microsoft.Exchange.Management.Deployment.ComponentInfoBasedTask.ExecuteScript(String
  script, Boolean handleError, Int32 subSteps, LocalizedString statusDescription)
  at 
  Microsoft.Exchange.Management.Deployment.ComponentInfoBasedTask.GenerateAndExecuteTa
  skScript(InstallationCircumstances installationCircumstance)
  

  [5/18/2007 2:21:49 PM] [1] [WARNING] An unexpected error has occurred and a Watson 
  dump is being generated: The Exchange server address list service failed to 
  respond. This could be because of an address list or email address policy 
  configuration error. It was running command '$error.Clear(); $count=0; 
  $ExchangeServers = Get-ExchangeServer -DomainController $RoleDomainController; 
  foreach($server in $ExchangeServers) { if(($server.AdminDisplayVersion.Build -gt 
  641) -and ($server.IsMailboxServer -eq $true)) { $count++; } } if( $count -eq 1) { 
  Set-OrganizationConfig -DomainController $RoleDomainController; }'.
  

  [5/18/2007 2:21:49 PM] [1] [ERROR] The Exchange server address list service failed 
  to respond. This could be because of an address list or email address policy 
  configuration error. It was running command '$error.Clear(); $count=0; 
  $ExchangeServers = Get-ExchangeServer -DomainController $RoleDomainController; 
  foreach($server in $ExchangeServers) { if(($server.AdminDisplayVersion.Build -gt 
  641) -and ($server.IsMailboxServer -eq $true)) { $count++; } } if( $count -eq 1) { 
  Set-OrganizationConfig -DomainController $RoleDomainController; }'.
  

  [5/18/2007 2:28:29 PM] [0] End of Setup

This issue can have any of the following causes.

Cause 1

The CN=Public Folders object is missing under CN=All Address Lists in the Active Directory directory service.

Cause 2

The Allow inheritable permissions from the parent to propagate to this object and all child objects check box is not selected on the CN=All Address Lists object and on the CN=Public Folders object.

Note This may be the cause in an organization in which you modify permissions to configure separate address lists for different groups.

Cause 3

There is a parenthesis or an ampersand in a recipient filter. Additionally, Exchange 2007 uses OPATH filters instead of LDAP filters.

To resolve this issue, use one of the following resolutions as appropriate for your situation.

Resolution for Cause 1

Manually create the CN=Public Folders container, remove the mailbox server role, and then reinstall the Exchange 2007 mailbox role.

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 Server 2003, Microsoft Exchange Server 2007, 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 manually create the CN=Public Folders, follow these steps:

1. Install the Microsoft Windows Server 2003 Support Tools if they are not installed. For more information about these support tools, click the following article number to view the article in the Microsoft Knowledge Base:
   892777  (http://support.microsoft.com/kb/892777/ ) Windows Server 2003 Service Pack 1 Support Tools
   To install the Microsoft Windows Server 2003 Support Tools, follow these steps:
   1. Insert the Windows Server 2003 CD.
   2. Click Start, click Run, and then click Browse.
   3. Locate the following folder on the CD:
      CD_Drive:\Support\Tools
   4. In the Files of Type list, click All Files.
   5. Click SUPTOOLS.MSI, click Open, and then click OK.
   6. Follow the directions in the Windows Support Tools Setup Wizard.
2. Click Start, click Run, type adsiedit.msc, and then click OK.
3. In the CN=Configuration container, locate the following container:
   CN=Services,CN=Microsoft Exchange,CN=ORGANIZATION,CN=Address Lists Container,CN=All Address Lists
   Note Replace ORGANIZATION with the name of the Exchange 2003 organization or with the name of the Microsoft Exchange 2000 Server organization.
4. Right-click CN=All Address Lists, point to New, and then click Object.
5. In the Create Object dialog box, click addressBookContainer under Select a class, and then click Next.
6. Type Public Folders in the Value box for the cn attribute, and then click Next.
7. Type Public Folders in the Value box for the displayName attribute, click Next, and then click Finish.
8. Click OK, and then exit the ADSI Edit snap-in.

Note Allow for sufficient time for replication to finish in a large enterprise that contains many domain controllers and many sites.

To remove the Exchange 2007 mailbox server role, follow these steps:

1. Start the Manage Your Server wizard. To do this, click Start, point to All Programs, point to Administrative Tools, and then click Manage Your Server.
2. Under Managing Your Server Roles, click Add or remove a role.
3. In the Configure Your Server Wizard, click Next on the Preliminary Steps page.
4. On the Server Role page, click the role that you want to remove, and then click Next.
5. On the Role Removal Confirmation page, click to select the Remove the server role check box, and then click Next.
6. On the Server Role Removed page, click Finish.

To install the Exchange 2007 mailbox server role, follow these steps:

1. Start the Manage Your Server wizard. To do this, click Start, point to All Programs, point to Administrative Tools, and then click Manage Your Server.
2. Under Managing Your Server Roles, click Add or remove a role.
3. In the Configure Your Server Wizard, click Next on the Preliminary Steps page.
4. On the Server Role page, click Mail server (POP3, SMTP), and then click Next.
5. On the Configure POP3 Service page, type the domain name, and then click Next.
6. On the Summary of Selections page, click Next, and then click Finish.

Resolution for Cause 2

1. Click Start, click Run, type adsiedit.msc, and then press ENTER.
2. In the CN=Configuration container, locate the following container:
   CN=Services,CN=Microsoft Exchange,CN=ORGANIZATION,CN=Address List Container,CN=All Address Lists
   Note Replace ORGANIZATION with the name of the Exchange 2003 organization or with the name of the Exchange 2000 organization.
3. Right-click CN=All Address Lists, and then click Properties.
4. On the Security tab, click Advanced.
5. Click to select the Allow inheritable permissions from the parent to propagate to this object and all child objects check box, and then click OK.
6. Double-click CN=All Address Lists, and then right-click the CN=Public Folders object.
7. Click Properties, and then click Advanced on the Security tab.
8. Click to select the Allow inheritable permissions from the parent to propagate to this object and all child objects check box, and then click OK.

Resolution for Cause 3

1. Remove the parenthesis from the recipient filter that is specified in the event ID 8325 message that is mentioned in the "Symptoms" section. To do this, follow these steps:
   1. Click Start, click Run, type adsiedit.msc, and then press ENTER.
   2. In the CN=Configuration container, locate the following container:
      CN=Services,CN=Microsoft Exchange,CN=ORGANIZATION,CN=Recipient Policies
      Note Replace ORGANIZATION with the name of the Exchange 2003 organization or with the name of the Exchange 2000 organization.
   3. Right-click the problem recipient policy in the details pane, and then click Properties.
   4. In the Attribute list, click purportedSearch, and then click Edit.
   5. In the Value box, remove the unnecessary characters, and then click OK two times.
2. Change the recipient policy to point to the newly renamed store object.
   
   Note For more information, visit the following Microsoft Web site:
   http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=8325&EvtSrc=MSExchangeAL&LCID=1033 (http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=8325&EvtSrc=MSExchangeAL&LCID=1033)

For more information about how to upgrade OPATH filters, visit the following Microsoft Web sites: