Some print jobs fail together with the Event 6161 when the "Print to File" option is used on a multiprocessor computer that is running Windows Server 2008 or Windows Vista and that is under heavy stress

Consider the following scenario:

• You have a multiprocessor computer that is running Windows Server 2008 or Windows Vista.
• You use the Print to File option to create lots of print jobs such as over 10000 print jobs.

In this scenario, some print jobs fail and the Event ID 6161 is logged in the System log:

Source: Microsoft-Windows-PrintSpooler
Event ID: 6161
Task Category: None
Level: Error
Keywords: Classic
Description:
The document <document name>, owned by <user name>, failed to print on printer <printer name>. Try to print the document again, or restart the print spooler.
Data type: RAW. Size of the spool file in bytes: 0. Number of bytes printed: 0. Total number of pages in the document: 0. Number of pages printed: 0. Client computer: <computer name>. Win32 error code returned by the print processor: 5. Access is denied.

This problem occurs because the Print Spooler service does not check the output file name correctly when the Print Spooler service assigns a file port to a print job. This behavior results in a timing issue when the computer is under heavy stress. This timing issue causes the Print Spooler service to use an incorrect output file name when the print job is handled. Therefore, the print job fails together with the error message "Access is denied."

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 the problem described in this article. 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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the �Hotfix Request� page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, your computer must be running one of the following operating systems:

• Windows Server 2008
• Windows Server 2008 Service Pack 2 (SP2)
• Windows Vista Service Pack 1 (SP1)
• Windows Vista Service Pack 2 (SP2)

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 previously released 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 item in Control Panel.

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008 and of Windows Vista SP1

For all supported x86-based versions of Windows Server 2008 SP2 and of Windows Vista SP2

For all supported Itanium-based versions of Windows Server 2008

For all supported Itanium-based versions of Windows Server 2008 SP2

For all supported x64-based versions of Windows Server 2008 and of Windows Vista SP1

For all supported x64-based versions of Windows Server 2008 SP2 and of Windows Vista SP2

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Additional file information for Windows Server 2008 and for Windows Vista

Additional files for all supported x86-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported x64-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported Itanium-based versions of Windows Server 2008 and of Windows Vista