The Print Spooler service may stop sending print jobs

The print queue on a Windows Server 2003-based computer may stop working for a printer that uses the standard port monitor (SPM) for TCP/IP. Specifically, the Print Spooler service may stop sending print jobs to this printer, even though the spooler continues to send print jobs to other printers. In this situation, the print job in the printer's queue shows a status of "Printing." If you remove the print job from the queue, and then you try to print again, the same problem occurs.

Back to the top

Resolution

This problem occurs because of an access violation that occurs in the printer-dr...

This problem occurs because of an access violation that occurs in the printer-driver process. When this problem occurs, the spooler does not stop, and the SPM port is not reset. This causes the print queue to crash.

To have us fix this problem for you, go to the "Fix it for me" section. If you'd rather fix this problem yourself, go to the "Let me fix it myself" section.

Back to the top

Fix it for me

To fix this problem automatically, click the Fix this problem link. Then, click Run in the File Download dialog box and follow the steps in the wizard.

Fix this problem
Microsoft Fix it 50226

Note This wizard may be in English only; however, the automatic fix also works for other language versions of Windows.

Note If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or to a CD, and then you can run it on the computer that has the problem.

Now go to the "Did this fix the problem?" section.

Back to the top

Let me fix it myself

This hotfix is designed to help diagnose where in the printer-driver process the access violation occurs. After you install this hotfix, a User.dmp file is created for the spooler process when this problem occurs. Send this User.dmp file to the manufacturer of the printer, and then request that the manufacturer provide an updated driver.

After you install this hotfix, create a registry value to enable the system to create a User.dmp file for the spooler process. Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756  (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows

To create this registry value and then enable it, follow these steps:

1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Locate the following subkey in the registry, and then click this subkey:
   
   

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type ThrowDriverException for the name of the DWORD value, and then press ENTER.
5. Right-click ThrowDriverException, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Exit Registry Editor.

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:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

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

Before you apply this hotfix, make sure that the computer is running one of the following operating systems:

• A 32-bit version of Windows Server 2003 with Service Pack 2 (SP2)
• An Itanium-based version of Windows Server 2003 with SP2
• An x64-based version of Windows with SP2

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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.

Windows Server 2003, x86-based versions

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform
Localspl.dll	5.2.3790.4046	342,016	23-Mar-2007	20:24	x86

Windows Server 2003, x64-based versions

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform
Localspl.dll	5.2.3790.4046	750,080	23-Mar-2007	22:15	x64

Windows Server 2003, Itanium-based versions

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform
Localspl.dll	5.2.3790.4046	968,192	23-Mar-2007	22:16	IA-64