General discussion

Locked

Exchange 5.5 memory leak/GO AWAY!

By kokomoarnold ·
We have an NT box (SP6a) ALR Revolution 6X6 with a memory leakage problem. It runs Exchange 5.5 SP4 (as the IMC only) and is the print server for a large office building also. We began getting high counters for Pool Nonpaged Bytes yesterday and found that above a value of 60 no one could print. Normal should be below 20. Regular resource usage is low: processors, memory, disk space are all barely breathing hard. Counters for Pool Paged Bytes are also very high. IMS Traffic counters for Exchangeare also high (Messages Entering MTS-IN and Leaving MTS-OUT). Other Exchange counters very low. Spooler service takes a long time to come up...but system resources are not taking a hit.

Service packs rerun, RAM checked and re-seated. 512K RAM, pagefile 1046 MB (523-768MB on both partitions), six Pentium Pro 200 processors, disk space to burn. Nothing helps. Nothing on TechNet either: two docs touch on the issue but not the exact problem, and provide "fixes" that have not been fully tested...Q272194 and Q293841.
Relevant errors in Event Viewer: event IDs 2019, 2021, and 9316.
Running McAfee NetShield 2000 vdef 4.0.4135, engine 4.1.40. Have ruled out virus attack.
How to deal with this resource problem? We want to free up memory and stop the leakage. This server is critical!

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Exchange 5.5 memory leak/GO AWAY!

by NetTek In reply to Exchange 5.5 memory leak/ ...

The following articles explain ways in which you can isolate a memory leak.

Q130926
Q150934
Q268343

It can be very difficult to find memory leaks. You will need to have patience, and make sure you gather enough data.

Collapse -

Exchange 5.5 memory leak/GO AWAY!

by kokomoarnold In reply to Exchange 5.5 memory leak/ ...

Poster rated this answer

Collapse -

Exchange 5.5 memory leak/GO AWAY!

by kokomoarnold In reply to Exchange 5.5 memory leak/ ...

Sorry, but I knew that already. I have already identified that the contention is between the Exchange System Attendant, the Spooler service and TCP/IP Print services. The issue is how to FREE UP those bytes held by leaks, and stopping those serviceson a production server is not going to cut it. I am not about to tell 600 people they cannot print but can still email the outside world, nor am I going to tell 20,000 people they can only send email to each other within the intranet because the IMSis disabled to conserve resources, and be happy because 600 people in the central office can still print. Stopping Exchange or the spooler clears this up fine, believe me. It's not an option, though.

This may have been exacerbated by a hardware-related issue due to overheating 2 weeks previous...but most evidence points to software.

Collapse -

Exchange 5.5 memory leak/GO AWAY!

by kokomoarnold In reply to Exchange 5.5 memory leak/ ...

This question was closed by the author

Back to Windows Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums