The information in this article applies to:
SYMPTOMS
If you have insufficient resources on your Windows NT Server system, one
or both of the following errors may appear on clients computers that are
trying to connect to the server:
-or-
NOTE: These errors may appear in a windowed dialog box, or as a numbered event error message in the system log on the client computer. The service or utility running on the server at the time of the error determines how the error appears on the client. CAUSEIf your server has more than 48 megabytes of RAM, the problem may occur because PagedPoolSize is set too small. The static value for PagedPoolSize is established when you install Windows NT. RESOLUTIONThis has been corrected in Windows NT 3.51. When you upgrade your computer from a previous version, if Windows NT Setup finds the value 0x03000000 (48 MB), it is reset to 0, which is the 3.51 default at installation time. WORKAROUND
You may be able to work around this problem by increasing the
PagedPoolSize value in the registry.
STATUSMicrosoft has confirmed this to be a problem in Windows NT Advanced Server version 3.1 and Windows NT Server version 3.5. This problem has been resolved in Windows NT version 3.51. MORE INFORMATION
The small PagedPoolSize is only one of several potential triggers, or
first causes, that affect the operation of SERVICES.EXE. The "RPC server is
too busy..." and "RPC server unavailable..." messages indicate that
SERVICES.EXE or one of its threads may have hung. A thread may remain in a
blocking state and appear to be hung if a resource is not available.
Q130069 SERVICES.EXE Fails With Access Violation and Returns RPC Busy... Q126401 Err Msg: "Not Enough Server Storage is Available to Process..." Additional query words: 3.10 prodnt cpr sufficient pagedpool page pool size ntfaqmax
Keywords : kberrmsg kbnetwork ntconfig ntregistry NTSrv |
Last Reviewed: October 6, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |