Event ID 2020 Source Srv
| Event ID | 2020 |
| Source | Srv |
| Type | Error |
| Description | The server was unable to allocate from the system paged pool because the pool was empty. |
| English, please! | This information is only available to subscribers. An example of English, please! |
| Comments |
Adrian Grigorof
According to Microsoft: "This behavior can occur when the print jobs sent to the central print share are not properly redirected to the shared printers connected to the client computers. This can result in a Memory Leak in MsvC on the server, which eventually causes the server to crash". Read McAfee Solution ID: nai23653 and M286060 below for more details. Go to the McAfee Knowledge Search page and search for the above solution to read it. In certain conditions, this may be caused by Symantec's Norton AntiVirus Corporate Edition software (see M272568). Vlastimil Bandik There ares several reason why this issue can happen, but in combination with event id 333 I suggest the modification of boot.ini file (see below): use /USERVA=2800 and /BASEVIDEO This helped in my case. Joerg Schmidtke In our case, the problem was Network Stored PST files on the server. The link to "Network Stored PST files" was very helpful and article M297019 solved our problem. Mihai Andrei See M891004 and M940307 for two hotfixes applicable to Microsoft Windows Server 2003. See M815493 and M906952 for two hotfixes applicable to Microsoft Windows 2000 Advanced Server. See M912480 and M927338 for two hotfixes applicable to Microsoft Exchange Server 2003. See M943052 for a hotfix applicable to Microsoft BizTalk Server 2004. If you installed Symantec AntiVirus Corporate Edition 8 or Norton AntiVirus Corporate Edition 7.x on your Windows NT-based client, scheduled a scan and the scan does not run, then see the link to "Symantec Knowledge Base Document ID: 2000050108464148". See M912376, M923360, M933998, "Dell Support Document Number: TT1061426", "JSI Tip 3408", "JSI Tip 5047" and "JSI Tip 8352" for additional information about this event. Tate This issue is commonly misdiagnosed, however, 90% of the time it is actually quite possible to determine the resolution quickly without any serious effort at all. See the link to "Understanding Pool Consumption and Event ID: 2020 or 2019" for more information. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! Ionut Marin See M886670 for a hotfix applicable to Microsoft Windows Server 2003. See M897063 for a hotfix applicable to Microsoft BizTalk Server 2002. As per Microsoft: "This problem may occur if Cache Manager-owned files become abandoned on the Modified-No-Write list". See M832791 for a hotfix applicable to Microsoft Windows 2000. As per Microsoft: "Several factors may deplete the supply of paged pool memory". See M312362 for more detailed information. As per Microsoft: "This behavior can occur when you have files that have a large number of extended attributes(An example of a extended attribute is the list of items under the summary tab of a file properties box). The NTFS file system does not assign the extended attribute streams a paging I/O resource and does not mark them as modified-no-write". See M304093 to fix this problem. As per Microsoft: "This problem may occur if you have installed WQuinn's QuotaAdvisor 4.1, build 452 or earlier on your computer". See M830067 for more details. If this memory leak occurs after you install Microsoft Windows 2000 Server Service Pack 4 and you have Microsoft Operations Manager (MOM) installed, see M825237 and M835517 for a hotfix. If you are running Norton AntiVirus and SymEvent driver version 11.0:0.13 from Symantec on your Microsoft Windows 2000 Server-based computer, the see M842716 to fix this problem. If you are running Sophos Anti-Virus and VERITAS Backup Exec, then read Sophos Support Article ID: 3245 for information on this issue. If this event appears when a user attempts a connection to a Citrix Presentation Server, then read "Citrix Support Document ID: CTX108553" for details on this issue. If you do not know witch process or driver causes the leak and want to find out you can use the "pstat.exe" tool. See the link below to download it. You might also want to look at M268343. It shows you how to use "umdh.exe" to find memory leaks. See M304101, M830265, and the link to "EventID 2020 from source NCP Server" for additional information. PaulD Read Veritas Support Document ID: 259150 and Veritas Support Document ID: 277891 for information on this problem. Robert Collinson We found that a possible cause for this problem, which eventually ended up with one of our main Terminal Servers crashing was due to falsely detected problems with the registry size causing the system to think that it did not have enough resources to update the users roaming profiles. It appeared that somehow the PagedPoolSize registry setting had been set to 192 MB, the maximum that it could be according to Microsoft. Setting it back to zero allows the system to decide how much it needs by itself. Rob Pagé This error messaged appeared when a print job being spooled to the “C:” drive exceeded the capacity of the partition. Freeing up disk space on the drive, or moving the location of the print spooler will fix the problem. See M314105 for information on how to move the print spooler folder. Hayfe This problem also accoured on a Windows 2003 Server when I had Promise RAID Tools prior to version 4.0.0.18 installed. Anonymous This also can happen if your max page file size is set bigger then the amount of free space on the hard drive, and the server tries to expand the page file and then it will run out of disk space. Kmex Jorgensen This issue may occur if a non-Microsoft program that is installed on your computer uses an outdated kernel-mode filter driver. See M822219 for more details. Also Check M823747 for a hotfix that helped me to fix this problem. Bulakov Alexy According to a newsgroup post: “A memory leak in Win2k SP4 (and MOM) has been identified and a fix is being developed. In the meantime, the workaround is to remove SP4 from the MOM DCAM server (revert back to SP3)”. This memory leak results in numerous events 2020 and 2000, only reboot temporary solve this problem. Eric Scales In addition, see articles M161870, M196745 and M298511. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! Anonymous The problem was also caused by a Memory Leak in the Dell server management tools. Bob The device reported an error on a request to write data to media: Error Reported: Unknown Error. Our ntbackup.exe would crash at random intervals and display the errors. This error was caused when the system ran out of memory and swap memory while doing the backup. We rebooted box and everything was OK. |
| Links | M161870, M196745, M268343, M272568, M286060, M297019, M298511, M304093, M304101, M312362, M314105, M815493, M822219, M823747, M825237, M830067, M830265, M832791, M835517, M842716, M886670, M897063, M891004, M906952, M912376, M912480, M923360, M927338, M933998, M940307, M943052, Pstat.exe, McAfee Knowledge Search, Symantec Knowledge Base Document ID: 2000050108464148, EventID 2020 from source NCP Server, Sophos Support Article ID: 3245, Veritas Support Document ID: 259150, Veritas Support Document ID: 277891, JSI Tip 3408, JSI Tip 8352, JSI Tip 5047, Dell Support Document Number: TT1061426, Citrix Support Document ID: CTX108553, Understanding Pool Consumption and Event ID: 2020 or 2019, Network Stored PST files |
| Search | Google Web - Microsoft Support - Bing - EventID.Net Queue - More links... |
| Custom search | The custom search information is available to subscribers only. |
| Feedback | Send comments - Notify me when updated |
| Print version |