Special considerations with Windows Type 4 print drivers

KB Home   |   Special considerations with Windows Type 4 print drivers

Main.WindowsType4PrintDrivers History

Hide minor edits - Show changes to output

October 09, 2018, at 08:29 PM by Aaron Pouliot - Edited to emphasize using a type 3 driver.
Changed lines 8-9 from:
!!Issues with Type 4 Drivers
to:
Below we've documented some of the shortcomings we've found with Type 4 drivers, some of which are completely unrelated to PaperCut.  At the bottom of this article we explain what limitations PaperCut has with Type 4 drivers.

To make a long story short,  we recommend using Type 3 drivers downloaded from a printer manufacturer's website whenever possible.

!!Limitations with Type 4
Drivers (unrelated to PaperCut)
Changed line 44 from:
!!PaperCut limitations with Type 4 Drivers
to:
!!Limitations with Type 4 Drivers and PaperCut
October 09, 2018, at 08:23 PM by Aaron Pouliot - Reorganized headers for clarity
Changed lines 1-2 from:
(:title Special considerations with Windows Type 4 print drivers. :)
to:
(:title Special considerations with Windows Type 4 print drivers:)
Changed lines 8-13 from:

!!PaperCut Watermarking will not work
Watermarking with PaperCut is only supported with RAW or PostScript spool files, but Type 4 drivers will not render documents in this format, which means that PaperCut is not able to inject a Watermark into the document.  If you intend to use the PaperCut Watermarking feature please make sure that you are using a Type 3 PostScript or PCL driver.


!!Jobs from Linux and [=MacOS=] clients will fail to print
to:
!!Issues with Type 4 Drivers

!!!Jobs
from Linux and [=MacOS=] clients will fail to print
Changed lines 13-14 from:
[@The document Print Document, owned by USER, failed to print on printer PRINTER. Try to print the document again, or restart the print spooler.
to:
-> [@The document Print Document, owned by USER, failed to print on printer PRINTER. Try to print the document again, or restart the print spooler.
Changed line 19 from:
!!"This operation is not supported" error when adding a printer or changing port settings
to:
!!!"This operation is not supported" error when adding a printer or changing port settings
Changed lines 21-22 from:
[[<<]]Attach:NotSupported1.jpg
to:
-> Attach:NotSupported1.jpg
Changed line 30 from:
!!"This operation is not supported" when changing the driver
to:
!!!"This operation is not supported" when changing the driver
Changed lines 32-33 from:
[[<<]]Attach:NotSupported1.jpg
to:
-> Attach:NotSupported1.jpg
Changed lines 40-41 from:

!!Using Type 4 print drivers on Virtual and Find Me printers.
to:
!!PaperCut limitations with Type 4 Drivers

!!!PaperCut Watermarking is not compatible with Type 4 Drivers
Watermarking with PaperCut is only supported with RAW or PostScript spool files, but Type 4 drivers will not render documents in this format, which means that PaperCut is not able to inject a Watermark into the document
.   If you intend to use the PaperCut Watermarking feature please make sure that you are using a Type 3 PostScript or PCL driver.

!!!Find-Me Printing won't work when Type 3 and Type 4 drivers are mixed
Changed line 50 from:
!!Type 4 print drivers and Change Print Job Settings
to:
!!!PaperCut's Change Print Job Settings is not compatible with Type 4 Drivers
July 24, 2018, at 04:59 AM by peterf - Updated with ChPS info for 18.2.1 GA
Changed lines 49-52 from:
to:
!!Type 4 print drivers and Change Print Job Settings
In PaperCut MF 18.2, we introduced the ability for users to Change Print Job Settings at the device. As one example, this allows users of supported copier devices to change their color job to a grayscale one at the point of release. Changes to job settings via this feature which require the spool file to be modified will not work if a Type 4 print driver is in use. If you intend to enable the Change Print Job Settings feature, a Type 3 print driver should be used on all the relevant print queues.

Changed line 57 from:
[-Keywords: Class Driver, type 4, type 3 event 372, event 824, Port Monitor, Hardware page count, sharing, disappearing jobs, disappear -]
to:
[-Keywords: Class Driver, type 4, type 3 event 372, event 824, Port Monitor, Hardware page count, sharing, disappearing jobs, disappear, change print job settings -]
April 24, 2018, at 03:23 PM by Aaron Pouliot -
Changed line 6 from:
A simple way to check the driver type is to open the Print Management console, open Printers, then look at the column named "Driver Type". This will say whether each printer is using a Type 3 or Type 4 driver.  A Type 4 driver is usually bundled with the operating system or is downloaded from Windows update, whereas Type 3 drivers are often downloaded from the printer manufacturer's website.
to:
A simple way to check the driver type is to open the Print Management console, open Drivers, then look at the column named "Driver Type". This will say whether a particular driver is a Type 3 or Type 4 driver.  A Type 4 driver is usually bundled with the operating system or is downloaded from Windows update, whereas Type 3 drivers are often downloaded from the printer manufacturer's website.
March 16, 2018, at 06:53 PM by Aaron Pouliot -
Added line 8:
Added line 12:
Changed lines 22-23 from:
!!"This operation is not supported" Error
This problem is not related to PaperCut, but can happen in two different scenarios detailed below.
to:
!!"This operation is not supported" error when adding a printer or changing port settings
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
.
Changed lines 26-32 from:
!!!When adding a printer or changing printer port settings
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.

This can happen also happen with the PaperCut TCP/IP Port, because this Port Monitor is installed during the Primary and Secondary server installations on Windows.
to:
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. This can happen also happen with the PaperCut TCP/IP Port, because this Port Monitor is installed during the Primary and Secondary server installations on Windows.
Changed lines 32-35 from:
!!!When updating the print driver associated with a printer.
This
error can also be generated when attempting to change a shared printer that uses a Type 4 to a Type 3 print driver.   

Fortunately
there is a workaround:
to:

!!"This operation is not supported" when changing the driver
This
error will happen without PaperCut and can be seen when attempting to change a Type 4 to a Type 3 print driver on a shared printer.
[[<<]]Attach:NotSupported1.jpg

Fortunately
there is an easy workaround:
Added line 42:
March 16, 2018, at 06:39 PM by Aaron Pouliot -
Changed line 6 from:
A simple way to check the driver type is to open the Print Management console, open Printers, then look at the column named "Driver Type". This will say whether each printer is using a Type 3 or Type 4 driver.
to:
A simple way to check the driver type is to open the Print Management console, open Printers, then look at the column named "Driver Type". This will say whether each printer is using a Type 3 or Type 4 driver.  A Type 4 driver is usually bundled with the operating system or is downloaded from Windows update, whereas Type 3 drivers are often downloaded from the printer manufacturer's website.
March 16, 2018, at 06:38 PM by Aaron Pouliot - Edited for clarity.
Changed lines 3-4 from:
Type 4 drivers were introduced by Microsoft with Windows Server 2012 and were intended to replace the default drivers bundled with the Windows operating system.  However, customers wishing to use these drivers have encountered some general issues when using the print driver in conjunction with PaperCut features as discussed below.
to:
!!What is a Type 4 Driver?
Type 4 drivers were introduced by Microsoft with Windows Server 2012 and were intended to replace
the default drivers bundled with the Windows operating system.  Unfortunately, there are a few issues customers have reported when using these drivers, and a couple problems when using these drivers in conjunction with specific PaperCut features. Each one of these situations is discussed below.

A simple way to check the driver type is to open the Print Management console, open Printers, then look at the column named "Driver Type". This will say whether each printer is using a Type 3 or Type 4 driver.

Changed lines 9-10 from:
Watermarking with PaperCut is only supported with RAW or PostScript spool files. Type 4 drivers will not render documents in this format, and PaperCut will not be able to inject the Watermark into the document.  Please make sure that you are using a Type 3 PostScript or PCL driver if you intend to use the PaperCut Watermarking feature.
to:
Watermarking with PaperCut is only supported with RAW or PostScript spool files, but Type 4 drivers will not render documents in this format, which means that PaperCut is not able to inject a Watermark into the document.   If you intend to use the PaperCut Watermarking feature please make sure that you are using a Type 3 PostScript or PCL driver.
Changed lines 12-13 from:
This issue will occur even without PaperCut, but printing from Mac and Linux clients will produce a rendering failure to printers using a Type 4 driver which can be found in the Windows Print Service event logs. From the user's perspective it will seem as if their print jobs disappeared. When there is a rendering error, Windows will capture this failure in the [=Microsoft-Windows-PrintService/Admin logs under event 372.=] 
to:
This issue will occur even without PaperCut, but printing from Mac and Linux clients will produce a rendering failure to printers using a Type 4 driver. From the user's perspective it will seem as if their print jobs disappeared. When this occurs, Windows will capture this failure in the Windows Print Service event logs, which can be found in Event Viewer on the print server under "Applications and Services Logs" > "Microsoft" > "Windows" > "[=PrintService=]" > "Admin" log as event 372. 
Changed lines 18-20 from:
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.

to:
If you encounter this problem, simply switching to a Type 3 print driver will correct this issue.
Changed lines 29-37 from:
This can happen also happen with the PaperCut TCP/IP Port, because this port monitor is installed during the 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.
to:
This can happen also happen with the PaperCut TCP/IP Port, because this Port Monitor is installed during the Primary and Secondary server installations on Windows.

This means that Type 4 drivers cannot be used in tandem with [[https://www.papercut.com/products/ng/manual/applicationserver/topics/printer-hwcheck.html|PaperCut Hardware Page Checks]] because it this type of driver will not work with 3rd party Port Monitors. If you intend to use Hardware Page Checks, please use a Type 3 driver downloaded from the manufacturer's web site.
Changed lines 37-40 from:
# Stop sharing the printer: Uncheck Share this printer
# Update
the print driver to the Type 3 version
# Share this printer
to:
# Right Click on the printer and choose Properties.
# Click on
the Sharing tab and uncheck "Share this printer".
# Switch to the Advanced tab and change the print driver to a Type 3 version.
# Return to the Sharing tab and recheck "Share this
printer".
March 15, 2018, at 11:02 PM by Aaron Pouliot -
Changed lines 11-16 from:
[=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.@]
to:
[@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.@]
Changed line 22 from:
!!!Adding a printer or changing printer settings to use PaperCut TCP/IP Port
to:
!!!When adding a printer or changing printer port settings
Changed line 27 from:
The PaperCut TCP/IP Port monitor is installed during Primary and Secondary server installations on Windows.
to:
This can happen also happen with the PaperCut TCP/IP Port, because this port monitor is installed during the Primary and Secondary server installations on Windows.
March 15, 2018, at 10:40 PM by Aaron Pouliot -
Changed lines 3-4 from:
Type 4 drivers were introduced by Microsoft with Windows Server 2012 that were intended to replace the default drivers bundled with the Windows operating system.  However, 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.
to:
Type 4 drivers were introduced by Microsoft with Windows Server 2012 and were intended to replace the default drivers bundled with the Windows operating system.  However, customers wishing to use these drivers have encountered some general issues when using the print driver in conjunction with PaperCut features as discussed below.
Changed lines 8-10 from:
!!Jobs from Linux and MacOS clients will fail to print
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. From a user point of view this can also manifest itself as disappearing print jobs. When there is a rendering error, Windows will capture this failure in the [=Microsoft-Windows-PrintService/Admin logs under event 372.=] 
to:
!!Jobs from Linux and [=MacOS=] clients will fail to print
This issue will occur even without PaperCut, but printing from Mac and Linux clients will produce a rendering failure to printers using a Type 4 driver which can be found in the Windows Print Service event logs. From the user's perspective it will seem as if their print jobs disappeared. When there is a rendering error, Windows will capture this failure in the [=Microsoft-Windows-PrintService/Admin logs under event 372.=] 
Changed lines 14-15 from:
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
to:

[@
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.@]
Changed lines 21-23 from:
!!!Adding a printer or changing printer settings to use PaperCut TCP/IP Port.
[[<<]]Attach:NotSupported1.jpg
to:
This problem is not related to PaperCut, but can happen in two different scenarios detailed below. 
[[<<]]Attach:NotSupported1.jpg 

!!!Adding a printer or changing printer settings to use PaperCut TCP/IP Port
Changed lines 39-44 from:

[[<<]]Attach:NotSupported1.jpg


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. 
to:
This error can also be generated when attempting to change a shared printer that uses a Type 4 to a Type 3 print driver.   

Fortunately there is a workaround:
Deleted line 42:
Deleted line 43:
March 15, 2018, at 10:33 PM by Aaron Pouliot - Added short intro
Changed lines 3-6 from:

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.

to:
Type 4 drivers were introduced by Microsoft with Windows Server 2012 that were intended to replace the default drivers bundled with the Windows operating system.  However, 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.

!!PaperCut Watermarking will not work
Watermarking with PaperCut is only supported with RAW or PostScript spool files.  Type 4 drivers will not render documents in this format, and PaperCut will not be able to inject the Watermark into the document.  Please make sure that you are using a Type 3 PostScript or PCL driver if you intend to use the PaperCut Watermarking feature.

!!Jobs from Linux and MacOS clients will fail to print
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. From a user point of view this can also manifest itself as disappearing print jobs. 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
.

Deleted lines 24-25:

Changed lines 50-52 from:

!!3) Using Type 4 print drivers on Virtual and Find Me printers.
to:
!!Using Type 4 print drivers on Virtual and Find Me printers.
Deleted lines 54-68:

!!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. From a user point of view this can also manifest itself as disappearing print jobs. 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.

!!4) PaperCut Watermarking will not work
Watermarking with PaperCut is only supported with RAW or PostScript spool files.  Type 4 drivers will not render documents in this format, and PaperCut will not be able to inject the Watermark into the document.  Please make sure that you are using a Type 3 PostScript or PCL driver if you intend to use the PaperCut Watermarking feature.
March 15, 2018, at 10:27 PM by Aaron Pouliot -
Changed lines 7-8 from:
!!!'''1) This operation is not supported. ''' Adding a printer or changing printer settings to use PaperCut TCP/IP Port.
to:
!!"This operation is not supported" Error
!!!
Adding a printer or changing printer settings to use PaperCut TCP/IP Port.
Changed lines 26-32 from:





!!!'''2) This operation is not supported. '''  When updating the print driver associated with a printer.
to:
!!!When updating the print driver associated with a printer.
Changed lines 41-42 from:
!!!'''3) Using Type 4 print drivers on Virtual and Find Me printers.   '''
to:
!!3) Using Type 4 print drivers on Virtual and Find Me printers.
Changed lines 48-50 from:

!!!'''4) Printing failures'''
to:
!!4) Printing failures
Changed line 60 from:
!!!'''4) PaperCut Watermarking will not work'''
to:
!!4) PaperCut Watermarking will not work
March 15, 2018, at 10:25 PM by Aaron Pouliot - Added note about Watermarking with Type 4 drivers
Added lines 64-66:

!!!'''4) PaperCut Watermarking will not work'''
Watermarking with PaperCut is only supported with RAW or PostScript spool files.  Type 4 drivers will not render documents in this format, and PaperCut will not be able to inject the Watermark into the document.  Please make sure that you are using a Type 3 PostScript or PCL driver if you intend to use the PaperCut Watermarking feature.
March 15, 2018, at 05:56 PM by timg - Added disappearing job keyword.
Changed lines 55-56 from:
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.=] 
to:
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. From a user point of view this can also manifest itself as disappearing print jobs. When there is a rendering error, Windows will capture this failure in the [=Microsoft-Windows-PrintService/Admin logs under event 372.=] 
Changed lines 69-70 from:
[-Keywords: Class Driver, type 4, type 3 event 372, event 824, Port Monitor, Hardware page count, sharing -]
to:
[-Keywords: Class Driver, type 4, type 3 event 372, event 824, Port Monitor, Hardware page count, sharing, disappearing jobs, disappear -]
July 13, 2015, at 09:39 PM by Alan Morris -
Changed line 10 from:
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(v=vs.85).aspx
to:
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
July 09, 2015, at 09:29 PM by Alan Morris -
Changed lines 55-57 from:
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
to:
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=]
July 09, 2015, at 09:25 PM by Alan Morris -
Changed lines 55-57 from:
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
to:
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
July 09, 2015, at 09:15 PM by Alan Morris -
Changed lines 7-8 from:
1) This operation is not supported.  Adding a printer or changing printer settings to use PaperCut TCP/IP Port.
[[<<]]Attach:
to:
!!!'''1) This operation is not supported. ''' Adding a printer or changing printer settings to use PaperCut TCP/IP Port.
[[<<]]Attach:NotSupported1.jpg
Changed lines 30-33 from:
2) This operation is not supported.  When updating the print driver associated with a printer.
[[<<]]Attach:

to:
!!!'''2) This operation is not supported. '''  When updating the print driver associated with a printer.

[[<<]]Attach:NotSupported1.jpg

Changed lines 37-46 from:
1.Stop sharing the printer: Uncheck Share this printer

2.Update the print driver to the Type 3 version

3.Share this printer



3) Using Type 4 print drivers on Virtual and Find Me printers. 
to:
# 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.  '''
Changed lines 53-54 from:
4) Printing failures
to:
!!!'''4) Printing failures'''
Deleted lines 64-65:

If you have any issues or require additional assistance, please email @@support@papercut.com@@
July 09, 2015, at 12:20 AM by Alan Morris - initial edit
Added lines 1-70:
(:title Special considerations with Windows Type 4 print drivers. :)


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.
[[<<]]Attach:
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(v=vs.85).aspx



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.
[[<<]]Attach:


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. 

1.Stop sharing the printer: Uncheck Share this printer

2.Update the print driver to the Type 3 version

3.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 [[https://www.papercut.com/products/ng/manual/ch-find-me-printing-and-load-balancing-requirements.html|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.


If you have any issues or require additional assistance, please email @@support@papercut.com@@
----
''Categories:'' [[Category.Implementation|+]], [[Category.Configuration|+]], [[Category.Windows|+]]
----

[-Keywords: Class Driver, type 4, type 3 event 372, event 824, Port Monitor, Hardware page count, sharing -]

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on October 09, 2018, at 08:29 PM
Printable View   |   Article History   |   Edit Article