[sniffer] Application popup error smtp32.exe imail1.exe
I've been getting the error message below for the past two weeks. I get it for both smtp32.exe and imail1.exe Application popup: smtp32.exe - Application Error : The application failed to initialize properly (0xc142). Click on OK to terminate the application. I did a search on ipswith's kb and I found the following: Microsoft resource (which will cause 0xC142 pop-ups for each E-mail that is received afterwards, until the server crashes). For further details, see: http://www.declude.com/dq.htm under the heading, Flaw #1 - Server crashing: Microsoft's Mystery Heap. I changed the number of delivery threads from 60 to 30 yesterday but I had the same problem this morning. Before making this change the cpu utilization was about 100% most of the time. After the change it decreased to 60%-70%. I noticed that this started happening when I installed message sniffer so today I disabled message sniffer and now the cpu utilization stays below 50% but a few times the queue manager makes it spike to 90%. Is there a way to use message sniffer without having this problem? This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
Re: [sniffer] Application popup error smtp32.exe imail1.exe
At 02:26 PM 3/26/2004, you wrote: I've been getting the error message below for the past two weeks. I get it for both smtp32.exe and imail1.exe Application popup: smtp32.exe - Application Error : The application failed to initialize properly (0xc142). Click on OK to terminate the application. snip I changed the number of delivery threads from 60 to 30 yesterday but I had the same problem this morning. Before making this change the cpu utilization was about 100% most of the time. After the change it decreased to 60%-70%. It seems that your server is heavily loaded so all adjustments are likely to be touchy. Scott (of Declude) has a good deal of experience dealing with this issue. It involves an undocumented resource in the Microsoft OS that seems to get used up when certain DLLs are loaded such as user32.dll - btw: Based on Scott's recommendation we long ago hacked the libraries on our code warrior compiler so that Sniffer does not link to the user32.dll. At the time this had a profound impact on the Mystery Heap problem for Sniffer. Is there a way to use message sniffer without having this problem? The 2-3 beta will definitely help the CPU usage. The Mystery Heap problem is more difficult to solve - the solution appears to be different on each system. In my experience the most important factor appears to be the number of processes opened by services at any one time. This is why reducing delivery threads usually helps. Others on the list - and especially on the Declude list will have more combined experience with this. If you haven't already you should ask there. _M This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
