The exchange server address list service failed to respond

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

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

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

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.

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.

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.

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?

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.

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

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

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.

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

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

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!

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!

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?

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

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..

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

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

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!! =)

I had this same situation today during an Exchange 2007 setup. I got the error on the Mailbox Server Role at the end of setup.  However, I simply applied the latest Exchange 2007 SP1 rollup fix which was suggested at the end of setup (check for latest updates), rebooted and then ran setup again, to re-add the mailbox server role.

I had this same issue since last evening. What I believe this trigger by taking off line one of my domain controller which holed PDC and other FSMO rolls. After server rebooted I had to restart System attended services to resolve this issue. It working fine now.

Came across this today as I moved the FSMO roles off our old PDC and demoted it to member server. Didn't need to reboot just restart the MS Exchange System Attendant service and it went away.

had a similar situation, restarted the system attendant service did the trick.

Same issue after moving of FSMO roles.  Restarted System Attendant service on the clustered mailbox server and problem was solved. Thanks for the later posts.

Same issue after moving of FSMO roles, same solution, it does work.