It normally does, it starts to cache stuff for faster access.. Someone asked this question the other day. Cant remember if it was in exchange 2k or 2k3 forum.
Inetinfo is a major culprit. At this juncture, the virtual memory it uses is at 585,000k. The physical memory is at 55,000k. The Store.exe is 101,000k virtual and 60,000k physical memory. On the other hand, CPU utilization is low.
This seems to perfectly normal, I have the same issue and all the Research that I have done suggest this a normal operation of exchange. There are a few messages that the server will give you when A serious Memory problem. If everything look ok, then it's normal.
I don't quite believe that a store.exe uses that much but even the rep's at microsoft said it was normal.
My store.exe process frequently runs at 750MB or more, indeed during online defragmentation of the exchange database, Exchange uses all available physical memory by design no matter how much is available, so what you're describing is perfectly normal.
I made a batch file that runs every 2 days through scheduled tasks. The batch file simply restarts the MS exchange info store service, which bets pretty hungry for Physical and Virtual memory.
Benjaminle, here is my batch file code. I run it through sched tasks. The last line just lets me know that the batch file has run. You can put a pause statement after each command for testing purposes, coz sometimes there are other dependent services that have to be stopped first.
Cheers
@echo off
net stop "microsoft exchange information store"
net start "microsoft exchange information store"
net send 192.168.0.1 INFO STORE SERVICE was restarted.
exit
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.