Fix Print Spooler V2.0
Líbera Oehlenschlage
I have a few printers set up on a print server. When some of my users try to print, the first print job seems to go through fine. After that, trying to send another print job to a printer completely locks up the application they are printing from, and the print job is never completed.
I've tried restarting the print spooler, cleaning out the spool files under system32\spool\printers, removing and adding the printer again, nothing seems to allow the user to print, until they do a hard reboot. Then we repeat the process again, first print works, nothing after that.
The print job 22 was sent through the print processor hpcpp140 on printer Office Printer, driver HP LaserJet Pro MFP M521 PCL 6, in the isolation mode 1 (0 - loaded in the spooler, 1 - loaded in shared sandbox, 2 - loaded in isolated sandbox). Win32 error code returned by the print processor: 0x103.
The print job 21 was sent through the print processor hpcpp140 on printer Office Printer, driver HP LaserJet Pro MFP M521 PCL 6, in the isolation mode 1 (0 - loaded in the spooler, 1 - loaded in shared sandbox, 2 - loaded in isolated sandbox). Win32 error code returned by the print processor: 0x0.
I believe the issue was I didn't remove the printer and the drivers from the clients before removing the device off the server. I removed the deployed printer from the GPO through Print Management, completely removed the device from the server, cleaned the drivers, then set the printer back up from scratch using the HP Universal PCL 6 driver. Re-deployed the printer through GPO, everything seems to be working now.
I managed to find and open the log and it displayed a whole list of errors. The error is always the same, saying the document cannot be printed. Try to print again of restart the print spooler. The Win32 error code returned by the print spooler is 2147500037. Unspecified error. (This is not the exact error message but my own translation, as my Windows version is in Dutch instead of English).
You may be right about a recent Windows update having upset things. I was able to print until the update KB3150513 was installed. I uninstalled this update when I realised I could no longer print (without being sure that this update caused the problem), but unfortunately the printer didn't came back alive...
In order to print double sided on a GDI Proofer you will need to use a collect for output action and group by job, sheet or signature. You will also need to configure the Windows spooler to print double sided.
You want to make sure that the collect for output is configured so the group being sent contains a front and back. Depending on how your job plan is designed, the choice can be Job, Sheet (Apogee Impose) or Signature (PJTF, JDF or Template).
This IPP specification extends the IPP Model and Semantics [rfc2911] object model by relaxing the restriction that each attribute value is the same for all pages within a Document. For example, with this extension, page 1 of a job could have a different media than the other pages in the job.
This specification defines the conceptual Job Release, Job Storage, Job Print Policy, Job Proof and Suspend, and Job Proof Print features for IPP, to support printing workflows important to institutional IT environments such as corporate businesses, governments, and universities.
This specification defines the IPP 2.0, 2.1, and 2.2 protocol versions. Each version defines a minimum set of supported IPP extensions to simplify development and interoperability of IPP Client and Printer implementations.
This specification defines new attributes, values, and operations to support features, capabilities, localization, and status information that traditionally could only be provided by vendor- or model-specific drivers.
As network infrastructure has become more complex, the traditional client-server model of printing is no longer sufficient to describe the interactions between the IPP Client and IPP Printer. This document defines an IPP Binding of the Cloud Imaging Model that allows IPP Printers to interface with shared services based in the network infrastructure, i.e., software-defined networks, and/or through Cloud-based solutions to remotely obtain and process Jobs and Documents, and provide state and configuration changes to those services.
This specification defines an IPP binding of the System object, System Control Service, Resource Service, and registration operation as defined in various Semantic Model specifications (PWG 5108.06, PWG 5108.03, and PWG 5109.1).
This document defines standard colorant and media names and naming conventions to be used by other PWG specifications. These lists of names are a superset of the names that are defined in the Printer MIB v2 (RFC 3805) and various Internet Printing Protocol documents
In traditional printing environments, clients rely on font downloads when they are not sure a given character is embedded in the printer. As printing moves to small clients, downloading may not be an option and clients have a need to know what characters are available in a given device.
The primary target of this document is printing using document formats based on XML or HTML (for example, XHTML-Print). It will be less applicable to traditional PDLs (PCL, PostScript, etc.) because they tend to have very format-specific mechanisms for managing character repertoires.
This document describes the concept of a Universal Printer Description Format and the set of schemas it is based on. The schemas describe input for a driver/client to assemble general information about the device and its features, to be used in user interfaces or for printing.
HTML 4 is a powerful language for authoring Web content, but its design does not take into consideration issues pertinent to printers, including the implementation cost (in power, memory, etc.) of the full feature set. Printers have relatively limited resources that cannot generally afford to implement the full feature set of HTML 4.
Because there are many ways to subset HTML, there are many almost identical subsets defined by organizations and companies. Without a common base set of features, developing print applications for a wide range of printers is difficult.
This specification defines a simple raster format to support printing, scanning, and facsimile without printer-specific driver software on resource-limited clients and printers. The format includes support for a set of standard and device color spaces and bit depths, and defines PWG Semantic Model elements and IPP attributes that enable a client to generate or request a supported raster stream.
The Print Service Interface is the set of interfaces and methods that enable a Client, such as a Printer, Mobile Device, Web Portal, or Service, to create a Print Job on a Print Service. The Print Service may be used to resolve and access the information to be printed.
This document is a high level overview of the Semantic Model defined by the PWG. This document briefly describes the semantic elements defined in various PWG documents and PWG documents submitted to the IETF. The Semantic Model also incorporates additions made by other groups addressing print systems. With every semantic element included a reference is provided to the document and section that details the semantic definition.
The Semantic Model contains a high level description of the Actions that operate on the objects and attributes in the model. This document does not describe the mapping of the semantics onto a specific protocol or network environment.
This document defines the usage counters for an Imaging System, such as a network spooler, a printer or a multifunction device, and the services such a system offers. This document does not describe mapping of these semantics to XML Schema, MIB or any protocol. Such mappings may be provided in separate documents.
This specification defines the abstract Web-based Imaging Management Service (WIMS) protocol. This specification defines five operations initiated by a WIMS Agent (embedded in services or devices), largely in support of Schedule-oriented remote management: RegisterForManagement (Agent allows management by an identified WIMS Manager); and UnregisterForManagement (cancel Agent association with a given WIMS Manager); GetSchedule (request a Schedule of planned actions); SendReports (send normal operational message); and SendAlerts (send warning or error exception message). This specification also defines four operations initiated by a WIMS Manager to support more conventional local management: BeginManagement (Manager requests ability to manage an identified Agent); EndManagement (Manager cancels association with Agent); SetSchedule (send a Schedule of planned actions with their timetables); ExecuteAction (execute the single identified action). This specification also defines sets of monitoring, management and administration actions that can be included within a Schedule. Transport bindings for the WIMS protocol are identified in the appendix.
This document defines an abstract PWG Power Management Model for Imaging Systems (Printers, Copiers, Multifunction Devices, etc.) that extends the abstract System and Subunit objects in the PWG Semantic Model.
This document defines the PWG Imaging System Power MIB (for Printers, Copiers, Multifunction Devices, etc.) that extends IETF MIB-II [RFC1213], IETF Host Resources MIB v2 [RFC2790], IETF Printer MIB v2 [RFC3805], IETF Finisher MIB [RFC3806], and PWG Imaging System State and Counter MIB v2 [PWG5106.3].
This document defines the PWG Printer Port Monitor (PPM) MIB v1.0 that supports printer status monitoring, automatic installation of device drivers, and other printing applications. The PPM MIB is entirely free-standing, but it also facilitates use of the IETF Host Resources MIB (RFC1514 / RFC2790) and IETF Printer MIB (RFC1759 / RFC3805) for printer status monitoring.
This document defines a standard format for the COMMAND SET capability in an IEEE 1284 Device ID [IEEE1284], for use: (a) by Imaging Systems (Printers, Copiers, Multifunction Devices, etc.) to encode their supported document formats; and (b) by Imaging Clients (workstations, mobile devices, spoolers, etc.) to decode these Imaging System supported document formats, to enable automatic device driver installation and subsequent Imaging Job submission.
93ddb68554