Not enough storage is available to process this command

  • Thread starter Thread starter Paul at Xerox
  • Start date Start date
P

Paul at Xerox

this is the error i get when i load the security rollup
update package when I try to view the Microsoft Windows
Network. this has happen on 3 PC that I have updated. I
get no event viewer errors. When I do a system restore
before update installed ,normal browsing returns.
 
-----Original Message-----
this is the error i get when i load the security rollup
update package when I try to view the Microsoft Windows
Network. this has happen on 3 PC that I have updated. I
get no event viewer errors. When I do a system restore
before update installed ,normal browsing returns.
.
Click to expand...
I stand corrected I remove that update and when I first
try to browse the Microsoft Network It will come up
populated but after about a minute it errors out with the
same problem.
 
Server storage is not the error. "Not enough storage is
available to process this command" I am not trying to
attach to a specific server. Just browse the Microsoft
Network
Click to expand...

Could you please post the entire error message? Often some other
text appears before the message you quoted and indicates where
the problem lies.

This error can be caused by some program that really gobbles up
memory.

Hans-Georg
 
I have the same problem. When I try to see my workgroup, the following error appears:

---------------------------------------
MYGROUP is not accessible. You might not have permission to use this network
resource. Contact the administrator of this server to find out if you have
access permissions.

Not enough storage is available to process this command.
---------------------------------------

Where MYGROUP is the name of the workgroup.

This problem does not happens with W2K neither W9x computers, only with WinXP! The XP instalation is Professional with Service Pack 4 and all fixes until 2005-06-26 (Automatic Updates On).

I have permission to access the workgroup (the access works sometimes). All computers is accessible through "net view \\computer".

The guest account is enabled and the "net use \\computer /user:guest" works.

The workgroup has more then 6 computers with XP and all have the same problem. All network settings is done with DHCP.

We have one Wins server that resolves NetBIOS names correctly.

The node type on all computers are HYBRID and share type is SIMPLE.

Curiously, the problem is less frequent in a XP Home Edition computer (using peer-to-peer Network), but I cant use P2P with all computers because of broadcast restrictions.

It appears to be a XP related problem. Ah, I have tested several "master browsers" for the workgroup with different Windows versions and have tested a very small network with only one W98Se box, one W2k box and one XP Pro box.

If somebody finds the solution, please post here.
 
I have the same problem. When I try to see my workgroup, the following
error appears:

---------------------------------------
MYGROUP is not accessible. You might not have permission to use this
network
resource. Contact the administrator of this server to find out if you
have
access permissions.

Not enough storage is available to process this command.
---------------------------------------

Where MYGROUP is the name of the workgroup.

This problem does not happens with W2K neither W9x computers, only with
WinXP! The XP instalation is Professional with Service Pack 4 and all
fixes until 2005-06-26 (Automatic Updates On).

I have permission to access the workgroup (the access works sometimes).
All computers is accessible through "net view \\computer".

The guest account is enabled and the "net use \\computer /user:guest"
works.

The workgroup has more then 6 computers with XP and all have the same
problem. All network settings is done with DHCP.

We have one Wins server that resolves NetBIOS names correctly.

The node type on all computers are HYBRID and share type is SIMPLE.

Curiously, the problem is less frequent in a XP Home Edition computer
(using peer-to-peer Network), but I cant use P2P with all computers
because of broadcast restrictions.

It appears to be a XP related problem. Ah, I have tested several
"master browsers" for the workgroup with different Windows versions and
have tested a very small network with only one W98Se box, one W2k box
and one XP Pro box.

If somebody finds the solution, please post here.
Click to expand...

The "Not enough storage is available to process this command", aka IRPStackSize,
error, is well known.
<http://nitecruzr.blogspot.com/2005/06/server-functionality-affected-by.html>
 
Thanks for your reply, but IRPStackSize is not the cause of this problem. I had tested it. The error is not the same too.

Other tests:
All tests from MS Network Troubleshooting was done.
Session manager memory limits and number of concurrency process was raised up.
All other tests in WinXP Network Problem Solver from Hans-Georg Michna was done.
All tests from thread WinXP Losing Network Places from PCbanter.net was done.
The "Pchuck's Network article: The NT Browser" was read.
It's not a firewall related problem. I disabled it and tested.
We use TCP/IP only and have no domain, only workgroups.
It's not a DNS problem.
All computers use one antivirus (not Norton) and at least one anti-spyware.
It's appears to not be a Winsock or IP stack problem.
It's not a RestrictAnonymous problem.

Now I'm testing if it can be a network segment problem, isolating some computers in one small broadcast segment.

It is a recent issue. The problem was first related to me by a user less then a month ago.

In another small network, the problem was solved changing the workgroup name. One by one, all computers was assigned to the new workgroup, always testing if the problem appears. Curiously the network only work with one configuration: one computer with WinXP Pro as master browser. All other Windows flavors acting as master browsers caused the problem. All other computers have the master browser function disabled (setting the registry MaintainServerList value to No).
 
Thanks for your reply, but IRPStackSize is not the cause of this
problem. I had tested it. The error is not the same too.

Other tests:
All tests from MS Network Troubleshooting was done.
Session manager memory limits and number of concurrency process was
raised up.
All other tests in WinXP Network Problem Solver from Hans-Georg Michna
was done.
All tests from thread WinXP Losing Network Places from PCbanter.net was
done.
The "Pchuck's Network article: The NT Browser" was read.
It's not a firewall related problem. I disabled it and tested.
We use TCP/IP only and have no domain, only workgroups.
It's not a DNS problem.
All computers use one antivirus (not Norton) and at least one
anti-spyware.
It's appears to not be a Winsock or IP stack problem.
It's not a RestrictAnonymous problem.

Now I'm testing if it can be a network segment problem, isolating some
computers in one small broadcast segment.

It is a recent issue. The problem was first related to me by a user
less then a month ago.

In another small network, the problem was solved changing the workgroup
name. One by one, all computers was assigned to the new workgroup,
always testing if the problem appears. Curiously the network only work
with one configuration: one computer with WinXP Pro as master browser.
All other Windows flavors acting as master browsers caused the problem.
All other computers have the master browser function disabled (setting
the registry MaintainServerList value to No).
Click to expand...

What value did you finally set IRPStackSize to? The Microsoft article
<http://support.microsoft.com/?id=177078> recommends starting with 11, and
increasing by 3, to a maximum of 50. You wouldn't be the first to need more
than 18. Check some earlier posts here, and see.
<http://groups-beta.google.com/groups?q=irpstacksize&qt_s=Search>

If that's truly not it, and hearing how much research you have done, maybe it's
time to try a pay call to Microsoft Support.
 
I using IRPStackSize=30 (dec). But tested 50 too.

Another thing. Why the Local Network folder is now being auto-populated with all shares the WinXP box finds in the network? There is a way to disable this?
 
I using IRPStackSize=30 (dec). But tested 50 too.

Another thing. Why the Local Network folder is now being auto-populated
with all shares the WinXP box finds in the network? There is a way to
disable this?
Click to expand...

Tools - Options - View tab - uncheck "Automatically search...".
 
I've found in the folder properties where to disable the auto-populate option on my Local Network Folder.

The navigation in the network is faster now. I'll test to see if that problem stops now.
 
The problem was solved. What a small option can do!

Thanks Chuck.

--
Fabio Yamamoto
STI-IQUSP
 
Just disabled the auto-populate option on my Local Network Folder. I think this may using too much "unknown" memory stack on "my network places" (or similar).
--
Fabio Yamamoto
 
Back
Top