The exchange server address list service failed to respond : Microsoft, Exchange, 2007

May 9, 2008 09:54am pdt

1. Sembee 998,732
2. kieran_b 585,215
3. mass2612 433,666
4. mattee76 308,229
5. LeeDerby... 257,333
6. peakpeak 247,182
7. abhaigh 210,299
8. Paka 202,599
9. isaman07 183,512
10. ATIG 172,054
11. TechSoEasy 152,392
12. tigermatt 150,022
13. Zanemwest 142,817
14. darkstar3d 135,864
15. nfmartins 121,170

1. Sembee 19,154,918
2. redseate... 2,303,745
3. rakeshmi... 1,588,757
4. Exchange... 1,324,209
5. Vahik 1,256,508
6. flyguybob 1,176,399
7. Kidego 1,167,655
8. LeeDerby... 1,109,856
9. ATIG 928,480
10. mass2612 920,452
11. kristinaw 872,406
12. ikm7176 765,259
13. TechSoEasy 752,304
14. marc_nivens 633,965
15. amaheshwari 611,971

02.29.2008 at 05:23AM PST, ID: 23203598

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.3

The exchange server address list service failed to respond

Zones: Exchange Email Server, Email Servers, Windows 2003 Active Directory

Tags: Microsoft, Exchange, 2007

We're currently using Microsoft Exchange 2007 in our business and today we spotted this problem when trying to add a new user

"The exchange server address list service failed to respond. this could be because of an address list or policy configuration error"

We have the one main server currently running, with a Virtual Machine running with the Client Access role, but this is only temporary. Could any one shine some light on how to fix this problem?

Many thanks.

Start your free trial to view this solution

Question Stats

Zone: Software

Question Asked By: cintra

Solution Provided By: glaxosmith

Participating Experts: 11

Solution Grade: A

Translate:

Loading Advertisement...

Microsoft

Internet Protocols
Applications

Development
OS

Hardware
Windows Security

Apple

Operating Systems
Hardware

Programming
Networking

Software

Internet

Search Engines
File Sharing
WebTrends / Stats
Spy / Ad Blockers

Web Browsers
New Net Users
Web Development
Chat / IM

Anti Spam
Web Servers
Anti-Virus
Email Clients

Gamers

Tips
Online / MMORPG
Puzzle
Emulators

Action / Adventure
Role Playing
Consoles
Game Programming

Strategy
Sports
Misc
Computer Games

Digital Living

Hardware
New Net Users
New Users

Software
Digital Music
Gaming World

Home Security
Apple
Networking Hardware

Virus & Spyware

Vulnerabilities
IDS
Encryption
Anti-Virus

Operating Systems Security
Software Firewalls
WebApplications
Cell Phones

Operating Systems
Internet
Hardware Firewalls

Hardware

Handhelds / PDAs
Displays / Monitors
Components
Networking Hardware

Peripherals
Laptops/Notebooks
Storage
Servers

Desktops
New Users
Misc
Apple

Software

System Utilities
Industry Specific
Network Management
Photos / Graphics
Page Layout
VMWare
Misc
Web Development

OS
CYGWIN
Voice Recognition
Message Queue
Quality Assurance
Security
Firewalls
MultiMedia Applications

Development
Database
Office / Productivity
Business Management
OS/2 Apps
Server Software
Internet / Email

ITPro

OS
Storage
Encryption
Operating Systems Security
Apple Hardware
Laptops & Notebooks
Servers
Networking Hardware
Peripherals

Devices
Displays / Monitors
WebTrends / Stats
Search Engines
Firewalls
WebApplications
IDS
Vulnerabilities
Email Clients

File Sharing
Spy / Ad Blockers
Web Browsers
Web Servers
Networking
Anti-Virus
Chat / IM
Anti Spam

Developer

Web Servers
Web Browsers
Game Programming
Dev Tools
Industry Specific
Office / Productivity

Database
CYGWIN
Web Development
Search Engines
File Sharing
WebTrends / Stats

Programming
Content Management
Application Servers
Protocols

Storage

Removable Backup Media
Storage Technology
Servers

Grid
Remote Access
Backup / Restore

Misc
Hard Drives

Miscellaneous
Security
Development
Linux
VMWare

MainFrame OS
Unix
Apple
OS / 2
AS / 400

BeOS
Microsoft
VMS / OpenVMS

Database

Oracle
Miscellaneous
MySQL
Software
Sybase
Contact Management
PostgreSQL
Data Manipulation
Clarion
InterSystems Cache

Siebel
MUMPS
OLAP
SQLBase
SAS
GIS & GPS
4GL
Berkeley DB
DB2
Informix

Interbase / Firebird
FoxPro
Reporting
LDAP
Filemaker Pro
MS SQL Server
dBase
MS Access

Security

Misc
Web Browsers
Software Firewalls
Operating Systems Security
File Sharing

Spy / Ad Blockers
Vulnerabilities
WebApplications
IDS
Anti-Virus

Encryption
Anti Spam
Email Clients
VPN
Chat / IM

Programming

Editors IDEs
Installation
Handhelds / PDAs
Multimedia Programming
System / Kernel

Algorithms
Game
Signal Processing
Project Management
Open Source

Database
Misc
Languages
Processor Platforms
Theory

Web Development

Scripting
Blogs
Web Servers
Software
Search Engines
Web Graphics
Images

Internet Marketing
Images and Photos
Components
Document Imaging
Web Languages/Standards
Illustration
WebApplications

Fonts
WebTrends / Stats
Authoring
Digital Camera Software
Miscellaneous

Networking

Protocols
Apple Networking
Network Management
Message Queue
Application Servers
Content Management
File Servers
Email Servers
Misc
Java Editors & IDEs

Wireless
Networking Hardware
Backup / Restore
System Utilities
ISPs & Hosting
Web Servers
Storage Technology
Removable Backup Media
Servers
Broadband

Grid
OS / 2
Novell Netware
Unix Networking
Windows Networking
Security
Telecommunications
Operating Systems
Linux Networking

Other

Community Advisor
Lounge
Community Support
New Net Users

Philosophy / Religion
Math / Science
Miscellaneous
URLs

Expert Lounge
Politics
Puzzles / Riddles

Community Support

Suggestions
New to EE
New Topics
Community Advisor

CleanUp
Announcements
General

Feedback
Input
EE Bugs

02.29.2008 at 05:35AM PST, ID: 21012990

cintra:

Doing Update-EmailAddressPolicy also results in the same error once I specify the policy.

02.29.2008 at 05:56AM PST, ID: 21013152

phylaxict:

Hi there, i have exactly the same problem. Only we have all roles installed on the same server.

02.29.2008 at 06:53AM PST, ID: 21013686

glaxosmith:

This started happening to me last night around 2AM.. I also see more posts coming up about it on other forums. I have been on the phone with PSS for 3 hours now and they still haven't figured it out... it's none of the usual stuff in the KB article on Microsoft's site. None of the solutions in this KB have worked thus far and this is the only KB I have found:

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

02.29.2008 at 07:29AM PST, ID: 21014043

dadarkmcse:

I'll add another voice saying I'm seeing this on my exchange server - one I just rebuilt on Tuesday of this week (2/26) - so I'm wondering if MS pushed down a patch that may have broken things in specific environments.

02.29.2008 at 07:43AM PST, ID: 21014206

glaxosmith:

We are deep into the schema now... MS is taking exports of my config and LDAP dumps to notepad and sending it off for examination. The team lead is also on the case. I hope what we are plugging through solves this, although I stopped taking notes an hour ago because it was just too much.

I also built this server this week on Monday (2/25) and was planning for a big E2K7 migration this weekend. Looks like we may be pulling the plug on that one... boy is this frustrating.

02.29.2008 at 07:46AM PST, ID: 21014245

LindaPol:

So will I, add another voice. This happenend to me also last night. Cannot create new Mailboxes anymore, Cannot update e-mailaddress Policy's , Cannot update send on behalf and make use of Forwarding addresses. everything else is working fine (OWA, Mailboxes and mailflow) Can this have something to do with the date? 29-02, it's a leap-year this year.

02.29.2008 at 07:50AM PST, ID: 21014298

cintra:

Hi guys. I've been doing some research and come across this:

http://msexchangeteam.com/archive/2008/02/28/448251.aspx#comments

I checked and we have Roll up 6 installed and the problem is here for us when it wasn't before. We're going to try removing it on our server and seeing if it solves the issue. It's something you could possibly look into. Could anyone else here confirm they have either Rollup 6 for RTM or Rollup 1 for SP1?

02.29.2008 at 07:55AM PST, ID: 21014352

glaxosmith:

I can add some more info to this. Removing Exchange and reinstalling it does not help. I have done this several times. The only thing I did not do is remove IIS and .NET before trying another reinstall.

There were 2 KB security patches released on 2/26 that were installed which fix security issues in IIS. These can be considered potential culprits. KB942830 and KB942831. Uninstalling these did not correct the problem, but we have yet to uninstall IIS and .NET then reinstall Exchange.

02.29.2008 at 08:00AM PST, ID: 21014410

glaxosmith:

I can confirm I do not have any rollups installed. Just E2K7STD SP1.

02.29.2008 at 08:10AM PST, ID: 21014528

cintra:

Just thought I'd let you know that I removed Rollup 6, restarted our Exchange box but the issue remains.

02.29.2008 at 08:19AM PST, ID: 21014631

glaxosmith:

Is E2K7 on par with E2K3 stability? I am almost wishing I stuck with E2K3 seeing this come up but I feel that E2K7's time has come to be the standard, am I wrong on this one?

Just in case anyone has some similarities in terms of equipment, this is a fresh domain with all new Dell servers shipped in last week. 2xDell 2950 and 1x1950. This E2K7 server is running dual quad xeons with SAS drives on a 2950, and the other two are DC's. Both dual procs using SATA.

All the servers are W2K3R2 STD SP2 with all the latest updates. The A/V clients are Endpoint security 11, and Exchange is running all by itself on a 64bit OS.

02.29.2008 at 09:06AM PST, ID: 21015199

arvehv:

Try to change the date forward with one day, so that you have a system date that is 01.03.2008 instead of 29.02.2008. I tried this now, and then everything worked, tried to go back and received the same error again. Did restart the server between the change of dates.

I therefore guess that the problem will be solved as soon as the clock passes 24:00 today:)

I know this may sound stupid, but it seems like exchange 2007 has trouble with this date.

Assisted Solution

02.29.2008 at 09:42AM PST, ID: 21015602

glaxosmith:

wow you are correct! MS confirmed this bug from their discussion teams. Expect a patch shortly.

How embarrasing... a leap year bug... seriously?

02.29.2008 at 09:50AM PST, ID: 21015675

RTPIT:

We ran across the same problem. Changing the date on the exchange server did not do the trick. Because we're setting up in a completely new environment in our test lab, we were able to set the date on our DCs to be March 1. Rebooted the exchange server made sure it picked up the new date from the DCs and then was able to create new mailboxes again. Great find Arvehv!

02.29.2008 at 09:57AM PST, ID: 21015751

traviskrings:

We are having this exact same issue today! We just set up GAL Sync with ILM yesterday, and started having these issues this morning. We have been assuming that it was all related to ILM 2007, but this post is very interesting. I have microsoft support supposed to be calling me soon. I will post any updates here. Please help if you have any ideas!

02.29.2008 at 10:01AM PST, ID: 21015781

bradster98:

We are working with a new Exchange installation, but the AD is production, so we can't change the date on our DCs. Any other workarounds or fixes?

02.29.2008 at 11:05AM PST, ID: 21016446

glaxosmith:

Update -- Just spoke with the MS team, they are NOT recommending nor supporting the date/time change workaround as they state it will cause other problems. They still do not know when the development team will have a patch out.

My guess is they would not have it out before leap year is over... why scramble with only 12 hours left.

Will have to put HR on hold for that new employee e-mail!

Accepted Solution

02.29.2008 at 12:29PM PST, ID: 21017232

waldofranco:

Take a look on this forum it seems a February 29th date bug !!!

http://forums.microsoft.com/technet/showpost.aspx?postid=2928121&siteid=17&sb=0&d=1&at=7&ft=11&tf=0&pageid=1

Assisted Solution

02.29.2008 at 12:30PM PST, ID: 21017236

waldofranco:

Microsoft answer is do not change date on the system. It could cause other problems, however they state some people that changed the date to one day ahead in all servers got it to work. I would just wait until tomorrow to continue with install. That is what I am going to do !!!

After spending hours looking for a solution I called microsoft and they say a lot of people are encountering the same issue today Feb 29th

Waldo

02.29.2008 at 01:03PM PST, ID: 21017527

rreddell:

Well.. I had a server crash last night.. (all my fault)... been trying to reinstall everything.. (exchange 2007).. Been banging my head against the wall on this.. started out with tons of errors.. but got them all worked out but this one...

What are the odds of this happening in today!??? Guess I'll come back after 12am midnight!

Thanks for the thread.. I would be here until after mid night banging my head over and over..

02.29.2008 at 01:14PM PST, ID: 21017634

traviskrings:

We had MS support address that there is an issue, but they have not given us a solution other than to wait for tomorrow.

02.29.2008 at 06:06PM PST, ID: 21019480

syscare:

The fix seems to be restart your Exchange Services or reboot the server

That worked for me now that the 29th Feb has passed :D

All roles (bar edge) running on a vmware session on my laptop

03.03.2008 at 01:26AM PST, ID: 21029968

cintra:

Hi guys. First thing we did this morning was to come in and reboot our Exchange 2007 server; it worked(!)
Who would have thought it would be down to a leap year!

If this is not patched I'm making sure I'm off 29th Feb 2012!! =)

20080236-EE-VQP-29 / EE_QW_2_20070628