Re: Allocated Memory Alert

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Luke Digby (lwdigby_at_easy.com)
Date: 02/23/04 

Date: Mon, 23 Feb 2004 16:05:54 -0000

Hi,

Thanks for the advice, it doesn't seem to be releasing. How long would a
releasing phase take?

I have run the Windows Update but there are no updates. I have also checked
to see if there any outstanding exchange patches, none. Calling in
Microsoft for support is not an option as it costs hundreds of £££'s per
solution. We are a small business and simply cannot afford it.

Thanks again,
Luke

"Robert King [MSFT]" <a-rking@online.microsoft.com> wrote in message
news:fvXbSFi%23DHA.1472@cpmsftngxa06.phx.gbl...
> Increasing and releasing is normal. Increasing and not releasing is not
> normal. Run your windows updates. If that doesn't work, call in and get
a
> case ID so we can help you.
>
> Robert King
> Microsoft Product Support Specialist
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> --------------------
> |
> | My SBS2003 Premium is throwing up memory allocation alerts. The
offending
> | processes are "store.exe" (about 400mb) and "mad.exe" (250mb). Both are
> | increasing. Is this normal. Is there anything you can do about it???
> |
> | Thanks in advance for any advice.
> |
> | Regards,
> | Luke Digby
> |
> | Below is a sample of my sbs monitoring:
> | Critical Alerts
> | Issue Last Occurrence Total
Occurrences
> | Allocated Memory 2/23/2004 00:31 1
> | 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.
> |
> |
> |
>

Relevant Pages

  • Re: Anyone know why the Alpha market is so so quiet?
    ... We noticed cron jobs were not getting run and cron was dying on their ... The bug was kicked up to AT&T. ... The cron was malloc'ing memory and never releasing it so it used up all ...
    (comp.os.vms)
  • Re: Not enough storage space
    ... Closing or even destroying (releasing) the command objects does not seem to help. ... This will actually release the memory or, as I experienced it, will put a ceiling on how much memory is used. ... has to be solved using what I'm using (evc++4, sqlce2 and OLEDB) Every ...
    (microsoft.public.sqlserver.ce)
  • Re: Memory problems (possibly very easy question)
    ... It is a common delusion that if you free storage your program should get smaller; ... memory usage warnings. ... But releasing it does not reduce the footprint, it merely keeps it from growing as the ... fragmentation may mean that the footprint will continue to grow, ...
    (microsoft.public.vc.mfc)
  • RE: Allocated Memory Alert
    ... Increasing and releasing is normal. ... | My SBS2003 Premium is throwing up memory allocation alerts. ... | A large amount of memory is committed to applications and processes. ... | Notifications task in the Server Management Monitoring and Reporting ...
    (microsoft.public.windows.server.sbs)
  • Re: IBM JVM and OS heap
    ... > shrinking the heap and releasing memory to OS are two different things. ... > decommitted on a heap shrinkage. ...
    (comp.lang.java.machine)