Customers wishing to use the print drivers included in Windows Server 2012 and 2012R2 have encountered some general issues when using the print driver in conjunction with PaperCut features as discussed below.
1) This operation is not supported. Adding a printer or changing printer settings to use PaperCut TCP/IP Port.
Windows Server 2012R2 will check the Port Monitor software associated with a printer which is configured to use a Type 4 print driver and generate this error. A port monitor is software that moves print data from the print spooler service to the printer. Microsoft provides additional information on MSDN: https://msdn.microsoft.com/en-us/library/windows/desktop/dd162825
When the Port Monitor is not one supplied with the operating system, Windows will prevent changes from occurring and post the above message.
The PaperCut TCP/IP Port monitor is installed during Primary and Secondary server installations on Windows.
This functionality from the operating system will block the PaperCut Hardware Page Count feature when a Type 4 driver is associated with the printer.
The supported configuration for Hardware Page Count is currently to use Type 3 print drivers.
Type 4 print drivers are included in the latest Windows versions, available from Windows Update, and can be downloaded from print vendor web sites.
2) This operation is not supported. When updating the print driver associated with a printer.
This error is generated when changing a shared printer that uses a Type 4 to a Type 3 print driver. The execution of this task requires multiple steps.
- Stop sharing the printer: Uncheck Share this printer
- Update the print driver to the Type 3 version
- Share this printer
3) Using Type 4 print drivers on Virtual and Find Me printers.
Only one driver type may be used in this configuration due to the different data output formats supported by the two driver types. When one Type 4 driver is used, then the Find Me and all real printers must use Type 4 drivers. For instance, redirecting PCL6 data to a print driver that only supports XPS data will result in output errors.
Requirements for Job Redirection is covered here.
4) Printing failures
Printing from Mac and Linux clients will produce a rendering failure to printers using a Type 4 driver, review the Windows Print Service event logs. When there is a rendering error, Windows will capture this failure in the Microsoft-Windows-PrintService/Admin logs under event 372.
Microsoft-Windows-PrintService/Admin Event 372
The document Print Document, owned by USER, failed to print on printer PRINTER. Try to print the document again, or restart the print spooler.
Data type: RAW. Size of the spool file in bytes: 104. Number of bytes printed: 104. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \\machine. Win32 error code returned by the print processor: 2147500037. Unspecified error
Changing to a Type 3 print driver will correct this issue or create a new shared printer using a Type 3 print driver and utilize this printer for users encountering problems.
Categories: Implementation / Deployment, Configuration, Windows
Keywords: Class Driver, type 4, type 3 event 372, event 824, Port Monitor, Hardware page count, sharing