Article ID: 223863 - Last Review: November 1, 2006 - Revision: 2.5 Spooler Service May Leak Memory Attempting to Close Print ProcessorThis article was previously published under Q223863 On This PageSYMPTOMS
The Spooler Service may leak private bytes when it attempts to close the print processor following the alteration of a print job.
CAUSE
The Spooler Service does not close the print processor under certain conditions in which the logic indicates the function is being re-entered.
RESOLUTIONWindows NT Server or Workstation 4.0To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
(http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)
Windows NT Server 4.0, Terminal Server EditionTo resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:152734
(http://support.microsoft.com/kb/152734/EN-US/
)
How to Obtain the Latest Windows NT 4.0 Service Pack
NOTE: If you install this fix, and then upgrade to Windows NT 4.0 Service Pack 6 without setting the UseSoftwareHive key discussed in article Q239907, you lose all your printers. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6. MORE INFORMATION
Because this fix addresses a GDI resource leak, an additional symptom of this problem is the printing of a print job with a data type of TEXT reported as spooled, but that never actually prints.
| Article Translations
|
Back to the top
