questioner
asked on
WinNT Server Service Not working
I am using NT workstation and networking with a couple of 95 machines. They are networked in a workgroup. The problem that I am having is that the NT machine will not join the work group nor can I share out any of it's drives. When the Server service tries to start up I get an error saying "Not enough server storage is available to process this command" What can I do to fix this??
I have plenty of space on the hard drive and plenty of RAM any assistance would be appreciated.
I have plenty of space on the hard drive and plenty of RAM any assistance would be appreciated.
What service pack are you running on the NT box?
How much room is on your C: partition? How do you have the swap files (virtual memory) set up?
I found this info at M$
Err Msg: "Not Enough Server Storage is Available to Process..."
--------------------------
The information in this article applies to:
Microsoft Windows NT Advanced Server, version 3.1
Microsoft Windows NT Server versions 3.5, 3.51, 4.0
--------------------------
SYMPTOMS
While running Windows NT, the following error message appears:
Not enough server storage is available to process this command.
CAUSE
This indicates that Windows NT does not have enough paged pool memory available to process a command. This can happen when the PagedPoolSize is either set too small or when an application does not re-allocate memory correctly.
Insufficient PagedPoolSize may be due to the fact that the INITIAL.INF file that shipped with Windows NT contains the following lines:
Ifstr(i) $(STF_PRODUCT) == "LanmanNT"
Ifstr(i) $(!STF_DOMAIN_ROLE) == "DC"
Debug-Output "SETUP.INF: AddPdcMachineAccount for PDC of new domain..."
LibraryProcedure STATUS, $(!LIBHANDLE),
AddPdcMachineAccount $(!STF_COMPUTERNAME)
Debug-Output "SETUP.INF: AddPdcMachineAccount returned: "$(STATUS)
Endif
shell "REGISTRY.INF" MakeQuotaEntries 48 24 Endif
The call to REGISTRY.INF only happens for Windows NT servers, not workstations. The parameters passed to REGISTRY.INF are PagedPoolSize (48) and RegistrySizeLimit (24). The PagedPoolSize value over-rides the value calculated at bootup based on physical memory. The algorithm for calculating PagedPoolSize at bootup produces values approximating the physical memory size of the computer up to a maximum of 192 megabytes.
For additional information on this algorithm, please see the following article(s) in the Microsoft Knowledge Base:
Q126402: PagedPoolSize and NonPagedPoolSize Values in Windows NT 3.5
WORKAROUND
This problem can be worked around by using the registry editor to zero out the PagedPoolSize parameter.
WARNING: Using the 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 the Registry Editor can be solved. Use this tool at your own risk.
The page pooled memory management parameters are located in:
HKEY_LOCAL_MACHINE
\SYSTEM
\CurrentControlSet
\Control
\Session Manager
\Memory Management
If the error is due to an application not re-allocating memory correctly, normal troubleshooting using tools such as Performance Monitor, or PMON.EXE (from the Windows NT Resource Kit) should be employed to isolate the problem component.
STATUS
Microsoft has confirmed this to be a problem in Windows NT Advanced Server version 3.1 and Windows NT Server version 3.5. This problem was corrected in Windows NT version 3.51.
Additional query words: prodnt 3.10 poolcalc
AND ALSO
Server Service Fails with System Error 8 or System Error 234
--------------------------
The information in this article applies to:
Microsoft Windows NT Workstation version 4.0
Microsoft Windows NT Server version 4.0
--------------------------
SYMPTOMS
The server service fails to start and the following events are recorded:
Event ID: 7023
Source: Service Control Manager
Type: Error
Description: The Server service terminated with the following error:
More data is available.
-or-
Not enough storage is available to process this command.
Event ID: 7001
Source: Service Control Manager
Type: Error
Description: The Net Logon service depends on the Server service
which failed to start because of the following error:
More data is available.
If you attempt to start the server service manually, the following errors may be displayed:
A system error has occurred.
System error 234 has occurred.
More data is available.
-or-
System error 8 has occurred.
Not enough storage is available to process this command.
Other services that may fail to start (also with event ID 7001) include the computer browser and the directory replicator, because these services are dependent on the Server service.
CAUSE
The cause of these errors is the result of too much data stored in the following key in the registry.
HKEY_LOCAL_MACHINE\System\
NOTE: The above registry key is one path; it has been wrapped for readability.
The Server service queries the registry value above for its entries. The buffer for the amount of information that the Server service can accept when it queries is approximately 32 KB. If there are more than 32 KB in that entry, the Server service will fail to start and return the error "More data is available," or "Not enough storage is available."
RESOLUTION
The solution is to remove any unnecessary entries from this value in the registry, or apply (or reapply) the latest Windows NT Service pack.
What I would do first is to reapply the latest service pack before anything else.
best regards
Draak
Err Msg: "Not Enough Server Storage is Available to Process..."
--------------------------
The information in this article applies to:
Microsoft Windows NT Advanced Server, version 3.1
Microsoft Windows NT Server versions 3.5, 3.51, 4.0
--------------------------
SYMPTOMS
While running Windows NT, the following error message appears:
Not enough server storage is available to process this command.
CAUSE
This indicates that Windows NT does not have enough paged pool memory available to process a command. This can happen when the PagedPoolSize is either set too small or when an application does not re-allocate memory correctly.
Insufficient PagedPoolSize may be due to the fact that the INITIAL.INF file that shipped with Windows NT contains the following lines:
Ifstr(i) $(STF_PRODUCT) == "LanmanNT"
Ifstr(i) $(!STF_DOMAIN_ROLE) == "DC"
Debug-Output "SETUP.INF: AddPdcMachineAccount for PDC of new domain..."
LibraryProcedure STATUS, $(!LIBHANDLE),
AddPdcMachineAccount $(!STF_COMPUTERNAME)
Debug-Output "SETUP.INF: AddPdcMachineAccount returned: "$(STATUS)
Endif
shell "REGISTRY.INF" MakeQuotaEntries 48 24 Endif
The call to REGISTRY.INF only happens for Windows NT servers, not workstations. The parameters passed to REGISTRY.INF are PagedPoolSize (48) and RegistrySizeLimit (24). The PagedPoolSize value over-rides the value calculated at bootup based on physical memory. The algorithm for calculating PagedPoolSize at bootup produces values approximating the physical memory size of the computer up to a maximum of 192 megabytes.
For additional information on this algorithm, please see the following article(s) in the Microsoft Knowledge Base:
Q126402: PagedPoolSize and NonPagedPoolSize Values in Windows NT 3.5
WORKAROUND
This problem can be worked around by using the registry editor to zero out the PagedPoolSize parameter.
WARNING: Using the 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 the Registry Editor can be solved. Use this tool at your own risk.
The page pooled memory management parameters are located in:
HKEY_LOCAL_MACHINE
\SYSTEM
\CurrentControlSet
\Control
\Session Manager
\Memory Management
If the error is due to an application not re-allocating memory correctly, normal troubleshooting using tools such as Performance Monitor, or PMON.EXE (from the Windows NT Resource Kit) should be employed to isolate the problem component.
STATUS
Microsoft has confirmed this to be a problem in Windows NT Advanced Server version 3.1 and Windows NT Server version 3.5. This problem was corrected in Windows NT version 3.51.
Additional query words: prodnt 3.10 poolcalc
AND ALSO
Server Service Fails with System Error 8 or System Error 234
--------------------------
The information in this article applies to:
Microsoft Windows NT Workstation version 4.0
Microsoft Windows NT Server version 4.0
--------------------------
SYMPTOMS
The server service fails to start and the following events are recorded:
Event ID: 7023
Source: Service Control Manager
Type: Error
Description: The Server service terminated with the following error:
More data is available.
-or-
Not enough storage is available to process this command.
Event ID: 7001
Source: Service Control Manager
Type: Error
Description: The Net Logon service depends on the Server service
which failed to start because of the following error:
More data is available.
If you attempt to start the server service manually, the following errors may be displayed:
A system error has occurred.
System error 234 has occurred.
More data is available.
-or-
System error 8 has occurred.
Not enough storage is available to process this command.
Other services that may fail to start (also with event ID 7001) include the computer browser and the directory replicator, because these services are dependent on the Server service.
CAUSE
The cause of these errors is the result of too much data stored in the following key in the registry.
HKEY_LOCAL_MACHINE\System\
NOTE: The above registry key is one path; it has been wrapped for readability.
The Server service queries the registry value above for its entries. The buffer for the amount of information that the Server service can accept when it queries is approximately 32 KB. If there are more than 32 KB in that entry, the Server service will fail to start and return the error "More data is available," or "Not enough storage is available."
RESOLUTION
The solution is to remove any unnecessary entries from this value in the registry, or apply (or reapply) the latest Windows NT Service pack.
What I would do first is to reapply the latest service pack before anything else.
best regards
Draak
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Draak, that looks like it will do the trick. Now I just need to dig out my service pack.
Much appreciated.
Much appreciated.