Re: Non Paged Memory Error
- From: Andy David {MVP} <adavid@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 20 Jun 2007 18:54:54 -0400
On Wed, 20 Jun 2007 15:29:16 -0700, Mark R.
<MarkR@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
It is a non paged exhaustion. The server locks up and cannot recover, so
reboot is required to become functional again. The event log is a 2019
message.
What is the exact text of the error?
.
"Oliver Moazzezi" wrote:
What is the error exactly?
Do you mean error or do you mean you're encountering non paged pool memory
exhaustion?
Oliver
"Mark R." <MarkR@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F0455725-D7B5-40A0-BEAF-A1C30F6EC89F@xxxxxxxxxxxxxxxx
I am having an issue with the non paged memory error. I've found the KB
(912376)article to reduce token size and also ask for the hot fix from
support to help it more. I am running Exchange 2003 Standard SP2 with the
latest patches from Windows Update. Will this hot fix (912480) help in a
big
way? I have the /3GB switch set in the boot.ini file and I have eliminated
most applications on the server as causes. One thing that I found is that
under the license monitor is a lot of unlicensed users with an enormous
amount of client connections. I have the necessary amount of CAL's for my
user count, but these enormous amounts of connections have to be a
problem. I
really need to get my server to stop freezing up. I have made sure that my
Outlook 2003 clients are not in cached mode, but the majority of my
clients
are Outlook 2000. Any other suggestions to get rid of this issue?
- References:
- Re: Non Paged Memory Error
- From: Oliver Moazzezi
- Re: Non Paged Memory Error
- Prev by Date: Re: Non Paged Memory Error
- Next by Date: Re: Configure OWA to use SSL
- Previous by thread: Re: Non Paged Memory Error
- Next by thread: Re: Non Paged Memory Error
- Index(es):
Relevant Pages
|