Error during fresh install of Exchange 2007

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:

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

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


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:

http://support.microsoft.com/kb/935636

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.
LVL 15
tntmaxAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

rehanahmedsCommented:
have you created any policy manually??
0
rehanahmedsCommented:
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.
0
tntmaxAuthor Commented:
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.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

tntmaxAuthor Commented:
It ended up being a naming issue. The server name was too long, and anything more than 15 characters is not supported. Sigh...
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
tntmaxAuthor Commented:
Well, at least, we'll find out. The server still has to be re-installed, but that appears to be the problem.
0
tntmaxAuthor Commented:
yep, it worked.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.