Re: A large amount of memory ... UPDATE
- From: "Gregg Hill" <bogus@xxxxxxxxxxx>
- Date: Tue, 6 Feb 2007 16:52:35 -0800
Ever since I (successfully, this time) limited the SBSMONITORING RAM usage,
I have not had another error. I will look more closely at the results the
next time I limit MSDE or SQL use.
Gregg Hill
"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message
news:%23MxtC2iRHHA.3592@xxxxxxxxxxxxxxxxxxxxxxx
Looking at the batch file I used, I had originally set it to 100, but it
either did not take and I missed that fact, or it reverted back somehow.
It's more likely that I just missed its failure to apply the new setting.
Gregg Hill
"Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:%23XqVKhiRHHA.4384@xxxxxxxxxxxxxxxxxxxxxxx
I can't remember what I throttled my monitoring to, but it's sure not 852
: -)
Glad you solved it.
"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message
news:uTCkq$dRHHA.4632@xxxxxxxxxxxxxxxxxxxxxxx
Dave,
I had limited (or so I thought) the SBSMONITORING instance of
sqlservr.exe to 100MB of RAM when I first installed the server. Tonight
after I got the allocated memory alert message again, it showed
SBSMONITORING using a max of 852MB of RAM, so I ran the limiting again,
with this message at the end of the SQL commands, "Configuration option
'max server memory (MB)' changed from 2147483647 to 100."
I did it again and set it to 200, with this result message,
"Configuration option 'max server memory (MB)' changed from 100 to 200."
Apparently, I missed checking the results when I first did the limit, or
something caused it to revert.
Anyway, as long as the change holds, I think I found the culprit.
Thank you for your help!
Gregg Hill
"Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:e0jgNxVRHHA.2076@xxxxxxxxxxxxxxxxxxxxxxx
I can't argue with ignoring something when that alert is the only
symptom. However, I don't think inetinfo.exe has any business using all
that RAM. Any idea what it's doing? Inetinfo runs a lot of Exchange
stuff, so I'm wondering if this can be Exchange-related. Maybe AV
configured to scan something it shouldn't be? I'm not sure what could
cause this, but I've got store.exe at 600+ mb while inetinfo is at
around 60.
"PhilScott-SBSAdmin" <PhilScottSBSAdmin@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
news:C3B5AED9-D5B5-4602-88EB-FF5348EA1CA8@xxxxxxxxxxxxxxxx
I have the same issue. Mine is followed by another email alert saying
that
the INETINFO.EXE process is allocating more memory than usual....etc.
If I
check my Task Manager I can see that INETINFO.EXE is using more memory
than
STORE.EXE.
I have checked the configuration for the Allocated Memory Alert and it
is
configured properly. There doesn't seem to be a noticeable problem
with our
server so I have been semi ignoring the message until I saw this
thread.
Strange thing is that generally these emails come around the same time
everyday.
"Dave Nickason [SBS MVP]" wrote:
In Task Manager, are you seeing any processes that appear to be using
an
undue amount of RAM? (Besides store.exe - ignore that one).
Another option is to cut back on the memory allocated to some
processes -
the MSDE instance for ISA logging is an example. Search Susan
Bradley's
blog for "throttle ISA" and "allocated memory" and you'll get some
more info
about that. http://msmvps.com/blogs/bradley/default.aspx
Meanwhile, if the server is functioning properly, another option
would be to
ignore the alerts. I'm not crazy about that since you lose
functionality in
a legitimate alert condition. However, if the alert is the only
symptom,
I'm not sure how much I'd change in the absence of other symptoms.
Or add some RAM. (On that subject, I'm running Premium with ISA but
not
SQL. 20 users but probably 26 or so client PCs. With 4 GB RAM, the
server
actually doesn't use it all. Right now, it's been up and running
since the
week of Patch Tuesday and it's using 2.56 GB, with store.exe
responsible for
almost 700 MB of that. I usually run in the low 3 GB range but most
of the
users have left for the day).
"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message
news:%23a1I2c$QHHA.4276@xxxxxxxxxxxxxxxxxxxxxxx
Dave,
I had Googled yesterday and found that reference before I posted.
Yes, it
is set to the correct amount for their 2GB of RAM.
Gregg Hill
"Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx> wrote
in
message news:%23kfGnf9QHHA.1200@xxxxxxxxxxxxxxxxxxxxxxx
First things first - check this blog to make sure the alert is
configured
correctly. (Ignore the "adding ram" thing - this tells the
correct
configuration regardless).
Allocated Memory Errors After Adding RAM
http://blogs.technet.com/sbs/archive/2006/06/07/433707.aspx
"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message
news:O9nrZc2QHHA.1908@xxxxxxxxxxxxxxxxxxxxxxx
Hello!
On a recent installation of SBS 2003 R2 on a Dell PE840 with 2GB
RAM
(client already had the bare server...I would have ordered it
with 4GB),
I keep getting these emails regarding excessive memory use. I
have a
near-identical installation on another server, with the only
differences
being it is a Dell PE830 with 4GB of RAM, and it never pops
either
message.
*************
Alert on DC01 at 1/27/2007 2:22:37 PM
A large amount of memory is committed to applications and
processes.
Consistently high memory usage can cause performance problems.
To determine which processes and applications are using the most
memory,
use Task Manager. Monitor the activity of these resources over a
few
days. If they continue to use a high level of memory and are less
critical processes or services, try stopping and then restarting
them.
You can disable this alert or change its threshold by using the
Change
Alert Notifications task in the Server Management Monitoring and
Reporting taskpad.
*************
The above message is followed four seconds later by this message
in the
Application Log of Event Viewer.
Event Type: Warning
Event Source: MSExchangeSA
Event Category: General
Event ID: 5008
Date: 1/28/2007
Time: 2:22:41 PM
User: N/A
Computer: DC01
Description:
The message tracking log file E:\Program
Files\Exchsrvr\DC01.log\20070119.log was deleted.
For more information, click
http://www.microsoft.com/contentredirect.asp.
*************
Any ideas why this messages pops and how to stop it?
Thank you for your time!
Gregg Hill
.
- References:
- Re: A large amount of memory is committed to applications and proc
- From: Gregg Hill
- Re: A large amount of memory is committed to applications and proc
- From: Dave Nickason [SBS MVP]
- Re: A large amount of memory is committed to applications and proc
- From: Gregg Hill
- Re: A large amount of memory is committed to applications and proc
- Prev by Date: Re: Domain names
- Next by Date: Re: Backup now takes all night
- Previous by thread: Re: A large amount of memory is committed to applications and proc
- Next by thread: Terminal Services
- Index(es):
Relevant Pages
|
Loading
