luke k
asked on
out of server storage space
can anyone suggest a solution for this message recieved
when the win nt server service tries to start:
error 1130: not enough server storage is available to process this command.
what is server storage and what can i do to set this.
i am presuming that this is not related to physical disk space, as i have a sufficient amount for any function.
I have 2 pagefiles set on drives D: and C: (winnt is on e:)
The size of the pagefile on both of these drives is
set to 75 - 200 so there should be more than enough memory.
I also have 96Mb of RAM.
thanks
Luke.
when the win nt server service tries to start:
error 1130: not enough server storage is available to process this command.
what is server storage and what can i do to set this.
i am presuming that this is not related to physical disk space, as i have a sufficient amount for any function.
I have 2 pagefiles set on drives D: and C: (winnt is on e:)
The size of the pagefile on both of these drives is
set to 75 - 200 so there should be more than enough memory.
I also have 96Mb of RAM.
thanks
Luke.
ASKER
Edited text of question
ASKER
I have 2 pagefiles set on drives D: and C: (winnt is on e:)
The size of the pagefile on both of these drives is
set to 75 - 200 so there should be more than enough memory.
I also have 96Mb of RAM.
The size of the pagefile on both of these drives is
set to 75 - 200 so there should be more than enough memory.
I also have 96Mb of RAM.
decrease your upper limit to 100 MB
ASKER
no change :(
Hy luke,
found it somewhere:
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.
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. When this is the case, the Event Log on the server in question will contain the following event message:
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.
You may receive 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, drill down to the HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\Services \ LanmanServer\ Parameters key in the Registry Editor and choose Add Value from the Edit menu. The Value Name should be IRPstackSize and the Data Type is REG_DWORD.
found it somewhere:
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.
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. When this is the case, the Event Log on the server in question will contain the following event message:
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.
You may receive 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, drill down to the HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\Services
ASKER
Hello,
In the directory you specify above in the registy there is
a value called 'Size: REG_DWORD 0x1' and as you said
added the value 'IRPstackSIze: REG_DWORD 0x4' that
seemed to be ok but are these 2 one in the same?
I changed the value for IRPstackSize from 0x1 up to 0x12
but the error still occurred. The 'Size' value could
only be changed to 0x1 and 0x2 and that was all, all other values
gave an error in the event viewer.
Is what I did right? Obviously not because i didn't work...
Thanks,
Melinda
In the directory you specify above in the registy there is
a value called 'Size: REG_DWORD 0x1' and as you said
added the value 'IRPstackSIze: REG_DWORD 0x4' that
seemed to be ok but are these 2 one in the same?
I changed the value for IRPstackSize from 0x1 up to 0x12
but the error still occurred. The 'Size' value could
only be changed to 0x1 and 0x2 and that was all, all other values
gave an error in the event viewer.
Is what I did right? Obviously not because i didn't work...
Thanks,
Melinda
If you receive this error, you may have a non-zero PagedPoolSize entry in the registry. Edit:
HKEY_LOCAL_MACHINE\SYSTEM\ CurrentCon trolSet\Co ntrol\Sess ion Manager\Memory Management
Set PagedPoolSize to 0.
Reboot.
HKEY_LOCAL_MACHINE\SYSTEM\
Set PagedPoolSize to 0.
Reboot.
ASKER
Our problem was solved by installing
and overwritting all newer files.
I assume that they were residual from service pack 3.
Thank you for all your help.
Luke.
and overwritting all newer files.
I assume that they were residual from service pack 3.
Thank you for all your help.
Luke.
Hi
I have the same problem and think that only reinstalling (upgradeing) helps.
Michael
I have the same problem and think that only reinstalling (upgradeing) helps.
Michael
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Look at your pagefile at turns it on ca. 20 MB of your RAM.
e.g.
64 MB RAM
Pagefile 80- 95 MB
regards
Gerd