Error during fresh install of Exchange 2007

Posted on 2008-02-11
Medium Priority
Last Modified: 2013-11-29
Hi everyone,

I am doing a fresh Exchange 2007 install on a brand new server in a new domain running Server 2003 x64. I was able to install most of the components using a standard install, but it failed with the Mailbox role. I get the following error:

The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error.

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; }'.

Elapsed Time: 00:00:26

This is the only server in a new domain. All the services are running normally, and I have a database created and mounted, with the Default Offline Address Book assigned to it through EMC. However, I keep getting this error, and I can't figure it out.

I have spent time researching this online, and came across this KB article:


I tried all these, and they did not work.

System Attendant is started, and I have rebooted after installation. I also have this error in the setup log:

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.

Since we have Outlook 2003 and Entourage clients, we had to select the option for backwards compatibility.

The purportedSearch attribute of the recipient policies was set to (mailNickname=*) by default.

Nothing on the Internet has turned up anything useful so far, and several websites keep pointing back to that MS KB article. Any help would be appreciated.
Question by:tntmax
  • 4
  • 2

Expert Comment

ID: 20871634
have you created any policy manually??

Expert Comment

ID: 20871647
Exchange 2007 setup has this validation check, that stops the setup if parenthesis "(" ")" or ampersand "&" characters are found in the purportedSearch attribute for a recipient policy already existing in your Exchange 2003 organization.

Simply use ADSIEDIT, navigate to Configuration --> Services --> MS Exchange --> [organization name] --> Recipient Policies.

For each recipient policy, open up the purportedSearch attribute and make a note of the original value. Then clear that value to <not set>. Once this has been done for all recipient policies, setup should complete.
LVL 15

Author Comment

ID: 20871938
Yeah, that's another step that I tried, and that did not work. I believe it did not work because it is not an existing Exchange 2003 organization.
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

LVL 15

Accepted Solution

tntmax earned 0 total points
ID: 20879192
It ended up being a naming issue. The server name was too long, and anything more than 15 characters is not supported. Sigh...
LVL 15

Author Comment

ID: 20879204
Well, at least, we'll find out. The server still has to be re-installed, but that appears to be the problem.
LVL 15

Author Comment

ID: 20889133
yep, it worked.

Featured Post

Learn to develop an Android App

Want to increase your earning potential in 2018? Pad your resume with app building experience. Learn how with this hands-on course.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article provides a step by step guide (with screenshots) showing how to create a new local (test) Administrator user profile in Windows 10 for troubleshooting purposes, and then how to remove it.
The Exchange database may sometimes fail to mount owing to various technical reasons. A dismounted EDB file can be the source of many Exchange errors including mailbox inaccessibility for users. Resolving the root cause of mounting problems becomes …
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Windows 10 is mostly good. However the one thing that annoys me is how many clicks you have to do to dial a VPN connection. You have to go to settings from the start menu, (2 clicks), Network and Internet (1 click), Click VPN (another click) then fi…

600 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question