Event ID 350 — Print Job Status
Applies To: Windows Server 2008 R2
This is preliminary documentation and subject to change.
A print job is a file that contains data to be printed.
|Product:||Windows Operating System|
|Message:||Document %1 failed to print and was deleted because of corruption in the spooled file. The associated driver is: %2. Try printing the document again.|
Restart the Print Spooler service or reinstall the printer driver
To resolve this error, try again to print the document. If this fails, use the procedures in this topic to do the following:
- Delete the print job and restart the Print Spooler service.
- Reinstall the printer driver.
- Install an updated printer driver.
Delete the print job and restart the Print Spooler service
To delete the failed document and restart the Print Spooler service, use the two procedures in this section.
Warning: Restarting the Print Spooler causes all print jobs to be restarted. After restarting the Print Spooler service, you might need to either reset some printers or turn them off and then turn them on again. On an active print server, perform this procedure outside of normal business hours or during scheduled maintenance time, if possible. Before using this procedure, take all printers offline and wait for all print jobs to be completed, or pause all printers and wait for all print jobs with Active status to be completed.
To delete a failed print job and restart the Print Spooler service:
- In the Printers folder in Control Panel or the Print Management snap-in, double-click the printer you want to use, select the print job you want to delete, and then press DELETE.
- In the Administrative Tools folder, open the Services snap-in, select Print Spooler, and then click the Restart Service toolbar button.
Note: You can also do this from an elevated Command Prompt window by typing net stop spooler && net start spooler at the command prompt. (To open an elevated Command Prompt window, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.)
In some instances, you might receive Error 1068 â€“ "The dependency service or group failed to start" â€“ when attempting to start the Print Spooler. This can happen if the Print Spooler service relies on other services that are not running. To resolve this issue, use the following procedure.
To verify or change the Startup setting for individual services (dependencies):
- In the Services snap-in, right-click Print Spooler and then click Properties.
- Click the Dependencies tab. The first box lists all of the system services that must be running for print spooler to start. These services are the dependencies.
- Make a note of each service, click OK, and then start each service that the Print Spooler service depends on, if the service is not already started. If a particular service was not started, right-click it, click Properties, and then confirm that the Startup type is set to Automatic.
Reinstall the printer driver
To reinstall the printer driver:
In the Administrative Tools folder, open the **Print Management **snap-in with administrative permissions, right-click the appropriate print server, and then click Server Properties.
Alternatively, open the Printers folder, right-click a blank area, click Run as administrator, and then click Server Properties.
Click the Drivers tab, select the driver you want to reinstall, and then click Reinstall.
After Windows finishes reinstalling the driver, print the document again.
Install an updated printer driver
Obtain an updated printer driver (from the printer vendor) that displays the Designed for Windows logo, install it on the client computer by following the instructions provided with the printer driver, and then print the document again.
To verify that the print server is functioning properly, retry printing and then inspect the printed document to confirm that it printed correctly.
Note: If the print server logs spooler information events, Windows logs Print Spooler Event 10 after each successful printing operation.