Event ID 54 — Print Job Status

Event ID 54 — Print Job Status

Updated: November 30, 2007

Applies To: Windows Server 2008

A print job is a file that contains data to be printed.

Event Details

Product: Windows Operating System
ID: 54
Source: Microsoft-Windows-PrintSpooler
Version: 6.0
Symbolic Name: MSG_BAD_JOB
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.

Resolve
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:

  1. 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.
  2. 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): 

  1. In the Services snap-in, right-click Print Spooler and then click Properties.
  2. 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.
  3. 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:

  1. 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.

  2. Click the Drivers tab, select the driver you want to reinstall, and then click Reinstall.
  3. 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.

Verify

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.

Related Management Information

Print Job Status

Printing Infrastructure

Related:

Document %1 was corrupted and has been deleted. The associated driver is: %2.

Details
Product: Windows Operating System
Event ID: 54
Source: Print
Version: 5.0
Component: Application Event Log
Symbolic Name: MSG_BAD_JOB
Message: Document %1 was corrupted and has been deleted. The associated driver is: %2.
   
Explanation

The print job caused the print spooler to stop more than once, so the print spooler deleted the job and will not try to print it again.

To force spooling with the RAW data type

  1. In Control Panel, open Printers and Faxes.
  2. Right-click the appropriate printer and then click Properties.
  3. On the Advanced tab, clear the Enable advanced printing features check box.
   
User Action

Try updating the printer driver with a newer version from the vendor if one is available.

If updating the driver does not work, try forcing the print queue to spool with the RAW (ready to print) data type.

To force spooling with the RAW data type

  1. In Control Panel, open Printers.
  2. Right-click the appropriate printer and then click Properties.
  3. On the Advanced tab, clear the Enable advanced printing features check box.

Related:

NLB Cluster %2 %1: Host %3 MAY be a Windows 2000 or NT 4.0 host participating in a cluster utilizing virtual cluster support. Virtual Clusters are only supported in a homogeneous Windows Server 2003 cluster. %4

Details
Product: Windows Operating System
Event ID: 54
Source: WLBS
Version: 5.2
Symbolic Name: MSG_WARN_VIRTUAL_CLUSTERS
Message: NLB Cluster %2 %1: Host %3 MAY be a Windows 2000 or NT 4.0 host participating in a cluster utilizing virtual cluster support. Virtual Clusters are only supported in a homogeneous Windows Server 2003 cluster. %4
   
Explanation

Virtual clusters, which are Network Load Balancing (NLB) clusters where specific port rules are assigned to specific Virtual IP addresses, are configured on this host, but at least one host in this cluster has one or more port rules that are not valid and appear to be missing the Virtual IP address specification. Therefore, either:

  • A Windows 2000 or Windows NT 4.0 host exists in the cluster. Virtual clusters require a cluster containing only hosts running products in the Windows Server 2003 family, or
  • A Windows Server 2003 host with an incorrectly configured port rule exists in the cluster.

The cluster will not converge until the problem is corrected.

   
User Action

If there is a Windows 2000 or Windows NT 4.0 host in the cluster, either remove it or stop using virtual clusters on the Windows Server 2003 hosts.

If the cluster contains only Windows Server 2003 hosts, then use NLB Manager to check the port rule configuration of all hosts to ensure that all hosts have compatible port rule configurations.

For more information about virtual clusters and port rules, see NLB in Help and Support.

Related:

Failed to retrieve the Active Directory system configuration session.Exception message:”%1″.

Details
Product: Exchange
Event ID: 54
Source: MSExchange OWA
Version: 8.0
Symbolic Name: ADSystemConfigurationSession
Message: Failed to retrieve the Active Directory system configuration session.Exception message:”%1″.
   
Explanation

This Error event indicates that an exception occurred while the Active Directory System Configuration Session was being retrieved. The Active Directory directory service may be unavailable or corrupted.

   
User Action

To resolve this error, do one or more of the following:

  • Monitor the event logs to see whether the error resolves itself. If it does not resolve itself, check Active Directory for possible problems.

  • If you have difficulty resolving the issue, contact Microsoft Customer Support. For information about how to contact support, visit Microsoft Help and Support.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related: