I was, at one time, part of the team that wrote those errors [1]. The ones that I dealt with for E2K7 made sense to when I reviewed or wrote them, or when I wrote the articles that described how to fix them. The error has to be as small and informative as possible, and work from more than one point of view, and be localizable. They are getting better, but there is always room for improvement.
To be better heard remember that for any topic or error that you can rate or comment on in the help on MSDN or on Technet comment it with your feedback. That feedback is automatically entered in to the bug tracking software at Microsoft and assigned to the person responsible for the document or area of the code base. If possible the documents are changed, if not the feedback is applied to future work. If you are really bold leave your email address in the comment and ask for a response. I made a point of always responding to those that gave me feedback, most others on the Exchange team are the same way. [1] I had a brilliant editor on my team who made sure that it sounded good when I was done with it. ~Kevinm WLKMMAS powered by 3Sharp<http://www.3sharp.com/>, Always WLKMMAS<http://www.wlkmmas.org/> What is your Zombie Plan? From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 04, 2008 7:57 AM To: MS-Exchange Admin Issues Subject: RE: Strange pair of events twice daily Inside track? HAH. :) I just complain vociferously and often enough that I get responses - sometimes. Error messages are improving, but it's a slow process. They have come a LONG way from Exchange 5.x, when all you got was the MAPI error. All the new .Net-based code in Exchange 2007 has significantly improved error messages - in fact, sometimes you wish the product would just SHUT UP. But having too much is generally preferable to having too little, that's for certain. It sounds weird, but good error messages cause code bloat. The more localized text you have in a program, the bigger the program is, the more memory it takes, the longer reporting an error takes, the more code paths that have to be executed to check for errors, etc. etc. etc. It's a line that has to be tread carefully. As systems grow more capable, there are more/better errors. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Maglinger, Paul [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 04, 2008 9:13 AM To: MS-Exchange Admin Issues Subject: RE: Strange pair of events twice daily Hey Michael, seeing as you appear to have some inside track to Microsoft, can you enlighten us on why they can't put their errors in plain english? I mean, what's the point in being so darn cryptic? ________________________________ From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 04, 2008 8:02 AM To: MS-Exchange Admin Issues Subject: RE: Strange pair of events twice daily I love generic errors. Not. That error is MAPI_E_CALL_FAILED. However, because of the "logon failure" - I would tend to wonder - how many disabled users do you have and do any of them have mailboxes associated with them? Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: ROBERT WILCOX [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 04, 2008 6:52 AM To: MS-Exchange Admin Issues Subject: Re: Strange pair of events twice daily D'oh, I meant all of the Exchange servers in one of the DOMAINS (not admin groups, as it's a single admin group). Thanks Rob ----- Original Message ---- From: ROBERT WILCOX <[EMAIL PROTECTED]> To: MS-Exchange Admin Issues <[email protected]> Sent: Wednesday, 4 June, 2008 11:50:05 AM Subject: Strange pair of events twice daily Hi all, We have a dozen Exchange 2003 SP 2 servers, split across two domains, all in the same Administrative Group. On all of the Exchange servers in one of the Admin groups, we get the following pair of events logged : Event Type: Error Event Source: MSExchangeIS Event Category: General Event ID: 9562 Date: 6/3/2008 Time: 12:04:08 AM User: N/A Computer: XYZABC Description: Failed to read attribute msExchUserAccountControl from Active Directory for /o=First Organization/ou=First Administrative Group/cn=Recipients/cn=XYZABC. Event Type: Error Event Source: MSExchangeIS Mailbox Store Event Category: Logons Event ID: 1022 Date: 6/3/2008 Time: 12:04:08 AM User: N/A Computer: XYZABC Description: Logon Failure on database "First Storage Group\Mailbox Store (XYZABC)" - Windows 2000 account stoop\Administrator; mailbox /o=First Organization/ou=First Administrative Group/cn=Recipients/cn=XYZABC. Error: -2147467259 They're logged at 4 minutes past minute, then 40 minutes past. They're logged again a 4 minutes past mid-day then 40 minutes past. Then again at midnight. I checked to see if the computer account XYZABC, had someone got a mail address, but it doesn't, and I don't see it listed in the list of mailboxes on the store under the server object in ESM. Saw a few pointers towards the RUS needing to be rebuilt - done that, and the same error's are still logged. Would I need to to the Enterprise RUS, and the domain RUS for the other domain as well? Thanks Rob ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
