Changes in IRP Stack Size in Lanman Server

ID: Q198386

The information in this article applies to:

Microsoft Windows NT Server version 4.0
Microsoft Windows NT Server version 4.0, Terminal Server Edition

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

When you access shares on a computer running Windows NT Server from a Windows NT client and the IRPstackSize parameter is set too low on the server, you may receive the following error message:

Not enough server storage is available to process this command.

CAUSE

Depending on the hardware configuration of a specific computer, the default value may not be large enough for the Srv service to properly administer shared directories on some of the physical drives. You may see one or both of 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 client tries to access certain shared directories on such a server.

When a Windows for Workgroups client tries to access the same shared directories, the following message will be generated:

Path not found.

WORKAROUND

To work around this problem, modify the registry by using the following information.

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

The registry value IRPstackSize, which may be listed at


   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer
   \Parameters

defaults to 0x4 if the value is not explicitly present. Valid values range from 0x1 to 0xC (1 to 12).

To increase the value of the parameter when it is not already present, go to the key:


   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
   \LanmanServer\Parameters

NOTE: The above registry key is one path; it has been wrapped for readability.

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 Value Name should be IRPStackSize and the Data Type is REG_DWORD.

RESOLUTION

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:

http://www.microsoft.com/windows/servicepacks/

Q152734 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:

http://www.microsoft.com/support/supportnet/overview/overview.asp

Service Pack 4 changes the default value to 11 with the minimum value allowed as 11. So, if you have any entry for this value and you have applied SP4 and the property is less than 11, just delete the value: IRPstackSize. Then, the new default value of 11 will be in effect.

STATUS

Microsoft has confirmed this to be 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.

Additional query words:

Keywords : NT4SP4Fix kbbug4.00 kbfix4.00.sp4
Version : winnt:4.0
Platform : winnt
Issue type : kbbug