Leap Year Error in Exchange 2007
Trouble with your Exchange 2007 list service failing to respond today? Go home and try again tomorrow - it's a leap year.
Users around the world are reporting in the Microsoft Exchange Server Admin forum that they are unable to create new email and domain acceptance policies today, February 29. When they advance the clock on the Exchange server to March 1, 2008 the policies work as expected.
The issue is preventing admins from moving mailboxes within their Exchange 2007 servers, getting the error:.
"The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error."
If you do decide to change your server time, be sure to stop and disable the Windows Time service on the Exchange server to prevent the time from resyncronizing with the Domain Controllers. Also be aware of other side effects, such as message tracking and log changes, etc.
Update: Nino Bilic from the Microsoft Exchange team has confirmed this problem on the Exchange Team Blog:
"After investigation of this problem we have learned that this problem would occur only if you have started or restarted the Microsoft Exchange System Attendant service between 12:00AM UTC , Feb 29, 2008 and 12:00AM UTC, Mar 1, 2008.
"If you are impacted by this, all that you have to do is restart the Microsoft Exchange System Attendant service after the midnight UTC, March 1, 2008. Restart of the System Attendant will not disrupt your Information Store service."
Labels: Microsoft Exchange 2007, troubleshooting
Subscribe to my feed
posted by Jeff @ 12:13 PM
2 Comments
Links to this post
2 Comments:
Note: I've tested on my single server production environment and haven't had an issue today. My server is running Exchange 2007 SP1. I suspect the issue is affecting multi-server implementations where servers span timezones.
Jeff
This bug has been confirmed by Microsoft:
Symptoms
During following operations you may 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”.
a. Move mailbox (Move mailbox completes successfully)
b. Create mailbox, mailbox store, public folder or public folder store
c. Change email related properties on a mailbox or public folder
d. Any operation using the RUS API
Information
· The above problem will clear itself at UTC/GMT 00 (7pm Eastern/4pm Pacific).
· You may have to restart the System Attendant after the above time to get past the problem.
· Problem is due to a mathematical problem in how Exchange interprets the date.
· Because this is a bug, we would non-decrement and refund the case
Post a Comment
Thank you for posting a comment! It is my hope that you find the information here useful. Let me know (and others) if this post helped you out or if you have a comment or further information.
Links to this post:
Create a Link
<< Home