|
Error: "Not enough server storage is available
to process this command."
The solution is in an obscure parameter known as
IRPStackSize. IRP stands for Input/Output Request Packet. This
packet contains specially formatted data that device drivers use
to communicate with each other deep within Windows' core, or
kernel. A "stack" in this context is a kind of scratchpad memory
used by the operating system. Thus IRPStackSize determines how
much scratchpad memory is set aside to handle IRPs.
In small networks, you normally don't have to worry about IRPs.
The default IRPStackSize is 15, and that's plenty of space for
typical operations. But some software can use up the available
space in the stack. When one too many IRPs come in, whatever
input/output operation was going on screeches to a halt and you
get the error message "Not enough server storage is available to
process this command" or "Not enough memory to complete
transaction."
Microsoft specifically fingers Symantec's Norton Antivirus in
Knowledge Base article 177078, which refers specifically to IRP
stack space running out.
Both Microsoft and Symantec focus on Norton Antivirus, but a
general Web search reveals that many users also associate this
error with Symantec's Norton Ghost.
Edit the Registry to increase IRPStackSize
Open the Registry Editor (Regedit) and navigate to the following
key:
HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Services \
LanmanServer \ Parameters
Figure 1. The Registry (click photos to enlarge). Editing the
Registry is the only way to get around the networking problem
caused by Symantec software. Here we've created a new blank
DWord and are about to type in the name: IRPStackSize.
Open the Parameters folder and left-click once in an empty
portion of the right pane. If IRPStackSize is already shown
under Name in the right-hand pane, double-click it, select
Decimal and increase the value shown in the Value data by at
least three. (More on this in a moment.)
The odds are that IRPStackSize won't even appear in the right
pane. This means Windows is operating purely on its internal
default settings for IRPStackSize. In this case, point to
Edit/New, and then click DWord Value. Enter IRPStackSize as the
new value in the right-hand pane. (The name is case-sensitive;
enter it exactly as shown.) Right-click on the entry you just
created and select Modify. Then select Decimal and, in the Value
Data box, enter the number you want. (See below.) Close the
Registry and reboot. See if the problem is resolved.
What size should you specify? The default value is 15, but you
can go as high as 49, if you need to. (Technically, you can go
all the way to 50, but Microsoft says using the maximum value
may cause more problems, so it's best to stay south of that
maximum.) Raising the IRPStackSize to 25 solved the problem on
Franz's system.
If 25 doesn't work for you, a little trial and error may be
necessary to get things right for your setup. Just keep bumping
the number up until you no longer see the error message.
Source: Fred Langa - Langalist
http://WindowsSecrets.com
|