I have a native Exchange Organization (one Exchange 2003 Enterprise SP2) and I try to install Exchange 2007. Actually I have a problem installing Mailbox Role. I got the following error (DNS, AD, DC are checked and seems ok), a part of the log: ------------------------------------------------------------ Applying RUS policy to the given recipient "MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e" with the home domain controller "srvdc03.domain.local". [27.12.2006 16:50:44] [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. [27.12.2006 16:50:44] [1] Exception : Microsoft.Exchange.Configuration.MonadDataProvider.MonadDataAdapterInvocationException: 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(ADSystemConfigurationSession configurationSession, ADRecipientSession recipientSession, ADRecipient recipient, Fqdn domainController, String serverName, TaskVerboseLoggingDelegate logHandler, TaskWarningLoggingDelegate writeWarning) at Microsoft.Exchange.Configuration.Tasks.RecipientTaskHelper.ApplyRusPolicy(ADSystemConfigurationSession 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(MonadAsyncResult asyncResult) at Microsoft.Exchange.Configuration.MonadDataProvider.MonadCommand.EndExecute(MonadAsyncResult asyncResult) at Microsoft.Exchange.Management.Deployment.ComponentInfoBasedTask.ExecuteScript(String script, Boolean handleError, Int32 subSteps, LocalizedString statusDescription) at Microsoft.Exchange.Management.Deployment.ComponentInfoBasedTask.GenerateAndExecuteTaskScript(InstallationCircumstances installationCircumstance) [27.12.2006 16:50:44] [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; }'. [27.12.2006 16:50:44] [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; }'. [27.12.2006 16:50:44] [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. [27.12.2006 16:56:03] [0] End of Setup [27.12.2006 16:56:03] [0] **********************************************
I tried the following: - delete my "2003 recipient policy" - only use "Default Policy"
I'm having the same problem after installing the first 2007 box on a DC in our domain. Can you give a bit more detail on how to use ADSI edit to give RUS the permissions you mentioned? It'd be very helpful.
After running into the similar situation and resolving all sorts of these listed permissions issues on the RUS, to no effect, the trick that did it for me was to put two entries into the DNS for the adapter on the new exchange server - i couldn't say which one it was, but finally the ldap appeared to be able to communicate and update ok, and the address list server began to respond.
To find this, I noticed an error in the event viewer saying that it could not register the adapter GUID in DNA (one of those long GUID strings). While the IP A record was entered just fine, this one was missing. based on looking at old server records. Looking at the existing records i noticed two places my new exchange server did not exist:
1) forest level |---_msdcs I added a new CNAME record to using the GUID found in the event viewer 2) forest level |---_msdcs |---domains |---domainGUID |---tcp I Added a new SRV record with _ldap protocol, simlilar to existing records for the new server
Hope this helps someone else...it took me two weeks of pounding this to come up with the error. Anyone know why these records wouldn't auto popluate, since there is nothign in the install instructions that says i have to do this manually first?
Can you expand on this a bit more please? How exactly did you use ADSI to do that? Was that an MS recommendation. Thanks in advance.. I have the same issue.
Posts: 3503
Joined: 21.Jul.2001
From: W Yorks, England
Status: offline
1. Load ADSIEdit.msc 2. Connect to Configuration container 3. Browse to Configuration, Services, Microsoft Exchange, <org. name>, Recipient Policies 4. Right click, select Properties, Security. 5. Add the security groups (see prev message) and click ok
If you want to use Powershell, use Add-ADPermission command with the container to change.
_____________________________
Peter Hutchison MCP Exchange Administrator University of Huddersfield
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2007] >> Installation >> Mailbox Role failed to install 
Mailbox Role failed to install - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
