Exchange Server Forums

Mailbox Role failed to install

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Installation >> Mailbox Role failed to install

Page: [1]

Message

<< Older Topic Newer Topic >>

Mailbox Role failed to install - 27.Dec.2006 11:19:28 AM

thorsten

Posts: 2
Joined: 27.Dec.2006
Status: offline

Hello,

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"

but didn't help. what can I try?

Greetings Thorsten

Post #: 1

Featured Links*

RE: Mailbox Role failed to install - 28.Dec.2006 5:40:02 AM

thorsten

Posts: 2
Joined: 27.Dec.2006
Status: offline

Hello,

I solved the problem doing the following:

Within ADSI Edit granted the exchange domain servers and also exchange servers full control of RUS, then replicated AD

Greetings and a happy new year
Thorsten

(in reply to thorsten)

Post #: 2

RE: Mailbox Role failed to install - 28.Dec.2006 8:44:08 AM

Henrik Walther

Posts: 6928
Joined: 21.Nov.2002
From: Copenhagen, Denmark
Status: offline

Good to hear you got it solved Thorsten.

Happy New Year to you too!

_____________________________

HTH
Henrik Walther
Lead Moderator/author
MSExchange.org

Follow me on Twitter!

(in reply to thorsten)

Post #: 3

RE: Mailbox Role failed to install - 11.Mar.2007 12:09:16 AM

jcmccain

Posts: 7
Joined: 10.Mar.2007
Status: offline

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.

Jesse

(in reply to Henrik Walther)

Post #: 4

RE: Mailbox Role failed to install - 19.Jul.2007 6:34:16 PM

jwalter10

Posts: 1
Joined: 19.Jul.2007
Status: offline

here's my two cents...

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?

(in reply to jcmccain)

Post #: 5

RE: Mailbox Role failed to install - 9.Oct.2007 1:13:42 PM

blah123

Posts: 1
Joined: 9.Oct.2007
Status: offline

Even after fixing your permission or receipient policy that you deleted, you need to REBOOT the exchange 2007 server

The Exchange 2007 setup caches the problem and will continue to fail even after the issue is resolved

(in reply to thorsten)

Post #: 6

RE: Mailbox Role failed to install - 27.Jan.2008 1:01:25 PM

sommert

Posts: 10
Joined: 27.Apr.2006
Status: offline

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.

(in reply to thorsten)

Post #: 7

RE: Mailbox Role failed to install - 11.Oct.2010 4:00:53 AM

pjhutch

Posts: 3578
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

(in reply to sommert)

Post #: 8