tag:blogger.com,1999:blog-1327431886118922768.post6232113112324724744..comments2008-02-29T22:41:00.621-08:00Jeffhttp://www.blogger.com/profile/05278298222887921824jeff@expta.comBlogger2125tag:blogger.com,1999:blog-1327431886118922768.post-6388958859227360862008-02-29T22:41:00.000-08:002008-02-29T22:41:00.000-08:00This bug has been confirmed by Microsoft:<BR/><BR/>Symptoms<BR/><BR/>During following operations you may get the following error: <BR/><BR/>“The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error”.<BR/><BR/> <BR/><BR/>a. Move mailbox (Move mailbox completes successfully)<BR/><BR/>b. Create mailbox, mailbox store, public folder or public folder store<BR/><BR/>c. Change email related properties on a mailbox or public folder<BR/><BR/>d. Any operation using the RUS API<BR/><BR/><BR/>Information<BR/><BR/>· The above problem will clear itself at UTC/GMT 00 (7pm Eastern/4pm Pacific).<BR/><BR/>· You may have to restart the System Attendant after the above time to get past the problem.<BR/><BR/>· Problem is due to a mathematical problem in how Exchange interprets the date.<BR/><BR/>· Because this is a bug, we would non-decrement and refund the caseJeffhttp://www.blogger.com/profile/05278298222887921824noreply@blogger.comtag:blogger.com,1999:blog-1327431886118922768.post-18995177174925124982008-02-29T12:50:00.000-08:002008-02-29T12:50:00.000-08:00Note: 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.<BR/><BR/>JeffJeffhttp://www.blogger.com/profile/05278298222887921824noreply@blogger.com