[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now


Store.exe not releasing memory?

Posted on 2014-04-27
Medium Priority
Last Modified: 2014-05-02
We are running SBS 2011 with Exchange 2010 on a server with 16G of memory. Recently there are have been issues with remote logins via RWW. Users can connect to the sharepoint site but when they try to continue on to make a connection to one of the remote machines nothing happens.

While troubleshooting I am finding that memory usage is at or close to 100% with store.exe using most of the available memory (about 8.5G). If I stop then restart the service the store.exe memory usage drops way down to a reasonable level and users are then able to connect remotely without difficultly. Memory usage will then remain stable for 5 or 6 hours but eventually when I check back store.exe has again sucked up all the memory and users cannont connect.

I know that many say that it is normal for store.exe to use all available memory but I do not see this behavior on two other SBS machine I manage. At the very least it would appear to me that store.exe is not releasing memory back to the pool when it is needed. I also don't see why it would be necessary for store.exe to use 8.5G of memory to support email for 12 users when no one is in the office.

The remote connection issue started to appear within the last couple of weeks. This would coincide with some updates that were installed at or around that time (Exchange Rollup 8 - 4/14 and Sharepoint SP2 with a couple of other Sharepoint updates on 4/18).

I am considering rolling back the updates but am concerned about compounding problems. Any thoughts or troubleshooting tips would be appreciated.
Question by:pmckenna11
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
LVL 71

Expert Comment

ID: 40025923
Store.exe only releases memory if it is told to do so. MS Apps should play very well with Store.exe, besides the delay needed to write back changed content of the Store.exe memory area. However, Store.exe might be very slow in releasing memory, leading to out-of-memory timeouts. If users retry a second time, they should get enough memory to perform RWW. It shouldn't be that way, as RWW is just another MS service, but I assume RWW and SBS are not designed to work together that well.

The reason Store.exe uses all available memory, if reasonable, is to cache the mailboxes as much as possible, to speed up access. So not the number of mailboxes determines the memory, but the overall size of mailboxes plus index into them.
LVL 57

Expert Comment

by:Pete Long
ID: 40025930
Yep this is normal behaviour
Exchange Store.exe Taking 99 - 100% Physical Memory

Author Comment

ID: 40025934
So a couple of things. First only a couple of users have mailboxes approaching 2Megs. Most have much less and all are capped at 2Megs so I don't see how caching could use 8.5 Gigs. Also the jump in memory seems to happen abruptly at some point after hours of running at a much lower usage.

Secondly this behavior is new and I don't see it on other SBS machines I manage. One in particular makes far heavier usage of Exchange.

Finally RWW is Sharepoint and is obviously an MS app. SBS was designed to meld all these services into a single box so they should all play well together.

Everything works fine until store.exe takes memory usage up to 100%. At that point only  does the remote access break. It remains broken until store is restarted. Repeating logins does not help. Restarting store temporarily solves the problem so it would appear that the very least store is not releasing memory as it should.
Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.


Author Comment

ID: 40025943
I have seen that page before. In another post he describes a way of putting a cap on the amount of memory store uses. I was thinking about using a cap but again this behavior is new and I don't see it on other SBS servers I manage. I just checked 2 SBS servers which have been running undisturbed for a few weeks and store is not using excessive amounts of memory on either. There is plenty of unallocated memory on both.

So the whole store memory usage may be a Red Herring but what is certain is that stopping Store and releasing memory solves my users remote connection issues. Perhaps the problem is with Sharepoint instead and the way it is asking for memory
LVL 71

Expert Comment

ID: 40025958
Store.exe using a lot of memory is nothing upsetting, as we all agree on.
Not releasing memory is. Probably it thinks it needs that memory permanently - do you see a lot of work done by Exchange over a longer period?
As I see it you would now need means to debug what Store.exe knows about its memory - but I don't know of any diagnostics available here. Maybe some performance counters ...
LVL 63

Assisted Solution

by:Simon Butler (Sembee)
Simon Butler (Sembee) earned 400 total points
ID: 40026014
Rollup 8 - sounds like you aren't on the latest service pack for Exchange 2010. Which build are you on? It should be 14.3 - if not then you are not on Service Pack 3 - update the machine and then reboot.


Assisted Solution

by:Carl Gray
Carl Gray earned 800 total points
ID: 40026183
I agree with Simon, update to SP3, and then update to Update Rollup 5 which is the latest for SP3.

After the Sharepoint updates did you run psconfig?

Finally, have you you updated IE on clients recently?
If so try adding the rww URL to the trusted sites under the security tab and add the URL to the compatibility list.

Hope this helps,
LVL 16

Accepted Solution

R. Andrew Koffron earned 800 total points
ID: 40026306
I see this issue on many SBS2011 Machines(in the last several months, so I assume it's update related), they always seem to hover around 90-92% memory use, but RWW stops working at about 95%. Super annoying like it's designed to fail.

check out this article.  you need to limit the exchange DB and the SQL for windows internal DB, Sharepoint, and in some cases set IIS items to recycle themselves.


Author Comment

ID: 40026313
Prompted by this page


I decided to go ahead and put a cap on the amount of RAM Exchange is using. That seems to have fixed the problem at least temporarily. Of course this does not address the underlying problem.

I checked and indeed this server is only running SP2. I will update it to SP3 shortly but want to wait a bit to see how it runs with just the memory cap.

I did not run psconfig after installing the Sharepoint updates and after following the link posted by OxfordSBSguy I do see several update related issues that need to be addressed. This is perhaps the root problem! I will get on this right away.

Finally browser compatibility issues are a constant source of headache with RWW. In this case that is not causing the problem but frequently someone changes something in their browser then I get a call.

Author Comment

ID: 40038861
Thanks for all the suggestions. They have been very helpful. The problem has been solved. I put an upper and lower limit on the amount of memory that Store can use. I also ran psconfig as was suggested. I believe that somehow the Sharepoint Service pack and related updates caused the problem and that running psconfig as suggested by OxfordSBSGuy solved the root problem.

Store has been sitting at 1G (which is the min) everytime I have checked it. It has been a week now with no more problems. Thanks!

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
Know the reasons and solutions to move/import EDB to New Exchange Server. Also, find out how to recover an Exchange .edb file and to restore the file back.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses

649 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question