| [size=-1]Event ID: 12002 | ||
| [size=-1]Source | [size=-1]MSExchangeIS | |
| [size=-1]Type | [size=-1]Error | |
| [size=-1]Description | [size=-1]Error <error code> occurred while processing message <> from 'Postmaster'. | |
| Things to understand | What is the role of the Microsoft Exchange Information Store service? | |
| [size=-1]Comments | [size=-1] Mihai Andrei (Last update 5/8/2006): - Error code: 8004011B-820003A2 - Several newsgroup posts suggest that hotfix M829093 solves this issue. Ionut Marin (Last update 4/17/2005): - Error code: FFFFFBFE-8200036D - See M826134. - Error code: 8000FFFF-80000000 - See M829093, M829047, and M838414. - Error code: 80040305-80000000 - See M833607. As per Microsoft: "These events are generated when messages in theuser's mailbox fail to be converted. This can happen when antivirusprograms strip off attachments from messages. The 12002 events aregenerated when a user with these messages in their mailbox, logs on tothe server to access their mail". See MSEX2K3DB for more details on this event. David Spears (Last update 9/15/2004): Istarted to receive this error after a series of hurricanes in Florida.I was constantly rebooting and shutting down the Exchange server toavoid ungraceful shutdowns and power failures. Somehow this lead to acorruption within the installation of Exchange. Reinstalling SP3 forExchange 2000 and all the hotfixes fixed this problem in my case. Wolfgang Henckert (Last update 10/16/2003): Thiserror comes with users being unable to open attachments in theiremails. I checked the security settings that are being propagated bygroup policy and the security settings assigned in the exchange publicfolder - no error there. I was able to open the attachments of olderemails. Doing a proper re-install of SP3 for Exchange worked for me. Charles Peterson (Last update 4/24/2003): Thiswas caused on my system by a single large email that was sent out butwas way over the users mailbox limits. Exchange closed the mailbox andthe email became "traped". The fix was simple, deleted the email, forsome reason this took quite a long time. No services shutdown or rebootwas required. Brian Calaway (Last update 4/16/2003): Ihave had this happen ever since SP3 Exchange 2000 patch. The problem isthe mail client either outlook or Owa will not delete the email. Itsays unknown error when you try to delete it. I port the users email toa pst file and then delete the mailbox. Make sure you verify the pstfile before you delete the mailbox. I then recreate a mailbox for theuser setup outlook on client again and import the pst file. Also this error may have something to do with antivirus scanning M:\drive or database stores corrupting email. See M298924 and M328841. Jason Kelley (Last update 4/16/2003): Thee-mail that was causing the problem was SPAM. When viewing the e-mailfrom OWA the subject contained question marks and binary symbols.Stopping all antivirus software on the exchange server that hosts themailbox allowed me or the enduser to delete the message from either OWAor the Outlook client. Anonymous Restarted my information store, and that seemed to correct the problem. For now. Rob Cawood I have had this problem for about 6 months and have finally resolved it with some help from Microsoft Consulting Services: Cause: It appears that this error is caused by some form of corrupt email in the Information Store. Fix: Give your user account the Exchange Services or Exchange DomainServers groups. Please note you need to remove yourself from DomainAdmins or Administrators as these accounts are explicitly denied accessto users mailboxes. See M262054 for more info. Once you have done this you need to search your M drive of your mailserver for text containing the originating email address contained inthe event log. Once found use your email client, either Web Access or Outlook to openthe offending mailbox and delete the message. Do not delete the filedirectly from Windows Explorer, use the mail client. Please note your company might have some security issues around yourability to access the users mailbox, but then you could always get theuser to delete the offending message. | |
| Links | M262054, M298924, M328841, M826134, M829047, M829093, M833607, M838414, MSEX2K3DB | |
| Search | Microsoft Support - Microsoft Search - Google Groups - Google Microsoft - EventID.Net Queue - More links... | |
| Various | Send comments - Notify me when updated | |
| 欢迎光临 邮件服务器-邮件系统-邮件技术论坛(BBS) (http://bbs.5dmail.cn/) | Powered by Discuz! X3.2 |