Not enough server storage is available to process this command

  • Thread starter Thread starter Gene
  • Start date Start date
G

Gene

I have Windows XP Pro SP2. However, this is a Toshiba laptop that came with
an XP Home disk image, which included Norton Antivirus (I think it was
2003). I recently rebuilt this computer by installing the Recovery CD, then
uninstalling all Norton software (NAV, Live Update, and a registration
wizard, if I remember), then XP Pro Upgrade (retail), the SP 2, then all
Microsoft updates.

I have a home network with a router and another Toshiba laptop. The other
laptop can successfully "Map a Network drive..." to the rebuilt laptop, but
the recently rebuilt laptop cannot map a network drive to the other.
Instead, it gets the "Not enough server storage is available to process this
command" message, discussed in Microsoft Knowledge Base article
http://support.microsoft.com/default.aspx?scid=kb;en-us;177078. From doing a
Google for "Not enough server storage is available to process this command"
I see this is a common problem.

I tried the suggested fix, namely to first add the default size for
IRPStackSize, then to increase it by 3 until I reached the max setting of
50. It is not working; I am not able to map network drives.

I then downloaded Norton's RNAV utility to "remove all Norton products". It
either did not find anything or else it managed to do it pretty quickly
without needing to reboot. In any case, after I rebooted I first tried
IRPStackSize at the default+3, and then at the max of 50. It still is not
working.

I have owned both of these laptops for 4-5 years and have rebuilt both of
them many, many times. This is the first time I have been stopped by this.
Does anyone have a suggestion?

Thanks,
Gene
 
I have Windows XP Pro SP2. However, this is a Toshiba laptop that came with
an XP Home disk image, which included Norton Antivirus (I think it was
2003). I recently rebuilt this computer by installing the Recovery CD, then
uninstalling all Norton software (NAV, Live Update, and a registration
wizard, if I remember), then XP Pro Upgrade (retail), the SP 2, then all
Microsoft updates.

I have a home network with a router and another Toshiba laptop. The other
laptop can successfully "Map a Network drive..." to the rebuilt laptop, but
the recently rebuilt laptop cannot map a network drive to the other.
Instead, it gets the "Not enough server storage is available to process this
command" message, discussed in Microsoft Knowledge Base article
http://support.microsoft.com/default.aspx?scid=kb;en-us;177078. From doing a
Google for "Not enough server storage is available to process this command"
I see this is a common problem.

I tried the suggested fix, namely to first add the default size for
IRPStackSize, then to increase it by 3 until I reached the max setting of
50. It is not working; I am not able to map network drives.

I then downloaded Norton's RNAV utility to "remove all Norton products". It
either did not find anything or else it managed to do it pretty quickly
without needing to reboot. In any case, after I rebooted I first tried
IRPStackSize at the default+3, and then at the max of 50. It still is not
working.

I have owned both of these laptops for 4-5 years and have rebuilt both of
them many, many times. This is the first time I have been stopped by this.
Does anyone have a suggestion?

Thanks,
Gene
Click to expand...

Which computer did you apply the change on, Gene?
<http://nitecruzr.blogspot.com/2005/06/server-functionality-affected-by.html>
http://nitecruzr.blogspot.com/2005/06/server-functionality-affected-by.html
 
Chuck said:
Which computer did you apply the change on, Gene?
<http://nitecruzr.blogspot.com/2005/06/server-functionality-affected-by.html>
http://nitecruzr.blogspot.com/2005/06/server-functionality-affected-by.html
Click to expand...

Hi Chuck,

I made the changes on the computer from which I tried to connect to the
other, that is, on the computer that gave me the error message. The other
computer can connect to the "problem" computer, so I never thought of making
the change to it. But--it makes sense, because, when I brought the "problem"
computer to work I was able to map network drives to the office computers.
[Sound of hand slapping forehead!] I never made the connection; the problem
must be the other computer.

Thanks for the tip. I will try it when I get home tonight.

Regards,
Gene
 
Earlier, I described a problem trying to map network drives between two
computers on a home network. I had applied Microsoft's fix described in
KB177078.
In response, "Chuck" wrote
Click to expand...

And I responded:
I made the changes on the computer from which I tried to connect to the
other, that is, on the computer that gave me the error message. The other
computer can connect to the "problem" computer, so I never thought of
making the change to it. But--it makes sense, because, when I brought the
"problem" computer to work I was able to map network drives to the office
computers. [Sound of hand slapping forehead!] I never made the connection;
the problem must be the other computer.

Thanks for the tip. I will try it when I get home tonight.
Click to expand...


I just created the IRPStackSize parameter in the Registry on the other
computer--the one TO which I am trying to connect--and it works! I am amazed
I did not think to try it on that other computer. Thanks a lot, Chuck.

BTW, is there any harm in leaving the IRPStackSize at 50? Or should I work
my way down by 3s until it does not work, then raise it up so it will work?
In other words, should I use the minimum necessary to map a network drive?

Thanks,
Gene

P.S. I just added your Blog (http://nitecruzr.blogspot.com/) to my "Try Hard
to Check Daily" List. I can learn a lot from it. Thanks.
 
Earlier, I described a problem trying to map network drives between two
computers on a home network. I had applied Microsoft's fix described in
KB177078.
In response, "Chuck" wrote
Click to expand...

And I responded:
I made the changes on the computer from which I tried to connect to the
other, that is, on the computer that gave me the error message. The other
computer can connect to the "problem" computer, so I never thought of
making the change to it. But--it makes sense, because, when I brought the
"problem" computer to work I was able to map network drives to the office
computers. [Sound of hand slapping forehead!] I never made the connection;
the problem must be the other computer.

Thanks for the tip. I will try it when I get home tonight.
Click to expand...


I just created the IRPStackSize parameter in the Registry on the other
computer--the one TO which I am trying to connect--and it works! I am amazed
I did not think to try it on that other computer. Thanks a lot, Chuck.

BTW, is there any harm in leaving the IRPStackSize at 50? Or should I work
my way down by 3s until it does not work, then raise it up so it will work?
In other words, should I use the minimum necessary to map a network drive?

Thanks,
Gene

P.S. I just added your Blog (http://nitecruzr.blogspot.com/) to my "Try Hard
to Check Daily" List. I can learn a lot from it. Thanks.
Click to expand...

Thanks for the update there, Gene. I don't really know why the instructions
tell us to start with a small value, and work up. I'd say if your computer runs
stably, leave it at that.

You might want to keep an eye on resource utilisation - Process Explorer is a
free Microsoft product, that will show you a lot more than Task Manager.
<http://nitecruzr.blogspot.com/2006/04/watching-what-your-computer-is-doing.html>
http://nitecruzr.blogspot.com/2006/04/watching-what-your-computer-is-doing.html
 
Chuck said:
Earlier, I described a problem trying to map network drives between two
computers on a home network. I had applied Microsoft's fix described in
KB177078.
In response, "Chuck" wrote
Which computer did you apply the change on, Gene?
http://nitecruzr.blogspot.com/2005/06/server-functionality-affected-by.html
Click to expand...

And I responded:
I made the changes on the computer from which I tried to connect to the
other, that is, on the computer that gave me the error message. The
other
computer can connect to the "problem" computer, so I never thought of
making the change to it. But--it makes sense, because, when I brought
the
"problem" computer to work I was able to map network drives to the
office
computers. [Sound of hand slapping forehead!] I never made the
connection;
the problem must be the other computer.

Thanks for the tip. I will try it when I get home tonight.
Click to expand...


I just created the IRPStackSize parameter in the Registry on the other
computer--the one TO which I am trying to connect--and it works! I am
amazed
I did not think to try it on that other computer. Thanks a lot, Chuck.

BTW, is there any harm in leaving the IRPStackSize at 50? Or should I work
my way down by 3s until it does not work, then raise it up so it will
work?
In other words, should I use the minimum necessary to map a network drive?

Thanks,
Gene

P.S. I just added your Blog (http://nitecruzr.blogspot.com/) to my "Try
Hard
to Check Daily" List. I can learn a lot from it. Thanks.
Click to expand...

Thanks for the update there, Gene. I don't really know why the
instructions
tell us to start with a small value, and work up. I'd say if your
computer runs
stably, leave it at that.

You might want to keep an eye on resource utilisation - Process Explorer
is a
free Microsoft product, that will show you a lot more than Task Manager.
<http://nitecruzr.blogspot.com/2006/04/watching-what-your-computer-is-doing.html>
http://nitecruzr.blogspot.com/2006/04/watching-what-your-computer-is-doing.html
Click to expand...


Thank you, I have Process Explorer in my Startup folder and use it to tell
me when my computer is ready to use each morning. Some processes, especially
svchost.exe, really hog resources, so I do not try to launch Outlook or
other big programs until the computer has quieted down. I have other things
to keep me busy.

I have bookmarked your blog item on Process Explorer, to read it later.

Thanks again for the help with this problem.

Kind regards,
Gene
 
Back
Top