Restarted Print Job Are Deleted When Spooler Service Is Restarted
ID: Q219355
|
The information in this article applies to:
-
Microsoft Windows NT Server version 4.0
-
Microsoft Windows NT Server, Enterprise Edition version 4.0
-
Microsoft Windows NT Workstation version 4.0
-
Microsoft BackOffice Small Business Server versions 4.0, 4.0a, 4.5
SYMPTOMS
Submitted print jobs are deleted after you restart your computer or after the Print Spooler service is restarted.
CAUSE
This problem occurs when you restart the computer because the Print Spooler service deletes print jobs if they appear to be corrupted.
For documents that previously went through a cycle of printing, restarting, and printing, the spooler
incorrectly determines that the job is corrupted.
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or
the individual fix. For information on obtaining the
latest service pack, please go to:
For information on obtaining the individual fix, contact Microsoft
Product Support Services. For a complete list of Microsoft Product Support
Services phone numbers and information on support costs, please go to the
following address on the World Wide Web:
http://www.microsoft.com/support/supportnet/overview/overview.asp
NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.
For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871
Determining If You Are Eligible for No-Charge Technical Support
STATUS
Microsoft has confirmed this to be a problem in Windows NT 4.0. This problem was first corrected in Windows NT 4.0 Service Pack 5.
Additional query words:
Keywords : kbdocfix kbbug4.00 kbfix4.00 nt4sp5fix
Version : winnt:4.0,4.0a,4.5
Platform : winnt
Issue type : kbbug
Last Reviewed: July 14, 1999