Copy large backup file to external drive

SBS2003 R1 Premium SP1

I'm again having issues with copying large backup files (45 GB+) to external
USB drives. Originally I had this issue with XCOPY but switched to ROBOCOPY
and it worked better, for a while. I think my backup size has increased
again so now it can't do the copy anymore, here's the robocopy output:
------------------------
New File 46.9 g HI HD Data Backup
2007-05-21.bkp
94.5%
2007/05/23 10:55:09 ERROR 1450 (0x000005AA) Copying File I:\NTBackup\HI HD
Data
Backup 2007-05-21.bkp
Insufficient system resources exist to complete the requested service.
Waiting 30 seconds... Retrying...
New File 46.9 g HI HD Data Backup
2007-05-21.bkp
94.5%
2007/05/23 11:19:04 ERROR 1450 (0x000005AA) Copying File I:\NTBackup\HI HD
Data
Backup 2007-05-21.bkp
Insufficient system resources exist to complete the requested service.
Waiting 30 seconds... Retrying...
New File 46.9 g HI HD Data Backup
2007-05-21.bkp
94.4%
2007/05/23 11:43:15 ERROR 1450 (0x000005AA) Copying File I:\NTBackup\HI HD
Data
Backup 2007-05-21.bkp
Insufficient system resources exist to complete the requested service.
Waiting 30 seconds... Retrying...
--------------------------------------

So close, but yet so far ;-)

From what I've researched this has something to do with the size of the
paged memory poll, from a MS post:
-------------------
The CopyFileEx and CopyFile functions are used by
all of the standard file-copy utilities that are included with Windows.
Because these functions use buffered I/O, the maximum size of a file that
you can copy depends on the amount of paged-pool memory that is available
at the start of the copy procedure and whether the Physical Address
Extensions (PAE) kernel which allows access to memory above 4 gigabytes
[GB] is in use. With the standard kernel, 1 kilobyte (KB) of paged pool is
required for each megabyte (MB) of file size that is opened for buffered
I/O. Because there are two files involved in a copy procedure, 2 KB of
paged pool are required for each MB in the source file.
-----------------

PAE is off, the server has 3GB of memory with plenty free with my paged pool
at ~200000K which by the formula above should allow up to 100 GB to be
copied. I also thought this wasn't an issue with robocopy, but apparently
it is as I see this in my event log when the copy fails:
------------
Event Type: Error
Event Source: Srv
Event ID: 2020
The server was unable to allocate from the system paged pool because the
pool was empty
--------------

KB259837 has some info on this for Windows 2000 and said it was fixed in the
latest service pack but apparently not in Windows SBS 2003 SP1. I haven't
put in SP2 yet (due to all the issues reported with SBS) but if someone can
confirm the issue is fixed then I can look at it.

I'm looking at KB304101 right now and it looks promising but I really don't
like messing with the pool sizes - anyone done this? Any other ideas?

Thanks.
--
Allan Williams

What is the file format of the USB drive?
FAT, FAT32, or NTFS?

--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues

"Al Williams" <donotreplydirect@usenewsgroup.com> wrote in message
news:uGrJMVXnHHA.4428@TK2MSFTNGP06.phx.gbl...
> SBS2003 R1 Premium SP1
>
> I'm again having issues with copying large backup files (45 GB+) to
> external USB drives. Originally I had this issue with XCOPY but switched
> to ROBOCOPY and it worked better, for a while. I think my backup size has
> increased again so now it can't do the copy anymore, here's the robocopy
> output:
> ------------------------
> New File 46.9 g HI HD Data Backup
> 2007-05-21.bkp
> 94.5%
> 2007/05/23 10:55:09 ERROR 1450 (0x000005AA) Copying File I:\NTBackup\HI HD
> Data
> Backup 2007-05-21.bkp
> Insufficient system resources exist to complete the requested service.
> Waiting 30 seconds... Retrying...
> New File 46.9 g HI HD Data Backup
> 2007-05-21.bkp
> 94.5%
> 2007/05/23 11:19:04 ERROR 1450 (0x000005AA) Copying File I:\NTBackup\HI HD
> Data
> Backup 2007-05-21.bkp
> Insufficient system resources exist to complete the requested service.
> Waiting 30 seconds... Retrying...
> New File 46.9 g HI HD Data Backup
> 2007-05-21.bkp
> 94.4%
> 2007/05/23 11:43:15 ERROR 1450 (0x000005AA) Copying File I:\NTBackup\HI HD
> Data
> Backup 2007-05-21.bkp
> Insufficient system resources exist to complete the requested service.
> Waiting 30 seconds... Retrying...
> --------------------------------------
>
> So close, but yet so far ;-)
>
> From what I've researched this has something to do with the size of the
> paged memory poll, from a MS post:
> -------------------
> The CopyFileEx and CopyFile functions are used by
> all of the standard file-copy utilities that are included with Windows.
> Because these functions use buffered I/O, the maximum size of a file that
> you can copy depends on the amount of paged-pool memory that is available
> at the start of the copy procedure and whether the Physical Address
> Extensions (PAE) kernel which allows access to memory above 4 gigabytes
> [GB] is in use. With the standard kernel, 1 kilobyte (KB) of paged pool is
> required for each megabyte (MB) of file size that is opened for buffered
> I/O. Because there are two files involved in a copy procedure, 2 KB of
> paged pool are required for each MB in the source file.
> -----------------
>
> PAE is off, the server has 3GB of memory with plenty free with my paged
> pool at ~200000K which by the formula above should allow up to 100 GB to
> be copied. I also thought this wasn't an issue with robocopy, but
> apparently it is as I see this in my event log when the copy fails:
> ------------
> Event Type: Error
> Event Source: Srv
> Event ID: 2020
> The server was unable to allocate from the system paged pool because the
> pool was empty
> --------------
>
> KB259837 has some info on this for Windows 2000 and said it was fixed in
> the latest service pack but apparently not in Windows SBS 2003 SP1. I
> haven't put in SP2 yet (due to all the issues reported with SBS) but if
> someone can confirm the issue is fixed then I can look at it.
>
> I'm looking at KB304101 right now and it looks promising but I really
> don't like messing with the pool sizes - anyone done this? Any other
> ideas?
>
> Thanks.
> --
> Allan Williams
>
>
>
>

NTFS. It's not the USB drive - the issue happens even if I copy to local
drives with large 45-50 GB files.

Looking into it further it seems that PAE extensions are enabled by default
on 2003 SP1 to support Hardware enforced DEP. As MS says "When the PAE
kernel is used, the overhead is doubled and 4 KB of paged pool is required
for each MB in the source file." which means that my maximum file would be
~50 GB which makes sense with what I'm seeing.

--
Allan Williams



"Cris Hanna [SBS-MVP]" <crisnospamhanna@computingnospampossibilities.net>
wrote in message news:uryN55XnHHA.1240@TK2MSFTNGP04.phx.gbl...
> What is the file format of the USB drive?
> FAT, FAT32, or NTFS?
>
> --
> Cris Hanna [SBS-MVP]
> -------------------------------------------------
> Microsoft MVPs
> Independent Experts (MVPs do not work for MS)
> Real World Answers
> ---------------------------------------------------------
> Please do not contact me directly regarding issues
>
> "Al Williams" <donotreplydirect@usenewsgroup.com> wrote in message
> news:uGrJMVXnHHA.4428@TK2MSFTNGP06.phx.gbl...
>> SBS2003 R1 Premium SP1
>>
>> I'm again having issues with copying large backup files (45 GB+) to
>> external USB drives. Originally I had this issue with XCOPY but switched
>> to ROBOCOPY and it worked better, for a while. I think my backup size
>> has increased again so now it can't do the copy anymore, here's the
>> robocopy output:
>> ------------------------
>> New File 46.9 g HI HD Data Backup
>> 2007-05-21.bkp
>> 94.5%
>> 2007/05/23 10:55:09 ERROR 1450 (0x000005AA) Copying File I:\NTBackup\HI
>> HD Data
>> Backup 2007-05-21.bkp
>> Insufficient system resources exist to complete the requested service.
>> Waiting 30 seconds... Retrying...
>> New File 46.9 g HI HD Data Backup
>> 2007-05-21.bkp
>> 94.5%
>> 2007/05/23 11:19:04 ERROR 1450 (0x000005AA) Copying File I:\NTBackup\HI
>> HD Data
>> Backup 2007-05-21.bkp
>> Insufficient system resources exist to complete the requested service.
>> Waiting 30 seconds... Retrying...
>> New File 46.9 g HI HD Data Backup
>> 2007-05-21.bkp
>> 94.4%
>> 2007/05/23 11:43:15 ERROR 1450 (0x000005AA) Copying File I:\NTBackup\HI
>> HD Data
>> Backup 2007-05-21.bkp
>> Insufficient system resources exist to complete the requested service.
>> Waiting 30 seconds... Retrying...
>> --------------------------------------
>>
>> So close, but yet so far ;-)
>>
>> From what I've researched this has something to do with the size of the
>> paged memory poll, from a MS post:
>> -------------------
>> The CopyFileEx and CopyFile functions are used by
>> all of the standard file-copy utilities that are included with Windows.
>> Because these functions use buffered I/O, the maximum size of a file that
>> you can copy depends on the amount of paged-pool memory that is available
>> at the start of the copy procedure and whether the Physical Address
>> Extensions (PAE) kernel which allows access to memory above 4 gigabytes
>> [GB] is in use. With the standard kernel, 1 kilobyte (KB) of paged pool
>> is
>> required for each megabyte (MB) of file size that is opened for buffered
>> I/O. Because there are two files involved in a copy procedure, 2 KB of
>> paged pool are required for each MB in the source file.
>> -----------------
>>
>> PAE is off, the server has 3GB of memory with plenty free with my paged
>> pool at ~200000K which by the formula above should allow up to 100 GB to
>> be copied. I also thought this wasn't an issue with robocopy, but
>> apparently it is as I see this in my event log when the copy fails:
>> ------------
>> Event Type: Error
>> Event Source: Srv
>> Event ID: 2020
>> The server was unable to allocate from the system paged pool because the
>> pool was empty
>> --------------
>>
>> KB259837 has some info on this for Windows 2000 and said it was fixed in
>> the latest service pack but apparently not in Windows SBS 2003 SP1. I
>> haven't put in SP2 yet (due to all the issues reported with SBS) but if
>> someone can confirm the issue is fixed then I can look at it.
>>
>> I'm looking at KB304101 right now and it looks promising but I really
>> don't like messing with the pool sizes - anyone done this? Any other
>> ideas?
>>
>> Thanks.
>> --
>> Allan Williams
>>
>>
>>
>>
>
>

Well a server reboot seemed to fix it up, my kernel paged and non-paged
memory shown in the task manager went right down and the robocopy worked.
It seems we can't get away from this "reboot the server every few weeks"
issue with the server grabbing more free memory the longer it is up...

--
Allan Williams



"Cris Hanna [SBS-MVP]" <crisnospamhanna@computingnospampossibilities.net>
wrote in message news:uryN55XnHHA.1240@TK2MSFTNGP04.phx.gbl...
> What is the file format of the USB drive?
> FAT, FAT32, or NTFS?
>
> --
> Cris Hanna [SBS-MVP]
> -------------------------------------------------
> Microsoft MVPs
> Independent Experts (MVPs do not work for MS)
> Real World Answers
> ---------------------------------------------------------
> Please do not contact me directly regarding issues
>
> "Al Williams" <donotreplydirect@usenewsgroup.com> wrote in message
> news:uGrJMVXnHHA.4428@TK2MSFTNGP06.phx.gbl...
>> SBS2003 R1 Premium SP1
>>
>> I'm again having issues with copying large backup files (45 GB+) to
>> external USB drives. Originally I had this issue with XCOPY but switched
>> to ROBOCOPY and it worked better, for a while. I think my backup size
>> has increased again so now it can't do the copy anymore, here's the
>> robocopy output:
>> ------------------------
>> New File 46.9 g HI HD Data Backup
>> 2007-05-21.bkp
>> 94.5%
>> 2007/05/23 10:55:09 ERROR 1450 (0x000005AA) Copying File I:\NTBackup\HI
>> HD Data
>> Backup 2007-05-21.bkp
>> Insufficient system resources exist to complete the requested service.
>> Waiting 30 seconds... Retrying...
>> New File 46.9 g HI HD Data Backup
>> 2007-05-21.bkp
>> 94.5%
>> 2007/05/23 11:19:04 ERROR 1450 (0x000005AA) Copying File I:\NTBackup\HI
>> HD Data
>> Backup 2007-05-21.bkp
>> Insufficient system resources exist to complete the requested service.
>> Waiting 30 seconds... Retrying...
>> New File 46.9 g HI HD Data Backup
>> 2007-05-21.bkp
>> 94.4%
>> 2007/05/23 11:43:15 ERROR 1450 (0x000005AA) Copying File I:\NTBackup\HI
>> HD Data
>> Backup 2007-05-21.bkp
>> Insufficient system resources exist to complete the requested service.
>> Waiting 30 seconds... Retrying...
>> --------------------------------------
>>
>> So close, but yet so far ;-)
>>
>> From what I've researched this has something to do with the size of the
>> paged memory poll, from a MS post:
>> -------------------
>> The CopyFileEx and CopyFile functions are used by
>> all of the standard file-copy utilities that are included with Windows.
>> Because these functions use buffered I/O, the maximum size of a file that
>> you can copy depends on the amount of paged-pool memory that is available
>> at the start of the copy procedure and whether the Physical Address
>> Extensions (PAE) kernel which allows access to memory above 4 gigabytes
>> [GB] is in use. With the standard kernel, 1 kilobyte (KB) of paged pool
>> is
>> required for each megabyte (MB) of file size that is opened for buffered
>> I/O. Because there are two files involved in a copy procedure, 2 KB of
>> paged pool are required for each MB in the source file.
>> -----------------
>>
>> PAE is off, the server has 3GB of memory with plenty free with my paged
>> pool at ~200000K which by the formula above should allow up to 100 GB to
>> be copied. I also thought this wasn't an issue with robocopy, but
>> apparently it is as I see this in my event log when the copy fails:
>> ------------
>> Event Type: Error
>> Event Source: Srv
>> Event ID: 2020
>> The server was unable to allocate from the system paged pool because the
>> pool was empty
>> --------------
>>
>> KB259837 has some info on this for Windows 2000 and said it was fixed in
>> the latest service pack but apparently not in Windows SBS 2003 SP1. I
>> haven't put in SP2 yet (due to all the issues reported with SBS) but if
>> someone can confirm the issue is fixed then I can look at it.
>>
>> I'm looking at KB304101 right now and it looks promising but I really
>> don't like messing with the pool sizes - anyone done this? Any other
>> ideas?
>>
>> Thanks.
>> --
>> Allan Williams
>>
>>
>>
>>
>
>

what are you running on the server besides SBS?

--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues

"Al Williams" <donotreplydirect@usenewsgroup.com> wrote in message
news:u2aarPhnHHA.1240@TK2MSFTNGP04.phx.gbl...
> Well a server reboot seemed to fix it up, my kernel paged and non-paged
> memory shown in the task manager went right down and the robocopy worked.
> It seems we can't get away from this "reboot the server every few weeks"
> issue with the server grabbing more free memory the longer it is up...
>
> --
> Allan Williams
>
>
>
> "Cris Hanna [SBS-MVP]" <crisnospamhanna@computingnospampossibilities.net>
> wrote in message news:uryN55XnHHA.1240@TK2MSFTNGP04.phx.gbl...
>> What is the file format of the USB drive?
>> FAT, FAT32, or NTFS?
>>
>> --
>> Cris Hanna [SBS-MVP]
>> -------------------------------------------------
>> Microsoft MVPs
>> Independent Experts (MVPs do not work for MS)
>> Real World Answers
>> ---------------------------------------------------------
>> Please do not contact me directly regarding issues
>>
>> "Al Williams" <donotreplydirect@usenewsgroup.com> wrote in message
>> news:uGrJMVXnHHA.4428@TK2MSFTNGP06.phx.gbl...
>>> SBS2003 R1 Premium SP1
>>>
>>> I'm again having issues with copying large backup files (45 GB+) to
>>> external USB drives. Originally I had this issue with XCOPY but
>>> switched to ROBOCOPY and it worked better, for a while. I think my
>>> backup size has increased again so now it can't do the copy anymore,
>>> here's the robocopy output:
>>> ------------------------
>>> New File 46.9 g HI HD Data Backup
>>> 2007-05-21.bkp
>>> 94.5%
>>> 2007/05/23 10:55:09 ERROR 1450 (0x000005AA) Copying File I:\NTBackup\HI
>>> HD Data
>>> Backup 2007-05-21.bkp
>>> Insufficient system resources exist to complete the requested service.
>>> Waiting 30 seconds... Retrying...
>>> New File 46.9 g HI HD Data Backup
>>> 2007-05-21.bkp
>>> 94.5%
>>> 2007/05/23 11:19:04 ERROR 1450 (0x000005AA) Copying File I:\NTBackup\HI
>>> HD Data
>>> Backup 2007-05-21.bkp
>>> Insufficient system resources exist to complete the requested service.
>>> Waiting 30 seconds... Retrying...
>>> New File 46.9 g HI HD Data Backup
>>> 2007-05-21.bkp
>>> 94.4%
>>> 2007/05/23 11:43:15 ERROR 1450 (0x000005AA) Copying File I:\NTBackup\HI
>>> HD Data
>>> Backup 2007-05-21.bkp
>>> Insufficient system resources exist to complete the requested service.
>>> Waiting 30 seconds... Retrying...
>>> --------------------------------------
>>>
>>> So close, but yet so far ;-)
>>>
>>> From what I've researched this has something to do with the size of the
>>> paged memory poll, from a MS post:
>>> -------------------
>>> The CopyFileEx and CopyFile functions are used by
>>> all of the standard file-copy utilities that are included with Windows.
>>> Because these functions use buffered I/O, the maximum size of a file
>>> that
>>> you can copy depends on the amount of paged-pool memory that is
>>> available
>>> at the start of the copy procedure and whether the Physical Address
>>> Extensions (PAE) kernel which allows access to memory above 4 gigabytes
>>> [GB] is in use. With the standard kernel, 1 kilobyte (KB) of paged pool
>>> is
>>> required for each megabyte (MB) of file size that is opened for buffered
>>> I/O. Because there are two files involved in a copy procedure, 2 KB of
>>> paged pool are required for each MB in the source file.
>>> -----------------
>>>
>>> PAE is off, the server has 3GB of memory with plenty free with my paged
>>> pool at ~200000K which by the formula above should allow up to 100 GB to
>>> be copied. I also thought this wasn't an issue with robocopy, but
>>> apparently it is as I see this in my event log when the copy fails:
>>> ------------
>>> Event Type: Error
>>> Event Source: Srv
>>> Event ID: 2020
>>> The server was unable to allocate from the system paged pool because the
>>> pool was empty
>>> --------------
>>>
>>> KB259837 has some info on this for Windows 2000 and said it was fixed in
>>> the latest service pack but apparently not in Windows SBS 2003 SP1. I
>>> haven't put in SP2 yet (due to all the issues reported with SBS) but if
>>> someone can confirm the issue is fixed then I can look at it.
>>>
>>> I'm looking at KB304101 right now and it looks promising but I really
>>> don't like messing with the pool sizes - anyone done this? Any other
>>> ideas?
>>>
>>> Thanks.
>>> --
>>> Allan Williams
>>>
>>>
>>>
>>>
>>
>>
>
>

Only 2 - CA's Etrust AV7.1 and the Wildfire IM server - both have been
around a while. Their general and kernel memory use looks pretty small, but
I'll check them as I monitor the paged and non-paged pools for the next few
weeks.

The top memory users are the usual suspects - store, sqlserv x 4 (memory
limited by me), wspserv, and inetinfo. The biggest paged/nonpaged memory
users are store, wspserv, and inetinfo.

Thanks for your help.

--
Allan Williams



"Cris Hanna [SBS-MVP]" <crisnospamhanna@computingnospampossibilities.net>
wrote in message news:edpjOEknHHA.1904@TK2MSFTNGP02.phx.gbl...
> what are you running on the server besides SBS?
>
> --
> Cris Hanna [SBS-MVP]
> -------------------------------------------------
> Microsoft MVPs
> Independent Experts (MVPs do not work for MS)
> Real World Answers
> ---------------------------------------------------------
> Please do not contact me directly regarding issues
>
> "Al Williams" <donotreplydirect@usenewsgroup.com> wrote in message
> news:u2aarPhnHHA.1240@TK2MSFTNGP04.phx.gbl...
>> Well a server reboot seemed to fix it up, my kernel paged and non-paged
>> memory shown in the task manager went right down and the robocopy worked.
>> It seems we can't get away from this "reboot the server every few weeks"
>> issue with the server grabbing more free memory the longer it is up...
>>
>> --
>> Allan Williams
>>
>>
>>
>> "Cris Hanna [SBS-MVP]" <crisnospamhanna@computingnospampossibilities.net>
>> wrote in message news:uryN55XnHHA.1240@TK2MSFTNGP04.phx.gbl...
>>> What is the file format of the USB drive?
>>> FAT, FAT32, or NTFS?
>>>
>>> --
>>> Cris Hanna [SBS-MVP]
>>> -------------------------------------------------
>>> Microsoft MVPs
>>> Independent Experts (MVPs do not work for MS)
>>> Real World Answers
>>> ---------------------------------------------------------
>>> Please do not contact me directly regarding issues
>>>
>>> "Al Williams" <donotreplydirect@usenewsgroup.com> wrote in message
>>> news:uGrJMVXnHHA.4428@TK2MSFTNGP06.phx.gbl...
>>>> SBS2003 R1 Premium SP1
>>>>
>>>> I'm again having issues with copying large backup files (45 GB+) to
>>>> external USB drives. Originally I had this issue with XCOPY but
>>>> switched to ROBOCOPY and it worked better, for a while. I think my
>>>> backup size has increased again so now it can't do the copy anymore,
>>>> here's the robocopy output:
>>>> ------------------------
>>>> New File 46.9 g HI HD Data Backup
>>>> 2007-05-21.bkp
>>>> 94.5%
>>>> 2007/05/23 10:55:09 ERROR 1450 (0x000005AA) Copying File I:\NTBackup\HI
>>>> HD Data
>>>> Backup 2007-05-21.bkp
>>>> Insufficient system resources exist to complete the requested service.
>>>> Waiting 30 seconds... Retrying...
>>>> New File 46.9 g HI HD Data Backup
>>>> 2007-05-21.bkp
>>>> 94.5%
>>>> 2007/05/23 11:19:04 ERROR 1450 (0x000005AA) Copying File I:\NTBackup\HI
>>>> HD Data
>>>> Backup 2007-05-21.bkp
>>>> Insufficient system resources exist to complete the requested service.
>>>> Waiting 30 seconds... Retrying...
>>>> New File 46.9 g HI HD Data Backup
>>>> 2007-05-21.bkp
>>>> 94.4%
>>>> 2007/05/23 11:43:15 ERROR 1450 (0x000005AA) Copying File I:\NTBackup\HI
>>>> HD Data
>>>> Backup 2007-05-21.bkp
>>>> Insufficient system resources exist to complete the requested service.
>>>> Waiting 30 seconds... Retrying...
>>>> --------------------------------------
>>>>
>>>> So close, but yet so far ;-)
>>>>
>>>> From what I've researched this has something to do with the size of the
>>>> paged memory poll, from a MS post:
>>>> -------------------
>>>> The CopyFileEx and CopyFile functions are used by
>>>> all of the standard file-copy utilities that are included with Windows.
>>>> Because these functions use buffered I/O, the maximum size of a file
>>>> that
>>>> you can copy depends on the amount of paged-pool memory that is
>>>> available
>>>> at the start of the copy procedure and whether the Physical Address
>>>> Extensions (PAE) kernel which allows access to memory above 4 gigabytes
>>>> [GB] is in use. With the standard kernel, 1 kilobyte (KB) of paged pool
>>>> is
>>>> required for each megabyte (MB) of file size that is opened for
>>>> buffered
>>>> I/O. Because there are two files involved in a copy procedure, 2 KB of
>>>> paged pool are required for each MB in the source file.
>>>> -----------------
>>>>
>>>> PAE is off, the server has 3GB of memory with plenty free with my paged
>>>> pool at ~200000K which by the formula above should allow up to 100 GB
>>>> to be copied. I also thought this wasn't an issue with robocopy, but
>>>> apparently it is as I see this in my event log when the copy fails:
>>>> ------------
>>>> Event Type: Error
>>>> Event Source: Srv
>>>> Event ID: 2020
>>>> The server was unable to allocate from the system paged pool because
>>>> the pool was empty
>>>> --------------
>>>>
>>>> KB259837 has some info on this for Windows 2000 and said it was fixed
>>>> in the latest service pack but apparently not in Windows SBS 2003 SP1.
>>>> I haven't put in SP2 yet (due to all the issues reported with SBS) but
>>>> if someone can confirm the issue is fixed then I can look at it.
>>>>
>>>> I'm looking at KB304101 right now and it looks promising but I really
>>>> don't like messing with the pool sizes - anyone done this? Any other
>>>> ideas?
>>>>
>>>> Thanks.
>>>> --
>>>> Allan Williams
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>