Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Tue, 4 Apr 2006 09:50:03 -0700,    group: microsoft.public.exchange.tools        back       


Non-paged pool memory critical - per ExBPA   
I ran a BPA report yesterday after manually updating to the latest version of 
the tool to see what may be different.  It returned a critical issue for one 
of my Exchange cluster nodes that reads "Non-[aged pool memory is over the 
critical threshold of 110 MB.  System instability may occur.  Current value: 
115 MB".  I'm a bit confused on the help file that instructs you how to solve 
this problem.  

It says to monitor the Memory | Pool Nonpaged Bytes perfmon counter to 
ensure that it is not climbing over the above listed threshold for the sytem. 
 I'm having some problems using this counter because I don't know what scale 
to use.   I.E. my vertical scale is set to 100 on the graph and to 0.0000100 
on the data scale for the Memory | Pool Nonpaged Bytes counter object.  
However, that counter is constatly pegged out way over a hundred.

How are you suppose to measure the Memory | Pool Nonpaged Bytes perfmon 
counter?
date: Tue, 4 Apr 2006 09:50:03 -0700   author:   SilverICE

Re: Non-paged pool memory critical - per ExBPA   
Non-paged pool (NPP) memory is typically used by drivers and filters. If 
ExBPA is warning about out-of-date software, then make sure that you upgrade 
as recommended. If you have any special AV or backup software on the machine 
also ensure that you're using the latest version available as these 
components tend to consume a lot of NPP.

-- 
Paul Bowden
Program Manager
Exchange Server Best Practices Analyzer
http://www.microsoft.com/exchange/analyzers

This posting is provided "AS IS" with no warranties, and confers no rights.

"SilverICE"  wrote in message 
news:BD5AE0FF-F9EA-4170-A288-F25CA0E92701@microsoft.com...
>I ran a BPA report yesterday after manually updating to the latest version 
>of
> the tool to see what may be different.  It returned a critical issue for 
> one
> of my Exchange cluster nodes that reads "Non-[aged pool memory is over the
> critical threshold of 110 MB.  System instability may occur.  Current 
> value:
> 115 MB".  I'm a bit confused on the help file that instructs you how to 
> solve
> this problem.
>
> It says to monitor the Memory | Pool Nonpaged Bytes perfmon counter to
> ensure that it is not climbing over the above listed threshold for the 
> sytem.
> I'm having some problems using this counter because I don't know what 
> scale
> to use.   I.E. my vertical scale is set to 100 on the graph and to 
> 0.0000100
> on the data scale for the Memory | Pool Nonpaged Bytes counter object.
> However, that counter is constatly pegged out way over a hundred.
>
> How are you suppose to measure the Memory | Pool Nonpaged Bytes perfmon
> counter?
>
date: Tue, 4 Apr 2006 11:03:44 -0700   author:   Paul Bowden [MSFT]

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us