Troubleshooting Global Print Driver Issues

KB Home   |   Troubleshooting Global Print Driver Issues

Main.TroubleshootingGlobalPrintDriver History

Hide minor edits - Show changes to output

March 27, 2019, at 04:40 AM by Mel Zouzoulas - Updated to mention the support web form
Changed line 19 from:
# Once both the spool files are captured, please email us at [[mailto:support@papercut.com|support@papercut.com]] with the following information:
to:
# Once both the spool files are captured, please log a ticket via (http://support.papercut.com) with the following information:
October 29, 2014, at 12:25 AM by 203.222.91.204 -
Changed lines 26-29 from:
!!Subheading


to:
!!More information


October 29, 2014, at 12:24 AM by 203.222.91.204 -
Added lines 26-32:
!!Subheading



* [[https://www.papercut.com/products/ng/manual/ch-global-print-driver.html|Manual section on Global Print Driver]]
* [[https://www.papercut.com/tour/global-print-driver/|Global Print Driver Tour Page]]

Changed line 19 from:
# Once both the spool files are captured, please email support at [[mailto:support@papercut.com|support@papercut.com]] with the following information:
to:
# Once both the spool files are captured, please email us at [[mailto:support@papercut.com|support@papercut.com]] with the following information:
October 06, 2014, at 03:39 AM by 203.222.91.204 - tweaks
Changed lines 9-10 from:
For example: a color print job sent by the user prints as grayscale when using the PaperCut Global Print Driver.
to:
For example: you observe that a color print job sent by the user prints as grayscale when using the PaperCut Global Print Driver.
Changed lines 17-18 from:
#Print the same document to the target print queue set up with the vendor specific driver and capture it's spool file.
to:
#Print the same document to the target print queue set up with the vendor specific driver and capture it's spool file. Be sure to select the same print options as used for step 1.
Changed lines 13-14 from:
Please follow the following steps:
to:
Please follow the steps below:
Changed lines 11-12 from:
You will need to capture two Windows spool files to help us fix the issue. The steps to capture a spool file are given [[https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile| here]].
to:
To resolve the issue, you will need to capture two Windows spool files. The steps to capture a spool file are given [[https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile| here]].
Changed lines 15-18 from:
#Send a job to the printer set up with the Global Print Driver. Capture it's spool file.

#Print the same document to the target queue set up with the vendor specific driver and capture it's spool file.
to:
#Send a job to the queue set up with the Global Print Driver. Capture it's spool file.

#Print the same document to the target print queue set up with the vendor specific driver and capture it's spool file.
Changed lines 11-12 from:
You will need to capture Windows two spool files to help us fix the issue. The steps to capture a spool file are given [[https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile| here]].
to:
You will need to capture two Windows spool files to help us fix the issue. The steps to capture a spool file are given [[https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile| here]].
Changed lines 11-17 from:
To solve the issue please follow the steps below:

#Capture a Windows Spool file by sending a job
to the printer set up with the Global Print Driver. The steps to capture a spool file are given [[https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile| here]].

#The vendor specific Postscript driver spool file also needs to be captured
. Please follow the steps to capture this spool file [[https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile| here]].

# Once both
spool files are captured, please email support at [[mailto:support@papercut.com|support@papercut.com]] with the following information:
to:
You will need to capture Windows two spool files to help us fix the issue. The steps to capture a spool file are given [[https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile| here]].

Please follow the following steps:

#Send a job to the printer set up with the Global Print Driver. Capture it's spool file
.

#Print
the same document to the target queue set up with the vendor specific driver and capture it's spool file.

# Once both the
spool files are captured, please email support at [[mailto:support@papercut.com|support@papercut.com]] with the following information:
October 02, 2014, at 08:45 AM by 203.222.91.204 -
Changed lines 1-10 from:
(:title Troubleshooting Global Print Driver:)

The PaperCut Global Print Driver is a standards compliant PostScript driver developed to produce PostScript output that is as widely compatible as possible. If vendor specific extensions are required to achieve functionality, the PaperCut server software works transparently in conjunction with the driver to apply these extensions to each job. This is done in the background using in-built Print Description Language (PDL) transforms.

When using the PaperCut Global Print Driver on the virtual queue and
the job does not get printed as expected. For example:  a color job was printed and the job got printed in grayscale.

This indicates that PaperCut's underlying transforms are not working as expected.

To help us fix the issue you will need to
follow the steps below:
to:
(:title Troubleshooting Global Print Driver Issues:)

The PaperCut Global Print Driver is a standards compliant PostScript driver developed to produce PostScript output that is as widely compatible as possible.

The PaperCut server software works transparently in conjunction with
the driver to apply vendor-specific extensions - required to achieve additional functionality. This is done in the background using in-built "Print Description Language" (PDL) transforms.

Occasionally PaperCut's underlying
transforms might not work as expected.

For example: a color print job sent by
the user prints as grayscale when using the PaperCut Global Print Driver.

To solve the issue please
follow the steps below:
Changed lines 15-18 from:
#Capture a Windows spool file by sending a job to the target queue using the vendor specific Postscript driver. The steps to capture a spool file are [[https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile| here]].

# Please email support at [[mailto:support@papercut.com|support@papercut.com]] with the following information:
** The problem in general terms
to:
#The vendor specific Postscript driver spool file also needs to be captured. Please follow the steps to capture this spool file [[https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile| here]].

# Once both spool files are captured, please email support at [[mailto:support@papercut.com|support@papercut.com]] with the following information:
** A clear description of the problem
Changed lines 21-23 from:
** The two files captured in step 1 and 2.

to:
** The two spool files captured in step 1 and 2.

Changed lines 13-14 from:
#Capture a Windows spool file by sending a job to the target queue using the vendor specific postscript driver. The steps to capture a spool file are [[https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile| here]].
to:
#Capture a Windows spool file by sending a job to the target queue using the vendor specific Postscript driver. The steps to capture a spool file are [[https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile| here]].
Changed lines 1-2 from:
(:title Troubleshooting Global Print Driver Title:)
to:
(:title Troubleshooting Global Print Driver:)
Changed lines 11-12 from:
#Capture a Windows Spool file by sending a job to the printer set up with the Gloobal Print Driver. The steps to capture a spool file are given [[https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile| here]].
to:
#Capture a Windows Spool file by sending a job to the printer set up with the Global Print Driver. The steps to capture a spool file are given [[https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile| here]].
Changed lines 15-18 from:
#Capture the two files, explain the problem and send it to us at support@papercut.com


to:
# Please email support at [[mailto:support@papercut.com|support@papercut.com]] with the following information:
** The problem in general terms
** The model and make of printer
** A link to the printer driver in use if available
** The two files captured in step 1 and 2
.

Changed line 25 from:
[-Keywords: GPD, Universal Print Driver, Global Print Driver, PDL transforms-]
to:
[-Keywords: GPD, Universal Print Driver, Global Print Driver, PDL transforms-]
Changed line 22 from:
[-Keywords: GPD, Universal Print Driver, Global Print Driver-]
to:
[-Keywords: GPD, Universal Print Driver, Global Print Driver, PDL transforms-]
Changed lines 11-16 from:
#Capture a Windows Spool file by sending a job to the printer set up with the Gloobal Print Driver. The steps to capture a spool file are given
[[https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile| here]].

#Capture a Windows spool file by sending a job to the target queue using the vendor specific postscript driver. The steps to capture a spool file are here:
[[https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile| here]].
to:
#Capture a Windows Spool file by sending a job to the printer set up with the Gloobal Print Driver. The steps to capture a spool file are given [[https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile| here]].

#Capture a Windows spool file by sending a job to the target queue using the vendor specific postscript driver. The steps to capture a spool file are [[https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile| here]].
Changed lines 11-20 from:
# Capture a Windows Spool file by sending a job to the printer set up with the Gloobal Print Driver. The steps to capture a spool file are given here: 
https:
//www.papercut.com/kb/Main/CapturingAWindowsSpoolFile

#
Capture a Windows spool file by sending a job to the target queue using the vendor specific postscript driver. The steps to capture a spool file are here:
https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile

#
Capture the two files, explain the problem and send it to us at support@papercut.com


to:
#Capture a Windows Spool file by sending a job to the printer set up with the Gloobal Print Driver. The steps to capture a spool file are given
[[https
://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile| here]].

#
Capture a Windows spool file by sending a job to the target queue using the vendor specific postscript driver. The steps to capture a spool file are here:
[[https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile| here]].

#
Capture the two files, explain the problem and send it to us at support@papercut.com


Changed lines 3-4 from:
When using the PaperCut Global Print Driver, and the job does not come out as expected. For example:  a color job was printed and the job got printed in grayscale.
to:
The PaperCut Global Print Driver is a standards compliant PostScript driver developed to produce PostScript output that is as widely compatible as possible. If vendor specific extensions are required to achieve functionality, the PaperCut server software works transparently in conjunction with the driver to apply these extensions to each job. This is done in the background using in-built Print Description Language (PDL) transforms.

When using the PaperCut Global Print Driver on the virtual queue and the job does not get printed
as expected. For example:  a color job was printed and the job got printed in grayscale.
Changed lines 17-20 from:
!!Subheading

TODO link your page here: https://www
.papercut.com/kb/Main/Miscellaneous
to:
# Capture the two files, explain the problem and send it to us at support@papercut.com


Changed line 22 from:
''Categories:'' [[Category.TODOFirstCategory|+]], [[Category.TODOSecondCategoryIfNeeded|+]]
to:
Added lines 1-22:
(:title Troubleshooting Global Print Driver Title:)

When using the PaperCut Global Print Driver, and the job does not come out as expected. For example:  a color job was printed and the job got printed in grayscale.

This indicates that PaperCut's underlying transforms are not working as expected.

To help us fix the issue you will need to follow the steps below:

# Capture a Windows Spool file by sending a job to the printer set up with the Gloobal Print Driver. The steps to capture a spool file are given here:
https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile

# Capture a Windows spool file by sending a job to the target queue using the vendor specific postscript driver. The steps to capture a spool file are here:
https://www.papercut.com/kb/Main/CapturingAWindowsSpoolFile

!!Subheading

TODO link your page here: https://www.papercut.com/kb/Main/Miscellaneous

----
''Categories:'' [[Category.TODOFirstCategory|+]], [[Category.TODOSecondCategoryIfNeeded|+]]
----
[-Keywords: GPD, Universal Print Driver, Global Print Driver-]

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 March 27, 2019, at 04:40 AM
Printable View   |   Article History   |   Edit Article