 |
 |
Don't have an exact answer for you, but: - are there any other errors/warnings in the logs regarding Exchange? - particularly, errors related to database clean-up, size limits being reached, failures to process routine maintenance tasks in normal time limits? this is what i think of off-hand to address an intermittent issue that arises after server has been running for some time. some maintenance task ran in exchange and failed to process leaving something buried in the back-end in a hung or non-responsive state - how high have you cranked up the logging on account creation routines and on exchange server address list. i'd (temporarily!) crank some related settings up to 'verbose' and see what kind of output is generated in logs when you create an account. maybe you'll identify some problem with your mail policies or your address book settings? those are the first things that come to my mind. the 'email address' policy can be touchy and the default address list i have seen generate errors of various importance without ever changing it much. - Joe On Mon, 2010-07-26 at 11:44 -0400, Aldrich, Dak wrote: > Good morning. It is proving to be quite the Monday morning. (And no, > I don’t have a “case of the Monday’s”! BUT I DO HAVE THE RED > SWINGLINE!) > > So, I have this issue with exchange. Had the problem about 3 weeks > ago, and it’s back. I do NOT want to accept “reboot the server” as > the solution. But... May not have a choice... > > When I try to add an email account, either as a new user or to an > existing one, I get the following error. > > Error: > The Exchange server address list service failed to respond. This > could be because of an address list or email address policy > configuration error. > > I also get this message when I attempt to edit the default email > address policy. > > However, once I reboot the server, I am fine. I can create the > account with no issue. So, something somewhere, over time, breaks > this. And I have NO CLUE what it is. Does anyone else have any > ideas? > > And yes, I’ve checked the date on the server. Set to the correct > time / date. As today is NOT February 29th, and it is NOT a leap > year, that is not the issue. Though that seems to be the ONLY > discussion I find on Experts Exchange or via Google on the matter. > > Thanks for any insight anyone might have. > > -dak aldrich > -network admin > -college of music, MSU > [log in to unmask] > -517.432.5045 > -http://comit.music.msu.edu > > ______________________________________________________________________ > This message is only for the intended recipient(s). If you are not > the named recipient you should not read, distribute or copy this > email. Any views or opinions expressed in this email are those of the > author and do not represent those of Michigan State University or the > College of Music. Any information obtained from or contained in these > emails is confidential. No information will be shared or given to any > persons outside of the appropriate department(s). -- Joseph M. Deming System Administrator MATRIX/History 415 Nat Sci Bldg East Lansing, MI 48824 (517) 884-2472 [log in to unmask]