That's by design. It grabs up 80% or so of available memory and uses it for buffers. Not to worry; It will relenquish RAM to other applications as needed.
I would stop all exchange services,
then run isinteg.exe on the public and private stores,
Use Trends housecall for exchange to check for viruses in the store
Check for hotfixes. I seem to recall a post sp3 hotfix for a store issue. Check for corruption as Packrat states. A damaged store can certainly do that. Look in your application log for related errors or warnings. You can turn up diagnosting logging if necessary.
What version of Anti-Virus are you running? Any add-ons or third party products that could be running in store.exe's memory space?
Exchange services need to be running to do an isinteg check, but you first must dismount the database in question to run an isinteg command against it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.