Question

Locked

Print Spooler service not working

By cdensem ·
Hi
We have two printers on our network that were working fine and now we cant print to them. When we go to properties for the printer we get a message saying the printer spooler is not running. We have searched forums and followed tips on restarting the server and stopping and starting the print spooler but still no luck.
Any ideas please???

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

A couple of things to try

by Jacky Howe In reply to Print Spooler service not ...

Print Service Product Operations Guide
Chapter 5 - Troubleshooting
On This Page
Overview
Problem #1: Cannot Print to a Network Printer
Problem #2: Cannot Print from a Program
Problem #3: Spooler Retries Old Print Job
Problem #4: Print Server Modifies Print Jobs
Problem #5: Spooler and -Out of Resource- Messages
Problem #6: -Could Not Connect to Printer-
Problem #7: Application Error, Spoolsv.exe, Access Violation Message
Problem #8: Spoolsv.exe or -Print Subsystem Is Unavailable- Message
Problem #9: Cannot Create or Select a Print Monitor
Problem #10: PrintQueue Objects are Deleted

Overview
The following tables contain troubleshooting tips that should be useful in maintaining this product. The tips are based on known issues, and follow the best practices for troubleshooting and problem management outlined by the Incident Management SMF and the Problem Management SMF, both found in the MOF Supporting Quadrant.


Problem #1: Cannot Print to a Network Printer
Description of Problem
You cannot print to a network printer. The methods used to resolve this problem are independent of the program.

Resolution of Problem

Verify basic network connectivity. Check user rights, protocols, and share names to determine if you can see the server. Copy files to a share on the print server using Windows Explorer. If you cannot access the server, you may not be able to access the printer.

Create a local printer and redirect the port to the network printer. In the ports section, create a new port. Click Local and type the server and printer name for the printer (for example, \\servername\printername). Use this port for the local printer. This determines whether there is a problem with the copying of files from the server to the workstation when you click Connect To Setup or Network Printer in the Add Printer Wizard.

If you are printing from a Microsoft MS-DOS based program, make sure that the NET USE command has been run to map the LPT port to the network share. If it has, delete it and remap the port. If the printer works now, there may be an issue with ghosted connections. A command may need to be run in the logon script to remap the port each time you log on. If the printer is still not printing, try typing dir > LPT <x> where <x> is the number of the port being mapped. If it still does not print, double-check the networking.

If you are using LPR or printing to a JetDirect card using TCP/IP protocol, try the following:

? Use the PING protocol to look for the IP address. If it fails, check the network connectivity and verify the IP address.

? Create an LPR port to the printer, and then create a local printer connected to that port. This is the recommended way to connect to a JetDirect printer. Sharing this printer on the network allows the computer to act as a print queue for the JetDirect printer.




Problem #2: Cannot Print from a Program
Description of Problem
You cannot print from a program. The methods used to resolve this problem are independent of the program.

Resolution of Problem

? Use a simpler file. Try creating a new document with less information in it. This determines if it is the program or something in the documents that is causing the problem.


? Check available disk space on the system drive. If there is not enough room to spool the job, larger jobs may fail where smaller jobs may not.


? Try to print from another operating system. If possible, test with a third operating system. If it prints correctly, the problem is related to the output file.




Problem #3: Spooler Retries Old Print Job
Description of Problem
When you send a print job to a printer, the print spooler might not delete the spool file from the %SystemRoot%\System32\Spool\Printers folder when the print job is completed, and the print spooler might repeatedly attempt to spool the print job.

Resolution of Problem

? To prevent this behavior from occurring, do not change the attributes of a spool file while it is in the %SystemRoot%\System32\ Spool\Printers folder.

? To work around this behavior, remove the read-only attribute and then delete the spool file from the %SystemRoot%\System32\ Spool\Printers folder.




Problem #4: Print Server Modifies Print Jobs
Descriptions and Resolutions of Problem
Print server modifies client print jobs. There are five common job-alteration problems, each with its own resolution:

Description of Problem (1)

LPR client print jobs include PCL or PostScript code, include incorrectly printed extended characters, or print in the print devices default font.

Resolution of Problem (1)

This problem occurs when the LPR client sends commands to the Windows TCP/IP print server that responds by assigning the print job the TEXT data type.

? Reconfigure the LPR clients to send different commands so that Windows assigns the job the RAW data type.


Description of Problem (2)

Last page of a Microsoft network-based client print job does not print.

Resolution of Problem (2)

This problem occurs when client applications do not append form-feed commands to their print jobs, and the print manager default data type is RAW. To resolve this:

? Set the default data type value to RAW [FF Auto] or RAW [FF Appended], or reconfigure the client application to append a form feed to print jobs.


Description of Problem (3)

Extra page prints after a Microsoft network-based client print job.

Resolution of Problem (3)

Description of Problem (4)

Microsoft network-based client print jobs include PCL or PostScript code, include incorrectly printed extended characters, or print in the print devices default font.

Resolution of Problem (4)

This problem occurs when the print manager default data type is TEXT. To resolve this:

? Set the default data type value to RAW.


Description of Problem (5)

PostScript print jobs sent from Macintosh clients do not print in color, print at a lower resolution, or fail.

Resolution of Problem (5)



Problem #5: Spooler and -Out of Resource- Messages
Description of Problem
? When you restart the computer or restart the print spooler service, you receive the following error message: Spoolsv.exe failed to start.

? When you open the printers properties, you receive the following error message: "Out of resource error."

? When you print a document, you receive an Access violation (Dr. Watson) error message. The Dr. Watson log points to the Spoolsv.exe with error code C0000005. You receive the following error message, and the print spooler stops: The instruction at <address> referenced memory at <address>. The memory could not be read.


Cause of Problem

These problems may occur if the default local port monitor is changed by a third-party program.

Resolution of Problem

The following are steps for resolving this problem:

1.
Start the Registry Editor (RegEdt32.exe).

2.
Locate the local port value under the following key in the registry:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Control\Print\Monitors\LocalPort

3.
Double click the Driver subkey, and then edit the value. Change the string value to Localspl.dll and then click OK.

4.
Check the following registry key for third-party monitors. Remove any nondefault monitors:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Control\Print\MonitorsThe default port monitors are:

? Apple Talk Printing Devices (When Windows Services for Macintosh is installed)

? BJ language monitor

? Local port

? PJL language monitor

? Standard TCP/IP port

? USB monitor

? Windows NT fax monitor


5.
Check the following registry key for third-party print providers. Remove any nondefault print providers:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Control\Print\ProvidersThe default print providers are:

? Internet print providers

? LanMan print services


6.
Quit the Registry Editor and restart the print spooler.




Problem #6: -Could Not Connect to Printer-
Description of Problem
When you attempt to print or connect to a print queue, the following error message may appear: Could not connect to the printer <printer> because the print processor is unknown.

In addition, printer icons may be missing from the Printers folder.

Cause of Problem

The winprint key is corrupted or missing, or the data value contains a leading space in the following registry location:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Control\Print\Environments\

Windows NT x86\Print Processors

Resolution of Problem

1.
Start the Registry Editor (RegEdt32.exe).

2.
Go to the following registry location:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Control\Print\Environments\Windows NT x86\Print Processors

3.
Click the Print Processors key.

4.
On the Edit menu, click Add Key, and then type winprint in the Key Name field of the Add Key dialog box (leave the Class field blank).

5.
Type the following values (shown in bold type) in the Add Value dialog box, and then click OK:

? Value Name: Driver

? Data Type: REG_SZ


6.
For the String Value, type localspl.dll , and click OK.

7.
Quit the Registry Editor and restart the print server.




Problem #7: Application Error, Spoolsv.exe, Access Violation Message
Description of Problem
When you attempt to print or configure the printer in Windows Server 2003, you may receive the following error message:

? An application error has occurred and an application error log is being generated.

? Spoolsv.exe

? Exception: access violation (0xc0000005), Address: <Hex address>


Cause of Problem

This problem occurs if you have many .SHD and .SPL files in the spool directory. The default location for all printer spool files is %SystemRoot%\System32\Spool\Printers.

Resolution of Problem

1.
Stop the spooler service.

2.
Remove the .SHD and .SPL files from the Spool directory.

3.
Remove any unused or old .TMP file from the Temp directory.

4.
Restart the spooler service.




Problem #8: Spoolsv.exe or -Print Subsystem Is Unavailable- Message
Description of Problem
When you start a Windows Server 2003 print server, you may receive the following error message: Spoolsv.exe has generated an error.

Also, if you try to view the properties of a printer, you may receive an error message that says the print subsystem is unavailable.

Cause of Problem

The print spooler service might have stopped. This problem can also occur if the server running Windows Server 2003 has a print driver that is designed for Windows 98 or Windows NT.

Resolution of Problem

1.
Start the Registry Editor (RegEdt32.exe).

2.
Locate and remove the following key from the registry:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\ Control\Print\Printers\

<Trouble Printer>

3.
Quit the Registry Editor.




Problem #9: Cannot Create or Select a Print Monitor
Description of Problem
You are unable to create or select a print monitor. One of the following symptoms may occur:

? Double-clicking one of the installed available print monitors does nothing.

? When trying to add a port, such as an LPR Port, you may receive a Dr. Watson access violation or application error message in Spoolsv.exe. This may be followed by: Specified port cannot be added. The remote procedure call failed. The printer already exists.


Cause of Problem

This problem is caused by the spooler service not being allowed to interact with the desktop.

Resolution of Problem

1.
In Control Panel, double-click the Services icon.

2.
Click the Spooler service, and click the Startup button.

3.
Verify that the service is configured to log on using the system account, and that it is allowed to interact with the desktop.

4.
If invalid network printer port names appear in the list, they can be deleted from within the print manager.




Problem #10: PrintQueue Objects are Deleted
Description of Problem
All of the PrintQueue objects published by print servers on the same site as a given domain controller may be detected as orphaned and deleted, even though the corresponding printers are available in the domain.

Cause of Problem

When this occurs, the printer pruner writes a system event for each PrintQueue object that is detected as an orphan. This can accumulate rapidly for sites with large numbers of published print queues. If there are many published printers on the site, the system event log may become filled with printer pruner events.

Resolution of Problem

To prevent incorrect printer pruning while a domain controller is removed from the network, use either of the following methods:

? Before removing a domain controller from the network for an interval longer than the directory pruning interval and directory pruning retry periods, set the Directory Pruning Interval value to Never. These policies are located in Group Policy Object Editor under Computer Configuration\Administrative Templates\Printers.

? Stop the spooler service on the domain controller.

How to forcefully clear all jobs from a print queue

All administrators should know how to clear the print queue in Windows when all the jobs get ?stuck? and none of the jobs can be deleted. This will save you from having to restart a server (which is bad!).

In order to get the printing services back up and running, follow these steps:

1. Go to Start, Control Panel and Administrative Tools. Double click on Services icon.

2. Scroll down to the Print Spooler service and right click on it and select Stop. In order to do this, you need to be logged in as Administrator. At this point, no one will be able to print anything on any of the printers that are being hosted on this server.

3. Next you need to go to the following directory: C:\WINDOWS\System32\spool\PRINTERS. Delete all the files in this folder. This will clear all print queues (it?s a good idea to first make sure there are no other print jobs being processed on any of the other printers on the server because doing this step will delete those jobs also)

4. Now you can go back to the Services console and right-click and choose Start for the Print Spooler service!

You can also go to a command prompt and type net stop spooler or net start spooler to start and stop the service.

Collapse -

have you tried these?

by patrick.kam In reply to Print Spooler service not ...

assuming you are using Windows XP...
did you restart the spoller service on the server or on your machine??

click START, RUN, "services.msc" end ENTER.
scroll down to Print Spooler, right click it and click Restart.

Or, remove the printer from your machine, reboot and logon, then add the printer again...

Collapse -

Fixed

by cdensem In reply to have you tried these?

Hi

We have now fixed this problem after a long time with the issues. The print spooler on another server that was the issue.
Thanks for the replys.

Collapse -

Printer sharing not work after Window restart

by luutienkhai In reply to Print Spooler service not ...

My company use workgroup in LAN, Some PC run Win 7, a few PC run Win XP.
I have a problem such as: The printer is shared in a PC run Win XP. Others PC run Win 7 want to use commom printer. After install and setting printer shared on LAN all PC access and print very good. But after restart PC client (win 7) then cannot print.
Any person can help me now? Thank you very much.

Regard

Related Discussions

Related Forums