Error Id 12800
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: Exchange 2000 event ID: 12800 Previous Versions of Exchange > Exchange Previous Versions - Administration, Monitoring, and Performance Question 0 Sign in to vote Hi all,I have a question regarding Exchange 2000. Recently, the application log of our Exchange 2000 Server is flooded with messages similar to the following: -Event Type: ErrorEvent Source: MSExchangeISEvent Category: Content EngineEvent ID: 12800Description: Message processing failed because there is not enough available memory (8007000E-80000000).The Exchange Server is running on Windows 2000 Standard Server with 1GB of RAM and is a member server of a Windows 2000 domain. It is fully patched as of last Saturday. This message appears roughly once every minute. The Exchange Server seems to be working fine. It does not seem to run out of virtual memory and the CPU utilization is quite low. I have searched the Internet but there is not much information I can find regarding this issue. I do not think there is any message looping going on since none of the users' mailbox is unusually large. The only thing I can think of is may be a corrupted message in a user's mailbox is causing these messages. Can anyone shed some light on this? Any suggestions are welcome and appreciated.Regards,CapNig. Tuesday, February 09, 2010 12:23 AM Reply | Quote All replies 0 Sign in to vote Hello CapNig,This issue is addressed in KB http://support.microsoft.com/default.aspx/kb/325044. If you are sure that the problem may not be with the VM fragmentation you can also try increasing the size of virtual memory file. Normally, it should be 1.5 times of the physical memory on the server.
| My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out event id 12800 error Users viewing this topic: none Logged in as: Guest Tree Style Printable Version All Forums >> [Microsoft Exchange 2000] >> General >> event id 12800 error Page: [1] Login Message << Older Topic Newer Topic >> event id 12800 error - 31.Dec.2003 4:02:00 PM dpower Posts: 15 Joined: 17.Nov.2003 From: NJ Status: offline Hi,The following error is filling up the application log on my Exch2k server. I have already applied the SP3 Rollup https://social.technet.microsoft.com/Forums/exchange/en-US/6d456698-4a7b-4eea-85bc-751b07381610/exchange-2000-event-id-12800?forum=exchangesvradminlegacy for Exchange, which did not help any ideas. Some users are having trouble getting into their mailboxes. ThanksEvent Type: ErrorEvent Source: MSExchangeISEvent Category: Content Engine Event ID: 12800Date: 12/31/2003Time: 9:10:48 AMUser: N/AComputer: EXCHVS1Description:Message processing failed because there is not enough available memory (8007000E-80000000). Post #: 1 Featured Links* RE: event id 12800 error - 2.Jan.2004 11:59:00 AM Henrik Walther Posts: 6928 Joined: 21.Nov.2002 From: Copenhagen, Denmark http://forums.msexchange.org/event_id_12800_error/m_30559700/tm.htm Status: offline Hello Dpower,Check: http://www.eventid.net/display.asp?eventid=12800&source= (in reply to dpower) Post #: 2 Page: [1] << Older Topic Newer Topic >> All Forums >> [Microsoft Exchange 2000] >> General >> event id 12800 error Page: [1] Jump to: Select a ForumAll Forums---------------------- [Microsoft Office 365] - - Exchange Online [Microsoft Exchange 2013] - - Installation - - General - - Management - - Outlook Web Access - - Mobility - - Migration - - Message Routing - - Secure Messaging - - Compliance - - High Availability - - Unified Messaging [Microsoft Exchange 2010] - - Installation - - General - - Management - - Outlook Web Access - - Mobility - - Migration - - Message Routing - - Secure Messaging - - Compliance - - High Availability - - Unified Messaging [Microsoft Exchange 2007] - - Installation - - General - - Management - - Outlook Web Access - - Mobility - - Migration - - Message Routing - - Secure Messaging - - Compliance - - High Availability - - Unified Messaging [Microsoft Exchange 2003] - - Installation - - General - - Server Security - - Outlook Web Access - - Message Routing - - Public F
Monitor an unlimited number of servers with $49/year With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it http://www.eventid.net/display-eventid-12800-source-MSExchangeIS-eventno-1105-phase-1.htm was still common to see an entire company using just one server, these days that's no longer the case. New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is error id ok and no "red lights" are blinking on any of the servers. read more... Event ID: 12800 Source: MSExchangeIS Source: MSExchangeIS Type: Error Description:Message processing failed because there is not enough available memory (8007000E-80000000). English: Request a translation of the event description in plain English. Concepts to understand: What is the role of the Microsoft Exchange Information Store service? Comments: EventID.Net This issue can occur if the attachment in the e-mail message error id 12800 is corrupted. See ME912068 for a hotfix applicable to Microsoft Exchange Server 2003. This event is logged on public folder servers under a number of heavy stress conditions, including servers that receive NNTP newsfeeds and servers under heavy MAPI client stress. See ME309207 for more information about this event. On a heavily loaded Exchange 2000 Server computer, the Store.exe process may spin in excess of 350 threads, perhaps as many as 800 to 900, and may use up the available virtual bytes. When this happens, event 12800 can occur. See ME267255 for details on solving this problem. x 3 EventID.Net See ME320652 for a hotfix applicable to Microsoft Exchange 2000. See ME812071 and ME837216 for two hotfixes applicable to Microsoft Exchange Server 5.5. See ME325044 for information on hot to troubleshoot virtual memory fragmentation in Exchange 2003 and Exchange 2000. See ME816753 and MSEX2K3DB for additional information on this event. x 3 Woodrow Wayne Collins As per Microsoft: "This problem may occur because Exchange Server may be in a low-memory condition. This situation may be experienced when almost no virtual address space is available for virtual memory". See ME870935 to resolve this problem. x 2 Mike As per Microsoft: "This problem can occur if the message loops in the information store. Each time that the message loops, it i