This article was previously published under Q154541
Windows NT client workstations may open large numbers of \pipe\spoolssconnections to a print server. This usually occurs when you start anapplication (such as Microsoft Word) that queries printers. The spoolssprocess on both the client and the server will open a large number ofhandles related to these connections.
When the application opens the printer, the spooler detects that some ofthe printer attributes on the server have changed and the local cache isinvalid. The client then refreshes the cache, including form information.For each form, a WM_DEVMODECHANGE is issued, which causes the problem.When winword.exe sees this message, it thinks the printer configurationhas changed and reopens it. A lot of these messages are sent, causingWord to go into a tight loop opening printers.
A Remote Procedure Call (RPC) requires one named pipe instance for everyactive RPC call. Because there are all these OpenPrinter calls (which arehanging), RPC needs many named pipes. RPC won't destroy these instancesuntil all context handles (that is, all OpenPrinters) have been closed.
Obtain the fix referenced below. Apply this fix to the Windows NT clientsystem(s) to correct the problem.
For related information, see the following article in the MicrosoftKnowledge Base:
Microsoft has confirmed this to be a problem in Windows NT versions 3.5 and3.51. This problem was corrected in the latest Windows NT 3.51 U.S. ServicePack. For information on obtaining the Service Pack, query on the followingword in the Microsoft Knowledge Base (without the spaces):