On an exchange 5.5 sp4 server running on win2k, the IMC shut down because
the IS complained that:
"Message processing failed because there is not enough available memory"
(EVENT ID 12800).

This was followed by events 4182 and 4102 (ims shutting down due to serious
error i.e. 12800)

There was one message in the inbound directory of the IMC and it would not
start until I removed that message.  There was nothing unusual about that
message, it was one that BLAT had generated from a backup process I have
scheduled.  After that restart, it ran for a while and then choked on two
other messages.  One was another BLAT message and the third was a MPEG movie
somebody had mailed in (probably a funny one, I haven't looked at it).  All
3 messages were about 10k bytes in length.

MS has a knowledgebase article about this problem: (or something very close)


http://support.microsoft.com/default.aspx?scid=KB;en-us;q325939

Which says:

If the Internet Mail Service receives a malformed inbound Internet message,
the Internet Mail Service may log event ID 12800, 4182, 4102, and 1001 error
messages in the Application event log, and then stop responding.

RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to
correct the problem that is described in this article. Apply it only to
computers that are experiencing this specific problem.


The fix is a new store.exe version 5.5.2656.60.  I am currently running
store.exe 5.5.2654.50 (a post sp4 fix).  After zapping those 3 emails, the
IMC has been running for about an hour now with no problems (and it has
never had a problem before).  Does anyone have any insight on this problem?
If it happens again I will call MS and request the patch, as it is not
available for download.

Tom


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to