Microsoft-Windows-PrintSpooler

Message #

Document {param1}; {param2} owned by {param3} was printed on {param4} through port {param5}.  Size in bytes: {param6}. Pages printed: {param7}. No user action is required.To stop logging information events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler information events check box.

Fields #

Message #

Document {param1}; {param2} owned by {param3} was paused on {param4}. This document will not print until the document owner resumes the print job. No user action is required.To stop logging information events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler information events check box.

Fields #

Message #

Document {param1}; {param2} owned by {param3} was resumed on {param4}. No user action is required.To stop logging information events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler information events check box.

Fields #

Message #

Document {param1}; {param2} owned by {param3} was deleted on {param4}. No user action is required.To stop logging information events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler information events check box.

Fields #

Message #

An administrator moved document {param1}; {param2} owned by {param3} to position {param4} on {param5}. This changes when the document will print. No user action is required.To stop logging information events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler information events check box.

Fields #

Message #

Form {param1} was added. No user action is required.To stop logging information events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler information events check box.

Fields #

Message #

Form {param1} was removed. No user action is required.To stop logging information events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler information events check box.

Fields #

Message #

The printer was successfully published to the Active Directory directory service. The print queue {param1} was successfully created in container {param2}. No user action is required.To stop logging information events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler information events check box.

Fields #

Message #

The printer was successfully removed from the Active Directory directory service. Print queue {param1} was successfully deleted from container {param2}. The printer can no longer be located by searching Active Directory. No user action is required.To stop logging information events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler information events check box.

Fields #

Message #

Print queue {param1} was successfully updated in the Active Directory directory service container {param2}. No user action is required.To stop logging information events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler information events check box.

Fields #

Message #

Printer {param1} was successfully removed from the Active Directory directory service. The printer can no longer be located by searching Active Directory. No user action is required.To stop logging information events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler information events check box.

Fields #

Message #

The print spooler removed print queue {param1} from the Active Directory directory service because it does not have a Universal Naming Convention (UNC) name or server name listed. No user action is required.To stop logging information events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler information events check box.

Fields #

Message #

The print spooler was unable to connect to print queue {param1} based on the information published in the Active Directory. Error {param2}. No user action is required.  If this print queue continues to be unreachable it may be removed from Active Directory. To stop logging information events for the print spooler; clear the Log spooler information events check box in Server properties.

Fields #

Message #

The print spooler removed print queue {param1} from the Active Directory directory service. No user action is required.To stop logging information events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler information events check box.

Fields #

Message #

The print spooler removed print queue {param1} from the Active Directory directory service because it is a duplicate of another print queue. No user action is required.To stop logging information events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler information events check box.

Fields #

Message #

The print spooler removed print queue {param1} from the Active Directory directory service. No user action is required.To stop logging information events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler information events check box.

Fields #

Message #

The priority of document {param1}; {param2} owned by {param3} was changed to {param4} on {param5}. Windows prints the document with the highest priority number before other print jobs with lower priority numbers. Documents that are currently printing are unaffected by changes in priority. No user action is required.To stop logging information events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler information events check box.

Fields #

Message #

Printer {param1} was created. No user action is required.To stop logging information events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler information events check box.

Fields #

Message #

Printer {param1} was deleted; and users will no longer be able to print to this printer. No user action is required.To stop logging information events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler information events check box.

Fields #

Message #

Printer {param1} will be deleted. No user action is required.To stop logging warning events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler warning events check box.

Fields #

Message #

Printer {param1} was paused. No user action is required.To stop logging warning events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler warning events check box.

Fields #

Message #

Printer {param1} was resumed. No user action is required.To stop logging warning events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler warning events check box.

Fields #

Message #

The jobs in the print queue for printer {param1} were deleted. No user action is required.To stop logging warning events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler warning events check box.

Fields #

Message #

Settings for printer {param1} were changed. No user action is required.To stop logging warning events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler warning events check box.

Fields #

Message #

Document {param1}; {param2} owned by {param3} timed out while printing on {param4}. The spooler waited for {param5} milliseconds and no data was received.

Fields #

Message #

Printer driver {param1} for {param2} {param3} was added or updated. Files:- {param4}. No user action is required.To stop logging warning events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler warning events check box.

Fields #

Message #

Printer driver {param1} was deleted. No user action is required.To stop logging warning events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler warning events check box.

Fields #

Message #

Printer {param1} failed to initialize because none of its ports ({param2}) could be found. This can occur if the ports were deleted or the port information is invalid.

Fields #

Message #

File(s) {param1} associated with printer {param2} were added or updated. No user action is required.To stop logging warning events for the print spooler; in Control Panel; open Printers; right-click a blank area of the window; click Run as Administrator; click Server Properties; click the Advanced tab; and then clear the Log spooler warning events check box.

Fields #

Message #

While attempting to publish the printer to the Active Directory directory service; Windows failed to publish property {param1} at {param2}.  Error: {param3}

Fields #

Message #

The print queue could not be found on domain {param1}.  It may have been deleted from the Active Directory directory service. Windows will attempt to republish the print queue.  Error: {param2}

Fields #

Message #

Updating the color profile failed for printer {param1} with Win32 error code {param2}. The colors printed may not be correctly matched to the colors in the document being printed.

Fields #

Message #

The print spooler failed to share printer {param2} with shared resource name {param3}. Error {param1}. The printer cannot be used by others on the network.

Fields #

Message #

Failed to upgrade printer settings for printer {param1} driver {param2}. Error: {param3}. The device settings for the printer are set to those configured by the manufacturer.

Fields #

Message #

Printer {param1} failed to initialize because a suitable {param2} driver could not be found. The new printer settings that you specified have not taken effect. Install or reinstall the printer driver. You might need to contact the vendor for an updated driver.

Fields #

Message #

While attempting to publish the printer to the Active Directory directory service; the print spooler could not create or update the print queue because Windows failed to bind to container: {param1}.  Error: {param2}. The printer is not published in Active Directory and cannot be located by searching Active Directory.

Fields #

Message #

While attempting to publish the printer to the Active Directory directory service; Windows failed to write an access control list (ACL) on directory service object {param1}.  Error: {param2}

Fields #

Message #

While attempting to remove the printer from the Active Directory directory service; Windows failed to delete print queue {param1} at {param2}.  Error: {param3}

Fields #

Message #

While attempting to publish the printer to the Active Directory directory service; the print spooler could not create or update the print queue under container {param1}.  Error: {param2}. The printer is not published in Active Directory and cannot be located by searching Active Directory.

Fields #

Message #

While attempting to publish the printer to the Active Directory directory service; the print spooler could not create print queue {param1} under container {param2} because Mandatory properties could not be set.  Error: {param3}. The printer is not published in Active Directory and cannot be located by searching Active Directory.

Fields #

Message #

While attempting to publish the printer to the Active Directory directory service; the print spooler could not find the appropriate print queue container because the primary domain query failed. Error: {param1}. This can occur if Domain Name System (DNS) cannot resolve the domain controller IP address; or if the domain controller or directory service is not functioning correctly. The printer is not published in Active Directory and cannot be located by searching Active Directory.

Fields #

Message #

While attempting to publish the printer to the Active Directory directory service; the print spooler could not find the appropriate print queue container because the Domain Name System (DNS) domain name could not be retrieved. Error: {param1}. This can occur if DNS cannot resolve the domain controller IP address; or if the domain controller or directory service is not functioning correctly. The printer is not published in Active Directory and cannot be located by searching Active Directory.

Fields #

Message #

While attempting to publish the printer to the Active Directory directory service; the print spooler could not find the appropriate print queue container because the binding to domain {param1} failed.  Error: {param2}. The printer is not published in Active Directory and cannot be located by searching Active Directory.

Fields #

Message #

While attempting to publish the printer to the Active Directory directory service; the print spooler could not find the appropriate print queue container on domain {param1}.  Error: {param2}. The printer is not published in Active Directory and cannot be located by searching Active Directory.

Fields #

Message #

While attempting to publish the printer to the Active Directory directory service; the print spooler failed to create or update print queue {param1} in container {param2}.  Error: {param3}. The printer is not published in Active Directory and cannot be located by searching Active Directory.

Fields #

Message #

While attempting to remove the printer from the Active Directory directory service; the print spooler failed to delete print queue {param1} from container {param2}.  Error: {param3}

Fields #

Message #

While attempting to publish the printer to the Active Directory directory service; the print spooler could not find the print queue container because the directory service is unreachable. The printer is not published in Active Directory and cannot be located by searching Active Directory.

Message #

The print spooler could not find the print queue container because the Domain Name System (DNS) server name could not be retrieved.  Error: {param1}. This might be because DNS cannot resolve the server IP address; or because the domain controller or directory service is not functioning correctly. The printer is not published in the Active Directory directory service and cannot be located by searching Active Directory.

Fields #

Message #

The document failed to print because of a Graphical Device Interface (GDI) error or a driver error in rendering the print job. Try printing the document again.

Message #

Print queue {param1} could not be deleted (pruned) from the Active Directory directory service.  Error: {param2}. The spooler will periodically try to remove the entry until it is successful. Continued failures may indicate an Active Directory problem; a basic network problem; or a communication problem between the domain controller and the print server.

Fields #

Message #

This version of {param1} is incompatible with this version of Windows. Please obtain and install a new version of the driver from the manufacturer (if available); or choose an alternate driver that works with this print device.

Fields #

Message #

The print spooler failed to create a symbolic link between HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Control\\Print\\Printers and HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Print\\Printers. Error {param1}. This only affects older applications; but is probably a sign that the system itself is in a poor condition or that the print spooler does not have the proper registry permissions.

Fields #

Message #

Document {param1} failed to print and was deleted because of corruption in the spooled file. The associated driver is: {param2}. Try printing the document again.

Fields #

Message #

The attempt for {param1} to use a Windows NT 4.0 (kernel mode) driver failed because this version of Windows does not support Windows NT 4.0 printer drivers. Please obtain and install a new version of the driver from the manufacturer (if available); or choose an alternate driver that works with this print device.

Fields #

Message #

{param1} initialization failed at {param2}. Error: {param3}. This can occur because of system instability or a lack of system resources.

Fields #

Message #

The print spooler was not able to add print queue {param1} under container {param2} in the Active Directory directory service because the cluster access control entry (ACE) could not be added to the print queue security descriptor.  Error: {param3}. The printer is not published in Active Directory and cannot be located by searching Active Directory.

Fields #

Message #

Failed to install or update driver {param1} on cluster spooler resource {param2}. Win32 error: {param3}. The printer driver is different from the driver in use on other computers (nodes) in the cluster. This can occur because of a transient failure in replication between nodes; or if the nodes are running Windows 2000 (which does not automatically replicate drivers).

Fields #

Message #

The document {param1} owned by {param2} failed to print on printer {param3}. Win32 error code returned by the print processor: {param4}. {param5}

Fields #

Message #

This version of Windows does not support Windows NT 4.0 (kernel mode) printer drivers and cannot accept the {param2} driver from the remote server {param1}. Please obtain and install a new version of the driver from the manufacturer (if available); or choose an alternate driver that works with this print device.

Fields #

Message #

The attempt to install printer {param1} into an offline operating system image failed with Win32 error code {param2}. This can occur if the printer driver requires user input or displays a user interface (UI) during installation.

Fields #

Message #

Printer {param1} failed to initialize its ports. Win32 error: {param2}. This error usually occurs because of a problem with the port monitor. Try recreating the port using a standard TCP/IP printer port; if possible. This problem does not affect other printers.

Fields #

Message #

The print spooler failed to cache print connection {param1}. This can occur because there are insufficient system resources. No user action is required.

Fields #

Message #

The print spooler {param1} failed to start. To determine the cause of this error; examine the preceding events in the Event Log.

Fields #

Message #

Windows could not load print processor {param1} because EnumDatatypes did not return any data. Module: {param2}. Please obtain and install a new version of the driver from the manufacturer (if available); or choose an alternate driver that works with this print device.

Fields #

Message #

Windows could not load print processor {param1} because EnumDatatypes failed. Error code {param2}. Module: {param3}. Please obtain and install a new version of the driver from the manufacturer (if available); or choose an alternate driver that works with this print device.

Fields #

Message #

The print server security descriptor for {param1} is invalid. The default print server security descriptor will be used.

Fields #

Message #

Windows could not initialize printer {param1} because the print processor {param2} could not be found. Please obtain and install a new version of the driver from the manufacturer (if available); or choose an alternate driver that works with this print device.

Fields #

Message #

The print spooler failed to verify printer driver package {param1} for environment {param2}. Win32 system error code {param3}. This can occur after an operating system upgrade or because of data loss on the hard drive. The print spooler will try to regenerate the driver information from the driver store; which is where drivers are saved before they are installed. No user action is required.

Fields #

Message #

The print spooler failed to verify printer driver package for environment {param1}. Win32 system error code {param2}. This can occur because of insufficient memory or other system failures. No user action is required.

Fields #

Message #

The print spooler failed to regenerate the printer driver information for driver {param1} for environment {param2}. Win32 system error code {param3}. This can occur after an operating system upgrade or because of data loss on the hard drive.

Fields #

Message #

The print spooler failed to unshare printer {param2} which is shared as {param3}. Error {param1}.

Fields #

Message #

The document {param1}; owned by {param2}; failed to print on printer {param3}. Try to print the document again; or restart the print spooler. Data type: {param4}. Size of the spool file in bytes: {param5}. Number of bytes printed: {param6}. Total number of pages in the document: {param7}. Number of pages printed: {param8}. Client computer: {param9}. Win32 error code returned by the print processor: {param1}0. {param1}1

Fields #

Message #

The spooler has detected that a component has an unusually large number of open Graphical Device Interface (GDI) objects. As a result; some enhanced metafile (EMF) print jobs might not print until the spooler is restarted.