RPC Failure on Heavily Loaded Print Server

Last reviewed: March 4, 1998
Article ID: Q172462
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.5 and 3.51
  • Microsoft Windows NT Server versions 3.5 and 3.51

SYMPTOMS

On Windows NT print servers with more than 40 printers running simultaneously (independent of the number configured on the system), RPC failures may occur. A client may receive the following RPC errors and may fail to connect to the server; the event log may also report RPC errors. Opening the Control Panel or Print Manager may show one or more of the following error messages:

  • Error 1723: The RPC server is too busy to complete this operation.
  • Error 1722: The RPC server is unavailable.
  • Error 1721: Not enough resources are available to complete this
                   operation.
    
    
  • Error 1727:The remote procedure call failed and did not execute

CAUSE

This problem occurs because the spooler loses track of table entries assigned to each thread when the thread count goes above forty.

RESOLUTION

An updated Spoolss.exe is available.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.51. A supported fix is now available, but is not fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information.


Additional query words: fpnw lpd lpr
Keywords : ntprint NTSrvWkst kberrmsg kbprint
Version : WinNT:3.5,3.51
Platform : winnt
Issue type : kbbug
Solution Type : kbfix


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 4, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.