A print job is deleted without being printed on a computer that is running Windows Server 2003 with Service Pack 1

On a computer that is running Microsoft Windows Server 2003 with Service Pack 1 (SP1), you use an application that prints by using a service that calls the ImpersonateLoggedOnUser function. For example, you use the eTrust Antivirus Alert Manager from Computer Associates to print trouble ticket items. After you do this, you see the print job spool in the print monitor. However, the print job has no size entry and is deleted without being printed. Additionally, the following error message may be logged in the Application event log on the print server:

Event Type: Information
Event Source: Print
Event Category: None
Event ID: 13
Description: Document document_number, document_name owned by user_name was deleted on printer_ name.

This problem occurs because a change was made to the spooler process in Windows Server 2003 SP1. When an application submits print jobs by calling the ImpersonateLoggedOnUser function, the application may not have access to duplicate handles. Duplicate handles are required by the Print Spooler service.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows Server 2003 with SP1, Itanium-based versions

Windows Server 2003, x64-based versions

Windows Service 2003 with SP1, x86-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.