Matthias Vandercleyen
asked on
Eventid 2020 Source Srv The server was unable to allocate from the system nonpaged pool because the pool was empty
Users are experiencing difficulties when connecting to shares on a windows server 2003 SP2 (DC + TS + file + print server). After a reboot the situation is all fine for a day or two.
Event log shows the 2020 Source Srv The server was unable to allocate from the system nonpaged pool because the pool was empty message.
Things I already did:
* Installed sp1 for the veritas backup exec 10d
* Modified the registry as stated in https://www.experts-exchange.com/questions/20617680/The-server-was-unable-to-allocate-from-the-system-paged-pool-because-the-pool-was-empty.html
* Executed poolmon for detecting memory leaks, but the output is too difficult. Can someone interpret the output on http://pastebin.com/ff605f72
Any help would be very appreciated
Thanks in advance
Event log shows the 2020 Source Srv The server was unable to allocate from the system nonpaged pool because the pool was empty message.
Things I already did:
* Installed sp1 for the veritas backup exec 10d
* Modified the registry as stated in https://www.experts-exchange.com/questions/20617680/The-server-was-unable-to-allocate-from-the-system-paged-pool-because-the-pool-was-empty.html
* Executed poolmon for detecting memory leaks, but the output is too difficult. Can someone interpret the output on http://pastebin.com/ff605f72
Any help would be very appreciated
Thanks in advance
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Installed all of the windows server 2003 updates on sunday (31-8-2008), rebooted the server.
The problem did not re-occur as for today, i will post more poolmon output on friday when i have access to the server.
I will then troubleshoot further like ashishsa stated.
To be continued...
The problem did not re-occur as for today, i will post more poolmon output on friday when i have access to the server.
I will then troubleshoot further like ashishsa stated.
To be continued...
ASKER
after the updates, the problem did not reoccur.
I had a look at the pool tags and MmCm is showing high memory allocation. This tag is the memory manager for contigious memory allocation.
Now we can do a couple of things to begin with on the server as must do troubleshooting.
1. Run hardware diagnostic on the server and see for any outdated firmware or hardware. Make sure that you update the firmware and Bios to the latest.
2. We can increase on the duration between failures by applying registry keys from KB 312362, but this will just delay the recurrence of the issue if there is a actual memory leak happening.
3. you will have to collect a few more poolmon log output at different intervals and post it so I will be able to review the tags.
4. What NICS and display card we are having on the machine.
5. Are we running / 3GB switch in the boot.ini
6. Also to fine tune the performance of the server we can execute the registry entries from the KB 324446.