Found bug today related to recipients, adding modifiying address policies. Looks like leap year problem. Changing date to 3/1 fixed. Might not be a good idea to change date on your production server, but fix worked. Alternatively, stop/start the MS Exchange SA after midnight. Chuck Swanson ECSA, CHFI, CEH, CEI, LPT, MCT, MCITP/MCTS:Exchange 2007, MCSEecurity, MCSE+Internet, MCNI, MCNE, CTT+, Security+ Swanson Computer Training & Consulting, Inc.

Great...I am on an Exchange course at the moment and 2 of the guys cannot use their virtual machines that are running e2k7 because of the leap year problem. Thanks again MS.

Great...I am on an Exchange course at the moment and 2 of the guys cannot use their virtual machines that are running e2k7 because of the leap year problem. Thanks again MS.

Pretty bizzare. Same thing happend here. Changed the date and then I could add a new user. At least this was found near the top of a Google search.

Glad to hear. I tried to call in to Microsoft first thing am when discovered to alert, but was put on hold for over a 1/2 hour after they took my info :-) I had to hang up :-( Hopefully my post helped others! Make sure you stop/start the MS Exchange SA after midnight if you are reading this after 2/29 and have pbm. Was tested in VPC at 11:59, then failed, stop and start fixed. .

Hi There, Your solution didn't work. I am in Australia and here the date is Mar 1, 2008 still Exchange 2007 give the same error. is there any fix available from microsoft to address this issue? M A L

wait for GMT to pass to march 1st. I had the same issue in australia.

Hi Guys, Sorry, it worked for well for me. After spending 10 hours research, I restarted the CAS/HUB server after 12:00 PM March 1st and MS System Attendant service on Mailbox serverand it fixes the problem.

Hi Guys, It worked for me as well. I changed the time to just over midnight on March 1, stopped and started the Exchange System Attendant and it worked. I was trying to move mailboxes in Exchange 2007 from my Exchange 2003 Server and it was failing with a "the exchange server address list service failed to respond" error.

I installed SP1 for Echange Server 2007 and it worked for me, wothout chanign the date. Nzm

Problem was with yesterdays date. Today's date OK. Systems with SP1 yesterday were reporting problems too. If anything, restarting the System Attendant today should resolve those with the problem. Chuck

I got that error also with SP1, after restarting the service it was gone Thanks

MSExchangeSA service in Ex2K7 is less powerfull compared to Ex2k3 but it is responsible for OAB,address lists , so it is very obvious that any errors related to address list or OAB generation its root cause will be 99% related to MSExchangeSA and like most of MS products the solution is simply Restart-Service MSexchangeSA

Thank you very much for the tip of restarting MS Exchange SA service, I troubleshooted this problem for 4 hours before I found this post. Iam running SP1FYI.

Late to respond, but try this... Go to your exchange server: Start, Run, CMD, Enter Type Ntdsutil, Enter Type LDAP policies, Enter Type connections, Enter Type connect to server "your DC with master roles", Enter ---should say binding to "your DC with master roles" Type quit, Enter Type quit, Enter Type quit, Enter Type exit, Enter Try making the change to Exchange now.