We have a file / print that hosts files and printers for about 100 users. The server origonally was hosted on a Windows 2000 Dell server. Running for a few years we started to get the following error in the event log and the server had to be rebooted.
Source: SRV Event: 2020
The server was unable to allocate from the system paged pool because the pool was empty.
This was noticeable when trying to access files on the server, an error to the end user states that no enough memory when browsing shares hosted on this server.
Since then we have migrated this server to a newer Dell server running Windows Server 2003. Intel Xeon 2.8Ghz with 2GB of RAM. 250GB disk space in a hardware RAID5 array. When migrating to the new server we copied files over and reshared along with using the Windows Printer Migration tool to migrate print queues. The same error showed up after about 2 months of operation and seems to happen about once every 2 to 3 weeks and a reboot is required.
On the origonal server monitoring the Pool Paged Bytes performance counter during these problems would show the spoolsv to grow extremely large, after the reboot or restarting the print spooler this would come down and the server would be available again for file sharing / printing.
I think it is a printer driver problem or a memory leak relating to the spooler service. I have tried newer drivers, making sure they are all for Windows 2003, no kernel mode drivers, etc. This has not stopped the problem. I have also read some MS KB articles on AV software causing this, but we have had the same Symantec AV software for a few years with no problems, and it is on other servers as well.
Any help would be appreciated as to what to look for or more information to collect to narrow down this problem.