Not enough server storage is available to process this command

[George]

I keep getting the error not enough server storage is available to process
this command when i copy a file that is around 100 megs in size. i do not
get the error when i copy small files. I have found articles that say to
change the irp packet size reg key and one that said to change your
pagedpoolmemory to 0. Neither of these fixes have helped. If anyone knows
of a fix for this I would greatly appreciate the info. I have about 300 gigs
of free space on the servers HD that i am copying to and the other HD has a
couple gigs free.

[Todd J Heron]

Beyond the IRP reg setting (and restarting the server following this
change), I have a few comments.

For Windows 2000 and above see:
Kerberos authentication may not work if user is a member of many groups:
http://support.microsoft.com/default.aspx?scid=kb;en-us;280830

I've seen a field report where this error could occur if the DC does not
have all these registry entries below:
.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RPC\ClientProtocols]
"ncacn_np"="rpcrt4.dll"
"ncacn_ip_tcp"="rpcrt4.dll"
"ncadg_ip_udp"="rpcrt4.dll"
"ncacn_nb_tcp"="rpcrt4.dll"
"ncacn_http"="rpcrt4.dll"

As a historical note, for Windows NT 4.0 and below, re-applying the current
service pack solves this problem. But I have not enocuntered any situations
where re-applying the latest SP was applicable to this error in a Windows
2000+ environment. This error in NT was caused when the OS had an old
version of the srv.sys file (from the NT 4.0 CD) which starts getting used
again in an installation which has had SP4 or later installed. Anytime a
change is made to the network settings that requires the original NT CD, the
change recopies the srv.sys file, even though the Server service may not
have been effected in any way. Service Pack levels greater than SP3 in NT
are completely incompatible the with the SP3 or less srv.sys file resulting
in the server service being unable to start.

[George]

I looked at the article and i am sure that we don't have any users that are a
member of 70 or 80 groups. I can sure check out getting that fix though. i
did want to clarify that the error does not occur in the event viewer. its a
pop up window that has the error in it. I don't know if that helps. also,
it's s windows server 2003 file server. It does not have any errors in it's
event viewer when these issues happen and my xp workstations don't have any
either. i will check the event logs of the domain controllers though. any
other thoughts? i looked all over the internet and have found very little
helpful info so far.

Post by Todd J Heron
Beyond the IRP reg setting (and restarting the server following this
change), I have a few comments.
http://support.microsoft.com/default.aspx?scid=kb;en-us;280830
I've seen a field report where this error could occur if the DC does not
..
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RPC\ClientProtocols]
"ncacn_np"="rpcrt4.dll"
"ncacn_ip_tcp"="rpcrt4.dll"
"ncadg_ip_udp"="rpcrt4.dll"
"ncacn_nb_tcp"="rpcrt4.dll"
"ncacn_http"="rpcrt4.dll"
As a historical note, for Windows NT 4.0 and below, re-applying the current
service pack solves this problem. But I have not enocuntered any situations
where re-applying the latest SP was applicable to this error in a Windows
2000+ environment. This error in NT was caused when the OS had an old
version of the srv.sys file (from the NT 4.0 CD) which starts getting used
again in an installation which has had SP4 or later installed. Anytime a
change is made to the network settings that requires the original NT CD, the
change recopies the srv.sys file, even though the Server service may not
have been effected in any way. Service Pack levels greater than SP3 in NT
are completely incompatible the with the SP3 or less srv.sys file resulting
in the server service being unable to start.
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

[Mike Brierley]

I have the exact same problem. Any time I try to copy large files I get
<font color=red>"Not enough server storage is available to process this
command"</font> and nothing in the event viewer. I have also found the
articles about irp and pagedpoolsize, neither seem to match the problem.
This is on windows 2003 Enterprise version.

Mike

Post by George
I looked at the article and i am sure that we don't have any users that are a
member of 70 or 80 groups. I can sure check out getting that fix though. i
did want to clarify that the error does not occur in the event viewer. its a
pop up window that has the error in it. I don't know if that helps. also,
it's s windows server 2003 file server. It does not have any errors in it's
event viewer when these issues happen and my xp workstations don't have any
either. i will check the event logs of the domain controllers though. any
other thoughts? i looked all over the internet and have found very little
helpful info so far.

Post by Todd J Heron
Beyond the IRP reg setting (and restarting the server following this
change), I have a few comments.
http://support.microsoft.com/default.aspx?scid=kb;en-us;280830
I've seen a field report where this error could occur if the DC does not
..
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RPC\ClientProtocols]
"ncacn_np"="rpcrt4.dll"
"ncacn_ip_tcp"="rpcrt4.dll"
"ncadg_ip_udp"="rpcrt4.dll"
"ncacn_nb_tcp"="rpcrt4.dll"
"ncacn_http"="rpcrt4.dll"
As a historical note, for Windows NT 4.0 and below, re-applying the current
service pack solves this problem. But I have not enocuntered any situations
where re-applying the latest SP was applicable to this error in a Windows
2000+ environment. This error in NT was caused when the OS had an old
version of the srv.sys file (from the NT 4.0 CD) which starts getting used
again in an installation which has had SP4 or later installed. Anytime a
change is made to the network settings that requires the original NT CD, the
change recopies the srv.sys file, even though the Server service may not
have been effected in any way. Service Pack levels greater than SP3 in NT
are completely incompatible the with the SP3 or less srv.sys file resulting
in the server service being unable to start.
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

[George]

Mike,
Do you have many apps running on that server? I have symantec corp. ver 9,
backup exec agent, landesk, and a veritas storage replication agent. any of
those match up with what you have? My server is a file and print server
only. it is windows server 2003 appliance server edition. its exactly like
my other servers though. i am just wondering if we have anything in common
between the servers that could be causeing the error. i tried disabling all
the services that i don't need, and i was able to copy large files again.
then i went back through and tried re-enabling them, and the error came back.
i then tried to disable the services one at a time to narrow down the bad
one and i haven't been able to copy large files without the error. i will
see if i can experiment with it more during off hours to find out what serive
is causing my issue.

Post by Mike Brierley
I have the exact same problem. Any time I try to copy large files I get
<font color=red>"Not enough server storage is available to process this
command"</font> and nothing in the event viewer. I have also found the
articles about irp and pagedpoolsize, neither seem to match the problem.
This is on windows 2003 Enterprise version.
Mike

Post by George
I looked at the article and i am sure that we don't have any users that are a
member of 70 or 80 groups. I can sure check out getting that fix though. i
did want to clarify that the error does not occur in the event viewer. its a
pop up window that has the error in it. I don't know if that helps. also,
it's s windows server 2003 file server. It does not have any errors in it's
event viewer when these issues happen and my xp workstations don't have any
either. i will check the event logs of the domain controllers though. any
other thoughts? i looked all over the internet and have found very little
helpful info so far.

Post by Todd J Heron
Beyond the IRP reg setting (and restarting the server following this
change), I have a few comments.
http://support.microsoft.com/default.aspx?scid=kb;en-us;280830
I've seen a field report where this error could occur if the DC does not
..
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RPC\ClientProtocols]
"ncacn_np"="rpcrt4.dll"
"ncacn_ip_tcp"="rpcrt4.dll"
"ncadg_ip_udp"="rpcrt4.dll"
"ncacn_nb_tcp"="rpcrt4.dll"
"ncacn_http"="rpcrt4.dll"
As a historical note, for Windows NT 4.0 and below, re-applying the current
service pack solves this problem. But I have not enocuntered any situations
where re-applying the latest SP was applicable to this error in a Windows
2000+ environment. This error in NT was caused when the OS had an old
version of the srv.sys file (from the NT 4.0 CD) which starts getting used
again in an installation which has had SP4 or later installed. Anytime a
change is made to the network settings that requires the original NT CD, the
change recopies the srv.sys file, even though the Server service may not
have been effected in any way. Service Pack levels greater than SP3 in NT
are completely incompatible the with the SP3 or less srv.sys file resulting
in the server service being unable to start.
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

[Mike Brierley]

Hi George,
This is an SQL SAP instance server. It's got 4GB of memory (Using /PAE
in the boot.ini), and after everything is running it's got about 500MB
free ram. I can copy small files but copying 3GB+ will not occur.
If you discover the 'service' let me know, I'll have my group open a
ticket to bug the folks at MS.

Mike

Post by George
Mike,
Do you have many apps running on that server? I have symantec corp. ver 9,
backup exec agent, landesk, and a veritas storage replication agent. any of
those match up with what you have? My server is a file and print server
only. it is windows server 2003 appliance server edition. its exactly like
my other servers though. i am just wondering if we have anything in common
between the servers that could be causeing the error. i tried disabling all
the services that i don't need, and i was able to copy large files again.
then i went back through and tried re-enabling them, and the error came back.
i then tried to disable the services one at a time to narrow down the bad
one and i haven't been able to copy large files without the error. i will
see if i can experiment with it more during off hours to find out what serive
is causing my issue.

[Todd J Heron]

Where is your pagefile at? Is it sitting on a fast drive? How large is it?
Have you defrgamented it recently?

[Mike Brierley]

Post by Todd J Heron
Where is your pagefile at? Is it sitting on a fast drive? How large is it?
Have you defrgamented it recently?

Multiple Page files (4GB limit) We have 2X4GB page files on seperate drives.

M.

[Mike Brierley]

Anyone else have this issue?
M.

Post by Mike Brierley

Post by Todd J Heron
Where is your pagefile at? Is it sitting on a fast drive? How large
is it? Have you defrgamented it recently?

Multiple Page files (4GB limit) We have 2X4GB page files on seperate drives.
M.

[George]

I tried doing a selective startup and disabled all un-needed services. i
still get the error. i have a page file on the c drive. i am going to
change it from the system managed page file to a set one and restart it this
evening to see if that will help.

Post by Mike Brierley
Anyone else have this issue?
M.

Post by Mike Brierley

Post by Todd J Heron
Where is your pagefile at? Is it sitting on a fast drive? How large
is it? Have you defrgamented it recently?

Multiple Page files (4GB limit) We have 2X4GB page files on seperate drives.
M.

[Mike Brierley]

tomorrow I'll have time to reboot the server with all the SAP & SQL
services stopped. I have been 'told' that it 'might' be a memory issue
(as in not enough). We'll see.

M.

Post by George
I tried doing a selective startup and disabled all un-needed services. i
still get the error. i have a page file on the c drive. i am going to
change it from the system managed page file to a set one and restart it this
evening to see if that will help.

Post by Mike Brierley
Anyone else have this issue?
M.

Post by Mike Brierley

Post by Todd J Heron
Where is your pagefile at? Is it sitting on a fast drive? How large
is it? Have you defrgamented it recently?

Multiple Page files (4GB limit) We have 2X4GB page files on seperate drives.
M.

[Mike Brierley]

After reboots and having 3.8 GB of free RAM the problem persists :(


M.

Post by Mike Brierley
tomorrow I'll have time to reboot the server with all the SAP & SQL
services stopped. I have been 'told' that it 'might' be a memory issue
(as in not enough). We'll see.
M.

Post by George
I tried doing a selective startup and disabled all un-needed
services. i still get the error. i have a page file on the c drive.
i am going to change it from the system managed page file to a set one
and restart it this evening to see if that will help.

Post by Mike Brierley
Anyone else have this issue?
M.

Post by Mike Brierley

Post by Todd J Heron
Where is your pagefile at? Is it sitting on a fast drive? How
large is it? Have you defrgamented it recently?

Multiple Page files (4GB limit) We have 2X4GB page files on seperate drives.
M.

[Lance]

Did you try searching around the MS KnowledgeBase?

This error message may have nothing to do with RAM at all. For example:
http://support.microsoft.com/default.aspx?scid=kb;en-us;177078

Lance
*****

Post by Mike Brierley
After reboots and having 3.8 GB of free RAM the problem persists :(
M.

Post by Mike Brierley
tomorrow I'll have time to reboot the server with all the SAP & SQL
services stopped. I have been 'told' that it 'might' be a memory
issue (as in not enough). We'll see.
M.

Post by George
I tried doing a selective startup and disabled all un-needed
services. i still get the error. i have a page file on the c
drive. i am going to change it from the system managed page file to
a set one and restart it this evening to see if that will help. "Mike

Post by Mike Brierley
Anyone else have this issue?
M.

Post by Mike Brierley

Post by Todd J Heron
Where is your pagefile at? Is it sitting on a fast drive? How
large is it? Have you defrgamented it recently?

Multiple Page files (4GB limit) We have 2X4GB page files on seperate drives.
M.

[Lance]

Oops. I apologize. I didn't see earlier posts where this fix was already
tried.

Lance
*****

Post by Lance
Did you try searching around the MS KnowledgeBase?
http://support.microsoft.com/default.aspx?scid=kb;en-us;177078
Lance
*****

[Burt]

We're have the exact issue when copying a 100 GB file between two W2K
servers. None of the usual fixes mentioned in this thread have worked
for us. MS couldn't help either. Did anyone find a resolution?

Thanks,

Burt

Post by Lance
Oops. I apologize. I didn't see earlier posts where this fix was already
tried.
Lance
*****

Post by Lance
Did you try searching around the MS KnowledgeBase?
http://support.microsoft.com/default.aspx?scid=kb;en-us;177078
Lance
*****

[George]

Hello everyone,
I found a solution that worked for me. i have a windows 2003 server that i
was having this problem on when i would copy large files like 100megs or
later. i tried all that IRP stack sized stuff as well as disabling all
un-necesary services, uninstalling programs, removed file and print services
for unix and macintosh, set the page pooled memory value to 0, increased the
page file and none of those things worked. i installed SP1 for windows
server 2003 and my problem is fixed. i really hope that this helps some
people that have this problem.

Post by Burt
We're have the exact issue when copying a 100 GB file between two W2K
servers. None of the usual fixes mentioned in this thread have worked
for us. MS couldn't help either. Did anyone find a resolution?
Thanks,
Burt

Post by Lance
Oops. I apologize. I didn't see earlier posts where this fix was already
tried.
Lance
*****

Post by Lance
Did you try searching around the MS KnowledgeBase?
http://support.microsoft.com/default.aspx?scid=kb;en-us;177078
Lance
*****