Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/172462

From BetaArchive Wiki
Knowledge Base


Article ID: 172462

Article Last Modified on 11/1/2006



APPLIES TO

  • Microsoft Windows NT Workstation 3.5
  • Microsoft Windows NT Workstation 3.51
  • Microsoft Windows NT Server 3.5
  • Microsoft Windows NT Server 3.51



This article was previously published under Q172462

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: kbbug kberrmsg kbfix kbprint KB172462