This article was previously published under Q198386
When you access shares on a computer running Windows NT Server from aWindows NT client and the IRPstackSize parameter is set too low on theserver, you may receive the following error message:
Not enough server storage is available to process this command.
Depending on the hardware configuration of a specific computer, the defaultvalue may not be large enough for the Srv service to properly administershared directories on some of the physical drives. You may see one or bothof the following event messages:
Event ID: 2011 Source: Srv The server's configuration parameter "irpstacksize" is too small for the server to use a local device. Please increase the value of this parameter. Event ID: 0 Source SRV Description: Description for Event ID 0 could not be found. It contains the insertion string \device\LanManServer
You may receive one of the above error message when a Windows NT clienttries to access certain shared directories on such a server.
When a Windows for Workgroups client tries to access the same shareddirectories, the following message will be generated:
Path not found.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition or the individual software update. For information on obtaining the latest service pack, please go to:
152734 how to obtain the latest windows nt 4.0 service pack
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
Service Pack (SP) 5 sets a minimum allowed of 7. It ignores all smaller values, and sets a default of 7 if none is specified.
SP6 sets a minimum allowed of 7. It ignores all smaller values and sets a default of 11 if none is specified.
To work around this problem, modify the registry by using the followinginformation.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
The registry value IRPstackSize, which may be listed at
NOTE: The above registry key is one path; it has been wrapped forreadability. For the IRPStackSize change to take effect, the Server has to be rebooted.
The value of IRPStackSize defaults to 0x4 if it is not explicitly present.If the key is not present, click Add Value in Registry Editor. The ValueName should be IRPStackSize and the Data Type is REG_DWORD.
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.