Exchange 2010 store.exe process taking up close to 30GB RAM. Help!

I have an SBS 2011 server running exchange 2010. the server has been running fine until a few weeks ago when the store.exe process keeps using close to 30GB of RAM memory, thus slowing the entire server down.

Can this issue be resolved without having to increase the RAM on the server? If yes, how?

I would imagine 30GB is not normal for an Exchange server with 20 mailboxes...
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Joshua GrantomSenior Systems AdministratorCommented:
It is designed to use as much memory as needed to minimize the use of the paging file. If another process needs memory, the store.exe should allow it to use it.

You can limit the amount it uses for its cache by editing an attribute in ADSI, Im sure I can find a blog somewhere with some instructions.

Here are some instructions from a blog by Peter Bursky.

Is the server up to date on patches?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
cgruberAuthor Commented:

Yes I am aware of how to limit the cache use via ADSI. Will that have any affect on users?

No, the server is not up to date.
Simon Butler (Sembee)ConsultantCommented:
If the server has 32gb of RAM (for example) then you should expect Exchange to take most of it.
However if something else wants the memory then it should give it back when asked for. If that isn't happening (which it seems is the case here) then you need to look at why.

Limiting the memory that Exchange can take isn't the answer, because it just deals with the symptom, not the cause.

What has changed recently? Has something new been installed on the server?
The usual cause of this kind of problem is something like AV or antispam software which hooks in to Exchange. Backup software I have seen do it as well.
If you have AV on the server, ensure that it has the correct exclusions for Exchange configured.

IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

Joshua GrantomSenior Systems AdministratorCommented:
It may effect delivery for a moment when you restart the store.exe service but as long as you give it enough, it shouldn't be a problem.
cgruberAuthor Commented:

if you want to limit the Database Cache to 4 GB of an Exchange 2010 server, set msExchESEparamCacheSizeMax to 131072 (4 GB = 4.194.304 KB / 32 KB).

So based on this, if I want to limit the cache use to 15GB, then I would set the msExchESEparamCacheSizeMax to 491520 ?
Simon Butler (Sembee)ConsultantCommented:
If the server isn't up to date, then you should update it before you start playing around with settings that Microsoft do not recommend. A lot of issues like this are resolved in Exchange service packs and rollups, particularly with third party products being the main cause.

cgruberAuthor Commented:
I've updated the server. store.exe still using the same amount of RAM.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.