Re: Store.exe consumes too much RAM
anonymous_at_discussions.microsoft.com
Date: 04/19/04
- Next message: Andrew: "Event id: 9175 - advice"
- Previous message: Todd Hayden: "Information Store taking all available memory."
- In reply to: anonymous_at_discussions.microsoft.com: "Re: Store.exe consumes too much RAM"
- Next in thread: adrien: "Re: Store.exe consumes too much RAM"
- Reply: adrien: "Re: Store.exe consumes too much RAM"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 18 Apr 2004 23:34:30 -0700
sorry I didn't submit my email address or details. My name
is Todd Hayden and my email address is
thayden@robbinswatson.com.au if you'd like to discuss and
share knowledge in regards to this problem.
>-----Original Message-----
>I'm having the same or similar symptoms as you all, i.e.
>exchange system would slow down and stop and usually a
>bunch of services noted in the MS article 316612
>(http://support.microsoft.com/default.aspx?scid=kb;en-
>us;316612&Product=exch2k) would stop, thereby requiring
>the server to be rebooted. We have performed 2 online
>virus scans via Symantec and Computer Associates and both
>report our server as uninfected. Our server (win2k with
>SBS2000, Exchange 2000, SQL Server 2000 all with latest
>updates) used to last up to a week before requiring a
>reboot. That was 10 months ago. Now we must reboot the
>server everyday as it will only last just a little over 1
>day. I have implemented a routine restart early every
>morning to workaround this BIG problem. I have also
>analysed the "virtual bytes" used by the "store" instance
>(i.e. \Process(store)\Virtual Bytes) a few times each
>under different circumstances, including monitoring
>a "silent night", meaning no major programs were running
>and still the store instance consumes the virtual bytes.
>
>We never have more than 34 client machines (32 win2k, 1
Xp
>& 1 win98) logged on to the domain. We have recently
>performed a defrag of the exchange private info store.
>
>We think our latest symptom of this BIG problem is
>universal print failures i.e. sometimes the application
>(it can be any application) will inform you that it can't
>find the printer or that it's not installed (which is a
>load of B.S.), or will seem like it printed successfully
>but will not be print out at all. We have 2 Kyocera FS
>printers and 2 Kyocera KM photocopiers on the network all
>with latest drivers installed. These print failure
>messages used to happen infrequently (10 months ago) but
>now it happens frequently everyday and the workaround is
>to try, try again. Sometimes closing the application,
then
>opening it again will bypass the problem.
>
>My entire log review with pictures to illustrate the BIG
>problem is available via email if you wish to review it
>out of interest.
>
>I've also noticed in Task Manager the Page Faults count
>for "WinMgmt.exe" is approx. 3 million by midday and our
>realtime antivirus scanner, "InoRT.exe" is approx. 6
>million by midday. Whether this has anything to do with
>the BIG problem I'm currently trying to figure out.
>
>P.S. Our AV protection is Computer Associates InoculateIT
>6 (with relevant updates installed).
>
>
>
>
>>-----Original Message-----
>>I have a very similar problem with a client's machine
>>except the machine has been running fine for a year
until
>>the end of January when I added Exchange 2k SP3 and the
>>Post SP3 patches. Since then the Store process
gradually
>>consumes all available memory until the server stops.
>>There are no error messages in the event log bit it is
so
>>slow it may take 10 minutes to open up the Services. The
>>server has been down as low as 4k of available memory.
If
>>I stop the Information Store service and restart it, it
>>takes about 14MB growing to about 50MB by the end of the
>>working day. By the following morning it is using 600MB+
>>out of the installed 1GB of RAM. Incidently the machine
>>is running SBS 2000 with 25 CALs although there are
>>currently only 15 users on the system. Under SBS it is a
>>Domain Controller and SQL Server is in use. Last year
we
>>had a similar problem with SQL Server taking all the
>>memory but it has been limited to 512MB and we have had
>no
>>problems since - until the end of January 2004.
>>The Anti-virus software was changed about the same time
>>from Symantec to AVG for Exchange 2k. Grisoft (AVG
>>authors) have looked at the problem and think it is a
>>Microsoft problem. Anyone got any ideas or do I just
>>throw memory at the problem?
>>
>>James
>>>-----Original Message-----
>>>Scott,
>>>
>>>This is a reply to an e-mail sent to me by Nino Bilic.
>I
>>believe it
>>>answers your previous questions.
>>>
>>>One thing I left out: it is a domain controller.
>>>
>>>Mike
>>>
>>>=======================
>>>Nino,
>>>
>>>Thanks very much for the e-mail. I'll try to describe
>>the situation,
>>>and I'll probably
>>>give you more detail than you need, but I don't know
>what
>>to leave
>>>out, so here's
>>>all of it.
>>>
>>>The problem is that store.exe gets huge. I've been
>>tracking it with
>>>Perfmon and
>>>it can grow to over 800 MB. The server has 2 x Pentium
>>III Xeon 550
>>>MHz processors
>>>and 1 GB of RAM. When store.exe gets big, the system
>>gets very
>>>sluggish. Perfmon
>>>shows that page faults and hard faults increase
>>drastically as
>>>store.exe expands.
>>>Two weeks ago, the system had 0.5 GB of RAM, and last
>>week, the system
>>>had 1.5 GB
>>>of RAM. In all 3 memory configurations, store.exe grew
>>to fill the
>>>avialable free memory.
>>>
>>>Store.exe grows when Backup Exec backs up the
>mailboxes.
>>It doesn't
>>>matter if
>>>Backup Exec is run locally on this server, or if this
>>server is backed
>>>up remotely.
>>>I am aware of the memory leak issue described in
>Q314952,
>>but this is
>>>not an issue
>>>here as I have applied SP 3 and post-SP3 Rollup Patch
>>6847.1, and all
>>>the components
>>>listed in the article are at version 6.0.6487.1.
>>>
>>>The first time backup the mailboxes, store.exe grows to
>>about 350-400
>>>MB, and Memory
>>>Usage (as shown by the Task Manager) is about 1000 MB.
>>The second
>>>time, store.exe
>>>grows to about 700-750 MB, and Memroy Usage is 1300
MB.
>>The third
>>>time, it nears 900 MB,
>>>and Memory Usage tops 1500 MB. The trend is
predictable
>>and
>>>repeatable: when mailboxes
>>>are backed up, store.exe grows, Memory Usage exceeds
>>physical memory,
>>>paging goes
>>>through the roof, and response goes down the toilet.
>>>
>>>The Windows 2000 Server Standard Edition is at SP4,
plus
>>all of the
>>>critical updates available
>>>from the Windows Update service. The server has Trend
>>ScanMail for
>>>Exchange, Trend
>>>ServerProtect anti-virus, and Trend OfficeScan anti-
>>virus. It has
>>>Terminal Services enabled
>>>in the Application Server mode.
>>>
>>>On the average, this server doesn't do much more than
be
>>the Exchange
>>>server and host
>>>the anti-virus stuff. There are only 17 mailboxes, and
>>on a busy
>>>8-hour day there may be 100
>>>incoming and 50 outgoing mail messages. Exchange 2000
>>Server was
>>>installed earlier this
>>>month as an upgrade from an Exchange Server 5.5 on a
>>different Windows
>>>2000 Server. The
>>>1.2 GB of information stores were moved using the "Move
>>Mailbox"
>>>method. The 5.5 server
>>>has been retired.
>>>
>>>My perception of slowness is based on several
>>observations: 1) the
>>>time it takes to log on via
>>>Remote Desktop is on the order of 10 seconds when
>>store.exe is small,
>>>and in excess of 45
>>>seconds when the server is paging; 2) the time it takes
>>to start
>>>administrative tasks like
>>>Exchange 2000 System Manager increases from a few
>seconds
>>to 30+
>>>seconds.
>>>
>>>I have two workarounds that seem to work: 1) run MemMAX
>>one or more
>>>times (this is a
>>>program which tries to reclaim memory by taking all
>>available RAM,
>>>forcing other processes
>>>to trim their working sets), 2) stop and start
>>the "Microsoft Exchange
>>>Information Store"
>>>service.
>>>
>>>To sum up, from reading threads in different MS
>>Newsgroups and
>>>searching through the
>>>Knowledge Base, I understand that store.exe is designed
>>to grab all
>>>available memory,
>>>and that this is thought by the designers to be no big
>>deal as Windows
>>>2000 will take away
>>>memory from store.exe if other processes need it. Fine
>>in theory, but
>>>it ain't working in
>>>practice here in this case. So, the question is, as it
>>always has
>>>been, "what can I do to
>>>limit the growth of store.exe?".
>>>
>>>
>>>======================
>>>
>>>
>>>
>>>
>>>On Tue, 24 Feb 2004 12:59:51 -0700, "Scott Harding - MS
>>MVP"
>>><scrockel@**NO_SPAM**hotmail.com> wrote:
>>>
>>>>I believe it is the same as Exchange 2000. I was just
>at
>>a Exchange 2003
>>>>conference today and they did not mention any new RAM
>>usage controls. So
>>>>what is using the CPU cycles? Typically that is going
>to
>>make the machine
>>>>more sluggish than some process using the RAM.
>>>
>>>.
>>>
>>.
>>
>.
>
- Next message: Andrew: "Event id: 9175 - advice"
- Previous message: Todd Hayden: "Information Store taking all available memory."
- In reply to: anonymous_at_discussions.microsoft.com: "Re: Store.exe consumes too much RAM"
- Next in thread: adrien: "Re: Store.exe consumes too much RAM"
- Reply: adrien: "Re: Store.exe consumes too much RAM"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
