Error 1130: Server storage
Daniel Mizrahi
Hello! I have a problem with a workstation. It can see the domain but the
domain can't see it back. When I'm trying to start the server service I get
this error:
Error 1130: Not enough server storage is available to process this command.
I'd appreciate any help.
Thank you
Nili
pepperami
Daniel
This is an excerpt from TechNet:-
To correct this problem:
WARNING: Using Registry Editor incorrectly can cause serious, system-wide
problems that may require you to reinstall Windows NT to correct them.
Microsoft cannot guarantee that any problems resulting from the use of
Registry Editor can be solved. Use this tool at your own risk.
1. Run Registry Editor (REGEDT32.EXE).
2. From the HKEY_LOCAL_MACHINE subtree, go to the following key:
\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
3. From the Edit menu, choose Add Value.
4. Use the following values:
Value Name: MinFreeConnections
Data Type: REG_DWORD
Decimal: 5
5. Close Registry Editor.
6. Run Control Panel and choose Network.
7. Under Installed Network Software, highlight Server and then choose
Configure.
8. Under Optimization, select Maximize Throughput for File Sharing
and then choose OK.
9. Either shutdown and restart Windows NT, or from a command prompt,
type the following two commands (pressing ENTER after each line):
net stop server
net start server
Hope this helps...
Thanks
______________________________________________
Peter White, MCP, CBS
pe...@pepperami.force9.co.uk
Daniel Mizrahi wrote in message <6gagkl$vg6$1...@news.ibm.net.il>...
Frank Hilger
PSS ID Number: Q106167
Article last modified on 11-07-1997
3.1 3.5 3.51 4.0
winnt
======================================================================
-----------------------------------------------------------------------
The information in this article applies to:
- Microsoft Windows NT operating system version 3.1
- Microsoft Windows NT Advanced Server version 3.1
- Microsoft Windows NT Workstation versions 3.5, 3.51, and 4.0
- Microsoft Windows NT Server versions 3.5, 3.51, and 4.0
-----------------------------------------------------------------------
When you access shares on a 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.
MORE INFORMATION
================
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). Depending on the
hardware configuration of a specific machine, 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.
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. The value of IRPStackSize defaults to 0x4
if it is not explicitly present. If the key is not present, choose
Add Value in the Registry Editor. The Value Name should be IRPStackSize
and the Data Type is REG_DWORD..
WARNING: Using Registry Editor incorrectly can cause
serious, system-wide problems that may require you to
reinstall Windows NT to correct them. Microsoft cannot
guarantee that any problems resulting from the use of
Registry Editor can be solved. Use this tool at your own
risk.
Additional query words: wfw wfwg prodnt IRP stack size
======================================================================
Keywords : NTPROTOCOL ntregistry NTSrvWkst kbnetwork
Version : 3.1 3.5 3.51 4.0
Platform : winnt
============================================================================
=
Copyright Microsoft Corporation 1997.
Frank Hilger
Daniel Mizrahi schrieb in Nachricht <6gagkl$vg6$1...@news.ibm.net.il>...
Nick Jeffrey
Please refer to Microsoft Knowledge base article Q106167 for a detailed
description of the problem.
In a nutshell, the following registry value is set too low:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManServer\Parameters
\IRPStackSize
If the IRPStackSize value does not exist, it will default to 4. Try
increasing this value until the problem disappears. The maximum value is
12 (decimal) or c (hex). Every increment takes up 36 bytes of memory, so
don't go overboard on memory-constrained systems.
Daniel Mizrahi <dan...@tsk.co.il> wrote in article
Chris Foster
On Mon, 6 Apr 1998 15:09:29 +0300, "Daniel Mizrahi" <dan...@tsk.co.il>
wrote:
>Hello! I have a problem with a workstation. It can see the domain but the
>domain can't see it back. When I'm trying to start the server service I get
>this error:
>Error 1130: Not enough server storage is available to process this command.
>I'd appreciate any help.
>Thank you
>Nili
>
>
There are lots of official lines from MS on this one. It could be one
of the already mentioned solutions of could be one of these:
- you need to reapply SP3
or
- your registry is set to a maximum size and your registry files are
getting too big. This is also an MS solution and I've never seen it
work in practice.
Good luck