Troubleshooting GCP Issues

KB Home   |   Troubleshooting GCP Issues

Main.DebuggingGCPIssues History

Hide minor edits - Show changes to output

November 22, 2019, at 03:52 AM by Mel Zouzoulas - Added Mobility Print
Added lines 2-3:

If you're looking for an alternative to Google Cloud Print, see [[https://www.papercut.com/products/free-software/mobility-print/|PaperCut Mobility Print]]. It provides you a simple way to print from your devices like iOS, Android, `ChromeOS, Windows and `MacOS. We have a migration article over [[https://www.papercut.com/kb/Main/HowToMigrateFromGoogleCloudPrintToMobilityPrint|here]]
April 24, 2018, at 11:29 PM by Aaron Pouliot -
Changed lines 5-7 from:
A: Check that you're running the latest version of PaperCut
Since Google's own Cloud Print product is still in Beta, there may be bug fixes and updates included with recent releases of the PaperCut Application Server and Print Provider - check the [[https://www.papercut.com/release-history/|Release History]] page to see if you're running the latest version, and to see if there have been any recent Google Cloud Print changes.
to:
A: Check that you’re running the latest version of PaperCut Since Google’s own Cloud Print product is still in Beta, there may be bug fixes and updates included with recent releases of the PaperCut Application Server and Print Provider - check the [[https://www.papercut.com/release-history/|Release History]]  page to see if you’re running the latest version, and to see if there have been any recent Google Cloud Print changes.
Changed lines 13-17 from:
Q: What do I check if the GCP jobs are logged under the wrong user?

A: We often see this happen if the customer has used the Google Cloud Print Connector or Chrome browser to publish the printers to Google Cloud Print, instead of publishing the printers through PaperCut.  When this happens, the PaperCut server sees that the jobs being printed on the print server by whatever user that shared the printers through Chrome or whatever service account that the Google Cloud Print Connector is running as (usually SYSTEM).

However, if you want to track what users are printing the jobs, you will need to publish these printers using PaperCut's implementation of Google Cloud Print.  Confirm that
you have enabled Google Cloud Print in PaperCut in the Mobile & BYOD section, then select a printer in PaperCut, and on the Summary tab choose "Publish to Google Cloud Print". There will now be a link to manage that printer in the Google Cloud Print web interface and share it out with your users.
to:
Q: What do I check if the GCP jobs are logged as the wrong user?

A: We sometimes see this happen if the printers were published using the Google Cloud Print Connector or Chrome browser, instead of PaperCut's implementation of Google Cloud Print.  When this happens, all of the jobs from GCP will be charged to the SYSTEM account (or whatever service account that the Google Cloud Print Connector is running as).

If this is happening, make sure
you have enabled Google Cloud Print in PaperCut in the Mobile & BYOD section, then select a printer in PaperCut, and on the Summary tab choose "Publish to Google Cloud Print". There will now be a link to manage that printer in the Google Cloud Print web interface and share it out with your users.
February 08, 2018, at 07:08 PM by Aaron Pouliot - Added screenshot showing pc_server_build tag
Changed lines 20-22 from:
To verify that the printer is being shared from PaperCut, log into the Google Cloud Print management interface, select a printer, choose Details, then expand the Advanced Details.  A printer published by PaperCut to Google Cloud print will have the tag "pc_server_build" followed by a build number.
to:
To verify that the printer is being shared from PaperCut, log into the Google Cloud Print management interface, select a printer, choose Details, then expand the Advanced Details.  A printer published by PaperCut to Google Cloud print will have the tag "pc_server_build" followed by a build number like the screenshot below.  If the tag "pc_server_build" number is missing, then the printer has not been published to Google Cloud Print using PaperCut.

Attach:PaperCut_GCP_Printer.png
February 02, 2018, at 07:57 PM by timg - Revamped a little, and linked to other useful articles too.
Changed lines 3-5 from:
!!Check that you're running the latest version of PaperCut
to:
Q: What version of PaperCut am I running?

A:
Check that you're running the latest version of PaperCut
Changed lines 8-11 from:
!!Finding Google Cloud Print (GCP) Jobs in PaperCut

You can see jobs printed through a PaperCut Google Cloud Print printer in the PaperCut Job Log. Go to the web admin interface in Printers : Job Log. "Google Cloud Print" (without the quotation marks) appears in the Attribs. column for the job.
to:
Q: How do I find GCP jobs in PaperCut?

A:
You can see jobs printed through a PaperCut Google Cloud Print printer in the PaperCut Job Log. Go to the web admin interface in Printers : Job Log. "Google Cloud Print" (without the quotation marks) appears in the Attribs. column for the job.
Changed lines 14-16 from:
!!Google Cloud Print jobs are logged in PaperCut as wrong user
We
often see this happen if the customer has used the Google Cloud Print Connector or Chrome browser to publish the printers to Google Cloud Print, instead of publishing the printers through PaperCut.  When this happens, the PaperCut server sees that the jobs being printed on the print server by whatever user that shared the printers through Chrome or whatever service account that the Google Cloud Print Connector is running as (usually SYSTEM).
to:
Q: What do I check if the GCP jobs are logged under the wrong user?

A:
We often see this happen if the customer has used the Google Cloud Print Connector or Chrome browser to publish the printers to Google Cloud Print, instead of publishing the printers through PaperCut.  When this happens, the PaperCut server sees that the jobs being printed on the print server by whatever user that shared the printers through Chrome or whatever service account that the Google Cloud Print Connector is running as (usually SYSTEM).
Changed lines 24-26 from:
!!Jobs intermittently appear to be stuck "In Progress" in environments with a Securly Webfilter
Some customers using Securly for Web Filtering, have noticed that intermittently jobs submitted via Google Cloud Print won't print, and will have a status of "In Progress".  When checking the error log there should be messages " Failed to download job... [the URL] returned a response status of 426 null".  Securly has a documented workaround for this issue, which is to install their trusted certificate in the Keystore so that they can monitor this web traffic (like a man-in-the-middle attack). 
to:
Q: Jobs are stuck as 'In progress' - what can I check?

A:
Some customers using Securly for Web Filtering, have noticed that intermittently jobs submitted via Google Cloud Print won't print, and will have a status of "In Progress".  When checking the error log there should be messages " Failed to download job... [the URL] returned a response status of 426 null".  Securly has a documented workaround for this issue, which is to install their trusted certificate in the Keystore so that they can monitor this web traffic (like a man-in-the-middle attack). 
Changed lines 30-32 from:
!!Debugging Google Cloud Print Connectivity Issues
The '''Application Server''' has to be able to make connections to Google Cloud Print services as detailed in the relevant section of our [[https://www.papercut.com/products/ng/manual/applicationserver/topics/mobile-google-cloud-print.html#aanchor794|User Manual]]. Please check our Google Cloud Print '''Requirements''' carefully to ensure that your environment meets our specifications.
to:
Q: How do I debug connectivity issues?

A:
The '''Application Server''' has to be able to make connections to Google Cloud Print services as detailed in the relevant section of our [[https://www.papercut.com/products/ng/manual/applicationserver/topics/mobile-google-cloud-print.html#aanchor794|User Manual]]. Please check our Google Cloud Print '''Requirements''' carefully to ensure that your environment meets our specifications.
Changed lines 48-53 from:
!!Address XMPP/Jabber security concerns
Another thing to consider was something brought up by one of our educational customers concerning network security
. At one point a packet shaping implementation had been put in place to intercept XMPP/Jabber traffic in an effort to prevent inappropriate content sharing between students. XMPP happens to be the same protocol that Google Cloud Print uses to perform printer discovery and authentication management with PaperCut. What we learned from this scenario is that If XMPP is traffic is being restricted, then PaperCut will not be able to correctly do its printer discovery and authentication management. In this case the symptom was that the customer had a persistent issue with their Google Cloud Printers showing offline.

!!Distinguishing PaperCut GCP printers from other GCP printers
There
are ways of publishing a printer in GCP other than with PaperCut. e.g. Google Chrome allows you to publish printers on GCP. PaperCut may track jobs from these non-PaperCut GCP Printers. e.g. PaperCut may be tracking the printers that Google Chrome publishes to GCP. You can distinguish PaperCut GCP printers from those published by Google Chrome by setting a naming template with the PaperCut web admin Config Editor:
to:
Q: What if my GCP printers are showing as 'offline'?

A: Take a look at [[https://www
.papercut.com/kb/Main/WhenPaperCutPublishedGoogleCloudPrintPrintersShowAsOffline|Troubleshooting GCP printers showing as offline]]

Q: What security concerns are there?

A: Another thing
to consider was something brought up by one of our educational customers concerning network security. At one point a packet shaping implementation had been put in place to intercept XMPP/Jabber traffic in an effort to prevent inappropriate content sharing between students. XMPP happens to be the same protocol that Google Cloud Print uses to perform printer discovery and authentication management with PaperCut. What we learned from this scenario is that If XMPP is traffic is being restricted, then PaperCut will not be able to correctly do its printer discovery and authentication management. In this case the symptom was that the customer had a persistent issue with their Google Cloud Printers showing offline.

Q: How do I distinguish PaperCut GCP printers from other GCP printers

A:
There are ways of publishing a printer in GCP other than with PaperCut. e.g. Google Chrome allows you to publish printers on GCP. PaperCut may track jobs from these non-PaperCut GCP Printers. e.g. PaperCut may be tracking the printers that Google Chrome publishes to GCP. You can distinguish PaperCut GCP printers from those published by Google Chrome by setting a naming template with the PaperCut web admin Config Editor:
Changed lines 70-73 from:

!!Still having issues with
GCP?

If you have checked all the items above, and you’re still seeing issues please follow these steps:
to:
Q: What if I'm still having issues with GCP?

A: If you have checked all the items above, and you’re still seeing issues please follow these steps:
November 17, 2017, at 06:15 PM by Aaron Pouliot - fixed typo
Changed lines 19-20 from:
If the printer does not have this tag,
then double check the steps on [[https://www.papercut.com/products/ng/manual/applicationserver/topics/mobile-google-cloud-print.html|set up Google Cloud Print]] in the manual to make sure the printers have been published correctly. 
to:
If the printer does not have this tag, then double check the steps in [[https://www.papercut.com/products/ng/manual/applicationserver/topics/mobile-google-cloud-print.html|how to set up Google Cloud Print]] in the manual to make sure the printers have been published correctly. 
November 16, 2017, at 10:00 PM by Aaron Pouliot -
Changed lines 19-20 from:
Double check the steps in the m in the manual on how to [[https://www.papercut.com/products/ng/manual/applicationserver/topics/mobile-google-cloud-print.html|set up Google Cloud Print]] to make sure the printers have been published correctly. 
to:
If the printer does not have this tag,
 then double check the steps on
[[https://www.papercut.com/products/ng/manual/applicationserver/topics/mobile-google-cloud-print.html|set up Google Cloud Print]] in the manual to make sure the printers have been published correctly. 
November 16, 2017, at 09:59 PM by Aaron Pouliot -
Changed lines 17-19 from:
See the steps in the manual, under the header "Publishing Printers to Google Cloud Print via PaperCut": https://www.papercut.com/products/ng/manual/applicationserver/topics/mobile-google-cloud-print.html
to:
To verify that the printer is being shared from PaperCut, log into the Google Cloud Print management interface, select a printer, choose Details, then expand the Advanced Details.  A printer published by PaperCut to Google Cloud print will have the tag "pc_server_build" followed by a build number. 

Double check the steps in the m in the manual on how to [[https://www.papercut.com/products/ng/manual/applicationserver/topics/mobile-google-cloud-print.html|set up Google Cloud Print]] to make sure the printers have been published correctly. 
November 16, 2017, at 06:47 PM by Aaron Pouliot - fixed manual link
Changed line 17 from:
See the steps in the manual here: https://www.papercut.com/products/ng/manual/applicationserver/topics/mobile-google-cloud-print/#mobile-gcp-setup-printers
to:
See the steps in the manual, under the header "Publishing Printers to Google Cloud Print via PaperCut": https://www.papercut.com/products/ng/manual/applicationserver/topics/mobile-google-cloud-print.html
November 16, 2017, at 06:43 PM by Aaron Pouliot - Included info about why GCP jobs come in as the wrong user
Added lines 11-17:

!!Google Cloud Print jobs are logged in PaperCut as wrong user
We often see this happen if the customer has used the Google Cloud Print Connector or Chrome browser to publish the printers to Google Cloud Print, instead of publishing the printers through PaperCut.  When this happens, the PaperCut server sees that the jobs being printed on the print server by whatever user that shared the printers through Chrome or whatever service account that the Google Cloud Print Connector is running as (usually SYSTEM).

However, if you want to track what users are printing the jobs, you will need to publish these printers using PaperCut's implementation of Google Cloud Print.  Confirm that you have enabled Google Cloud Print in PaperCut in the Mobile & BYOD section, then select a printer in PaperCut, and on the Summary tab choose "Publish to Google Cloud Print". There will now be a link to manage that printer in the Google Cloud Print web interface and share it out with your users.

See the steps in the manual here: https://www.papercut.com/products/ng/manual/applicationserver/topics/mobile-google-cloud-print/#mobile-gcp-setup-printers
November 13, 2017, at 06:57 PM by Aaron Pouliot -
Changed lines 13-15 from:
We do see a specific error message when customers are using Securly for Web Filtering, in the Google Cloud Print web interface jobs have a status of "In Progress".  When checking the error log there should be messages " Failed to download job... [the URL] returned a response status of 426 null".  Securly has a documented workaround for this issue, which is to install their trusted certificate in the Keystore so that they can monitor this web traffic (like a man-in-the-middle attack).  https://support.securly.com/hc/en-us/articles/224762187-Papercut-Google-Cloud-Print-not-working-with-Securly
to:
Some customers using Securly for Web Filtering, have noticed that intermittently jobs submitted via Google Cloud Print won't print, and will have a status of "In Progress". When checking the error log there should be messages " Failed to download job... [the URL] returned a response status of 426 null".  Securly has a documented workaround for this issue, which is to install their trusted certificate in the Keystore so that they can monitor this web traffic (like a man-in-the-middle attack). 

See
: https://support.securly.com/hc/en-us/articles/224762187-Papercut-Google-Cloud-Print-not-working-with-Securly
November 13, 2017, at 06:51 PM by Aaron Pouliot - Added info about Securly and 426 null error
Deleted line 5:
Added lines 12-13:
!!Jobs intermittently appear to be stuck "In Progress" in environments with a Securly Webfilter
We do see a specific error message when customers are using Securly for Web Filtering, in the Google Cloud Print web interface jobs have a status of "In Progress".  When checking the error log there should be messages " Failed to download job... [the URL] returned a response status of 426 null".  Securly has a documented workaround for this issue, which is to install their trusted certificate in the Keystore so that they can monitor this web traffic (like a man-in-the-middle attack).  https://support.securly.com/hc/en-us/articles/224762187-Papercut-Google-Cloud-Print-not-working-with-Securly
September 12, 2017, at 02:10 AM by peterf - Revised some content, and added mention of new feature in 17.3
Changed lines 15-18 from:
The Application Server has to be able to make connections to the Google Cloud as detailed in the 'requirements' section of the [[https://www.papercut.com/products/ng/manual/ch-google-cloud-print.html|Google Cloud Print manual page]].

Check that the necessary ports on your firewall are opened up as detailed on the [[https://www
.papercut.com/kb/Main/FirewallPorts|Firewall Ports]] page - especially port 5222. From the PaperCut server (not your own workstation), run a terminal or command prompt, and type the following command:
to:
The '''Application Server''' has to be able to make connections to Google Cloud Print services as detailed in the relevant section of our [[https://www.papercut.com/products/ng/manual/applicationserver/topics/mobile-google-cloud-print.html#aanchor794|User Manual]]. Please check our Google Cloud Print '''Requirements''' carefully to ensure that your environment meets our specifications.

Check that the necessary ports on your firewall are opened up as detailed in the [[https://www.papercut.com/kb/Main/FirewallPorts|Firewall Configuration - Ports Used by PaperCut NG and PaperCut MF]] Knowledge Base article, particularly TCP port 5222. From the '''Application Server''' (not your own workstation), open a Terminal or Command Prompt session
, and type the following command:
Changed lines 21-22 from:
For example on a Mac you should see:
to:
On macOS you should see the following result, if everything is okay:
Changed lines 25-26 from:
Or on Windows you should see:
to:
On Windows, you should instead see this:
Changed lines 28-29 from:
Note that if you get a message saying that Telnet does not exist, then you may need to enable/install Telnet on your server as per this Microsoft Technet article on [[https://technet.microsoft.com/en-us/library/cc771275|installing Telnet Client]] on Windows.
to:

Note that if you get a message saying that Telnet does not exist, then you may need to enable/install Telnet on your server. On Windows, this is done as per the [[https://technet.microsoft.com/en-us/library/cc771275|Install Telnet Client]] Microsoft [=TechNet=] article. Telnet was removed from the High Sierra release of macOS. One method to install it is to first install [[https://brew.sh/|Homebrew]], and then follow the instructions found [[https://dor.ky/restore-telnet-in-mac-os-high-sierra-10-13/|here]] to use Homebrew to download the Telnet binary.
March 08, 2017, at 07:03 PM by Art Almaguer - small edit to my XMPP addendum from yesterday
Changed line 31 from:
Another thing to consider was something brought up by one of our educational customers concerning network security. At one point a packet shaping implementation had been put in place to intercept XMPP/Jabber traffic in an effort to prevent inappropriate content sharing between students. XMPP happens to be the same protocol that Google Cloud Print uses to perform printer discovery and authentication management with PaperCut. What we learned from this scenario is that If XMPP is traffic is being restricted, then PaperCut will not be able to correctly do its printer discovery and authentication management.
to:
Another thing to consider was something brought up by one of our educational customers concerning network security. At one point a packet shaping implementation had been put in place to intercept XMPP/Jabber traffic in an effort to prevent inappropriate content sharing between students. XMPP happens to be the same protocol that Google Cloud Print uses to perform printer discovery and authentication management with PaperCut. What we learned from this scenario is that If XMPP is traffic is being restricted, then PaperCut will not be able to correctly do its printer discovery and authentication management. In this case the symptom was that the customer had a persistent issue with their Google Cloud Printers showing offline.
March 08, 2017, at 01:05 AM by Art Almaguer - added section to Address XMPP/Jabber security concerns
Added lines 30-31:
!!Address XMPP/Jabber security concerns
Another thing to consider was something brought up by one of our educational customers concerning network security. At one point a packet shaping implementation had been put in place to intercept XMPP/Jabber traffic in an effort to prevent inappropriate content sharing between students. XMPP happens to be the same protocol that Google Cloud Print uses to perform printer discovery and authentication management with PaperCut. What we learned from this scenario is that If XMPP is traffic is being restricted, then PaperCut will not be able to correctly do its printer discovery and authentication management.
August 23, 2016, at 03:14 AM by peterf - REALLY fixed that link. For REAL.
Changed line 28 from:
Note that if you get a message saying that Telnet does not exist, then you may need to enable/install Telnet on your server as per this Microsoft Technet article on [[https://technet.microsoft.com/en-us/library/cc771275(v=ws.10).aspx|installing Telnet Client]] on Windows.
to:
Note that if you get a message saying that Telnet does not exist, then you may need to enable/install Telnet on your server as per this Microsoft Technet article on [[https://technet.microsoft.com/en-us/library/cc771275|installing Telnet Client]] on Windows.
August 23, 2016, at 03:13 AM by peterf - Fixed the link for Telnet install instructions.
Changed line 28 from:
Note that if you get a message saying that Telnet does not exist, then you may need to enable/install Telnet on your server as per this Microsoft Technet article on [[http://technet.microsoft.com/en-us/library/cc771275(v=WS.10).aspx|installing Telnet Client]] on Windows.
to:
Note that if you get a message saying that Telnet does not exist, then you may need to enable/install Telnet on your server as per this Microsoft Technet article on [[https://technet.microsoft.com/en-us/library/cc771275(v=ws.10).aspx|installing Telnet Client]] on Windows.
Changed lines 17-18 from:
Check that the necessary ports on your firewall are opened up as detailed on the [[https://www.papercut.com/kb/Main/FirewallPorts|Firewall Ports]] page - especially port 5222. From the PaperCut server, run a terminal or command prompt, and type the following command:
to:
Check that the necessary ports on your firewall are opened up as detailed on the [[https://www.papercut.com/kb/Main/FirewallPorts|Firewall Ports]] page - especially port 5222. From the PaperCut server (not your own workstation), run a terminal or command prompt, and type the following command:
Changed lines 28-29 from:

to:
Note that if you get a message saying that Telnet does not exist, then you may need to enable/install Telnet on your server as per this Microsoft Technet article on [[http://technet.microsoft.com/en-us/library/cc771275(v=WS.10).aspx|installing Telnet Client]] on Windows.

April 10, 2014, at 08:38 PM by TimG - Added steps for sending further debug information
Changed lines 3-6 from:
to:
!!Check that you're running the latest version of PaperCut
Since Google's own Cloud Print product is still in Beta, there may be bug fixes and updates included with recent releases of the PaperCut Application Server and Print Provider - check the [[https://www.papercut.com/release-history/|Release History]] page to see if you're running the latest version, and to see if there have been any recent Google Cloud Print changes.

April 10, 2014, at 08:36 PM by TimG - Added steps for sending further debug information
Added lines 41-57:
!!Still having issues with GCP?

If you have checked all the items above, and you’re still seeing issues please follow these steps:

*Enable debug mode in the App Server as detailed on the [[https://www.papercut.com/kb/Main/HowToEnableDebugInNG|Application Server Debug]] page
*Additionally check the 'Enable detailed logging for Google Cloud Print’ box under Options -> Advanced -> Diagnostics
*Restart the App Server if possible, or re-publish printers that you’re having issues with, or send a test job through the system to capture the process that you’re seeing difficulties with in debug mode

Please then send an email to us through the Admin console’s ‘About' tab -> Support Info -> Email Support. Please include:

#Version and build number of PaperCut
#Debug logs as detailed in the KB article above
#Username/email address of the user sending the test print job / Printername of the printer that you’re testing with, or any other specific test information that we can use to narrow down the area of the logs to look in.



Changed line 61 from:
[-Keywords: GCP, Android, google printer hosting, spooler service, windows queue, chromebook, byod -]
to:
[-Keywords: GCP, Android, google printer hosting, spooler service, windows queue, chromebook, byod, troubleshoot -]
April 10, 2014, at 08:33 PM by TimG - Added connectivity debug test
Added line 10:
Added lines 20-21:
Attach:gcp_telnet_mac.png"Mac Telnet Terminal"
Changed lines 24-26 from:
to:
Attach:gcp_telnet_win.png"Windows Telnet Terminal"

Changed lines 6-9 from:
You can see jobs printed through a PaperCut Google Cloud Print printer in the PaperCut Job Log. Go to the web admin interface in Printers : Job Log

"Google Cloud Print" (without the quotation marks) appears in the Attribs. column for the job.
to:
You can see jobs printed through a PaperCut Google Cloud Print printer in the PaperCut Job Log. Go to the web admin interface in Printers : Job Log. "Google Cloud Print" (without the quotation marks) appears in the Attribs. column for the job.
Changed lines 10-12 from:
NOTE: Only PaperCut GCP printer jobs appear here.

to:
!!Debugging Google Cloud Print Connectivity Issues
The Application Server has to be able to make connections to the Google Cloud as detailed in the 'requirements' section of the [[https://www
.papercut.com/products/ng/manual/ch-google-cloud-print.html|Google Cloud Print manual page]].

Check that the necessary ports on your firewall are opened up as detailed on the [[https://www.papercut.com/kb/Main/FirewallPorts|Firewall Ports]] page - especially port 5222. From the PaperCut server, run a terminal or command prompt, and type the following command:

@@telnet talk.google.com 5222@@

For example on a Mac you should see:

Or on Windows you should see:


Changed lines 23-28 from:
There are ways of publishing a printer in GCP other than with PaperCut. e.g. Google Chrome allows you to publish printers on GCP.

PaperCut
may track jobs from these non-PaperCut GCP Printers. e.g. PaperCut may be tracking the printers that Google Chrome publishes to GCP.

You
can distinguish PaperCut GCP printers from those published by Google Chrome by setting a naming template with the PaperCut web admin Config Editor.
to:
There are ways of publishing a printer in GCP other than with PaperCut. e.g. Google Chrome allows you to publish printers on GCP. PaperCut may track jobs from these non-PaperCut GCP Printers. e.g. PaperCut may be tracking the printers that Google Chrome publishes to GCP. You can distinguish PaperCut GCP printers from those published by Google Chrome by setting a naming template with the PaperCut web admin Config Editor:
Changed lines 35-36 from:
''Also See: [[https://www.papercut.com/tour/google-cloud-print/|PaperCut Google Cloud Print Tour]]''
to:
April 10, 2014, at 07:52 PM by TimG - Updated attribute screenshot to one image.
Changed lines 10-13 from:
Whole Job Log entry Attach:gcp_in_joblog.png"A GCP job in PaperCut Job Log"

Attribs of entry Attach:gcp_attribs.png"Attributes of job
"
to:
Attach:gcp_attributes.png"A GCP job in PaperCut Job Log"
February 04, 2014, at 01:36 AM by peter - consistenized
Changed lines 4-5 from:
!!Finding Google Cloud Print Jobs in PaperCut
to:
!!Finding Google Cloud Print (GCP) Jobs in PaperCut
Changed lines 14-16 from:
NOTE: Only PaperCut Google Cloud Print printer jobs appear here.

to:
NOTE: Only PaperCut GCP printer jobs appear here.

Changed lines 18-21 from:
There are ways of publishing a printer in Google Cloud Print other than with PaperCut. e.g. Google Chrome allows you to publish printers on Google Cloud Print.

PaperCut may track jobs from these non-PaperCut Google Cloud Printers. e.g. PaperCut may be tracking the printers that Google Chrome publishes to Google Cloud Print.
to:
There are ways of publishing a printer in GCP other than with PaperCut. e.g. Google Chrome allows you to publish printers on GCP.

PaperCut may track jobs from these non-PaperCut GCP Printers. e.g. PaperCut may be tracking the printers that Google Chrome publishes to GCP.
Changed lines 30-31 from:
Another way to check whether a GCP printer is published by PaperCut is to go to the printer in the PaperCut web admin interface Printers : Printer List : <Printer name>: Printer Details then go the Google Cloud Print section and click on the "Manage sharing in Google Cloud Print" link.
to:
Another way to check whether a GCP printer is published by PaperCut is to go to the printer in the PaperCut web admin interface Printers : Printer List : <Printer name>: Printer Details then go the "Google Cloud Print" section and click on the "Manage sharing in Google Cloud Print" link.
Changed lines 14-16 from:
""NOTE: Only PaperCut Google Cloud Print printer jobs appear here.""

to:
NOTE: Only PaperCut Google Cloud Print printer jobs appear here.

Changed lines 6-7 from:
You can see jobs printed through a PaperCut Google Cloud Print printer in the PaperCut Job Log. This is in the web admin interface in Printers : Job Log
to:
You can see jobs printed through a PaperCut Google Cloud Print printer in the PaperCut Job Log. Go to the web admin interface in Printers : Job Log
Changed lines 18-19 from:
There are other ways of publishing a printer in Google Cloud Print other than with PaperCut. e.g. Google Chrome allows you to publish printers on Google Cloud Print.
to:
There are ways of publishing a printer in Google Cloud Print other than with PaperCut. e.g. Google Chrome allows you to publish printers on Google Cloud Print.
February 04, 2014, at 01:27 AM by peter - First draft
Changed lines 14-16 from:
"""NOTE: Only PaperCut Google Cloud Print printer jobs appear here."""

to:
""NOTE: Only PaperCut Google Cloud Print printer jobs appear here.""

Changed lines 22-23 from:
You can distinguish PaperCut Google Cloud Print printers from those published by Google Chrome by setting a naming template with the PaperCut web admin Config Editor.
to:
You can distinguish PaperCut GCP printers from those published by Google Chrome by setting a naming template with the PaperCut web admin Config Editor.
Changed lines 28-31 from:
This will make the PaperCut Google Cloud Print printer start with "PC__". e.g. If the printer name is "Physics Printer" then it will appear in Google Cloud Print as "PC_Physics Printer"


to:
This will make the PaperCut GCP printer start with "PC__". e.g. If the printer name is "Physics Printer" then it will appear in GCP as "PC_Physics Printer". If this printer was also published to GCP by Google Chrome then it would appear as "Physics Printer".

Another way to check whether a GCP printer is published by PaperCut is to go to the printer in the PaperCut web admin interface Printers : Printer List : <Printer name>: Printer Details then go the Google Cloud Print section and click on the "Manage sharing in Google Cloud Print" link.

If you want to check id a CGP printer was published through PaperCut then find your  printer in https://www.google.com/cloudprint#printers and select "Advanced Details". PaperCut GCP printers will have a pc_server_build tag.

''Also See: [[https://www.papercut.com/tour/google-cloud-print/|PaperCut Google Cloud Print Tour]]''

Changed line 37 from:
''Categories:'' [[Category.TODOFirstCategory|+]], [[Category.TODOSecondCategoryIfNeeded|+]]
to:
''Categories:'' [[Category.Printers|+]], [[Category.GoogleCloudPrint|+]]
Changed line 39 from:
[-Keywords: TODO keywords here if needed-]
to:
[-Keywords: GCP, Android, google printer hosting, spooler service, windows queue, chromebook, byod -]
Added line 11:
Changed lines 14-15 from:
!!NOTE: Only PaperCut Google Cloud Print printer jobs appear here.
to:
"""NOTE: Only PaperCut Google Cloud Print printer jobs appear here."""


!!Distinguishing PaperCut GCP printers from other GCP printers
Changed lines 9-11 from:
Attach:gcp_in_joblog.png"A GCP job in PaperCut Job Log"
Attach:gcp_attribs.png"Attributes of job"
to:

Whole Job Log entry
Attach:gcp_in_joblog.png"A GCP job in PaperCut Job Log"
Attribs of entry Attach:gcp_attribs.png"Attributes of job"
Changed lines 19-20 from:

to:
You can distinguish PaperCut Google Cloud Print printers from those published by Google Chrome by setting a naming template with the PaperCut web admin Config Editor.

Go to Options : Config Editor
Edit value of "gcp.printers.name-template" e.g. PC__%printer-queue%
Press the Update button

This will make the PaperCut Google Cloud Print printer start with "PC__". e.g. If the printer name is "Physics Printer" then it will appear in Google Cloud Print as "PC_Physics Printer"


February 04, 2014, at 12:51 AM by peter - temp safety save
Changed lines 4-10 from:

!!Subheading

%right% Attach:gcp_in_joblog.png"A GCP job
in PaperCut"

TODO link your page here: https://www
.papercut.com/kb/Main/Miscellaneous
to:
!!Finding Google Cloud Print Jobs in PaperCut

You can see jobs printed through a PaperCut Google Cloud Print printer in the PaperCut Job Log
. This is in the web admin interface in Printers : Job Log

"Google Cloud Print" (without the quotation marks) appears in the Attribs
. column for the job.
Attach:gcp_in_joblog.png"A GCP job in PaperCut Job Log"
Attach:gcp_attribs.png"Attributes of job"

!!NOTE: Only PaperCut Google Cloud Print printer jobs appear here.

There are other ways of publishing a printer in Google Cloud Print other than with PaperCut. e.g. Google Chrome allows you to publish printers on Google Cloud Print.

PaperCut may track jobs from these non-PaperCut Google Cloud Printers. e.g. PaperCut may be tracking the printers that Google Chrome publishes to Google Cloud Print.


Changed lines 7-8 from:
%rframe% Attach:gcp_in_joblog.png"A GCP job in PaperCut"
to:
%right% Attach:gcp_in_joblog.png"A GCP job in PaperCut"
Changed lines 7-8 from:
Attach:gcp_in_joblog.png"A GCP job in PaperCut"
to:
%rframe% Attach:gcp_in_joblog.png"A GCP job in PaperCut"
Changed lines 7-8 from:
[[Attach:gcp_in_joblog.png]]
to:
Attach:gcp_in_joblog.png"A GCP job in PaperCut"
Added lines 7-8:
[[Attach:gcp_in_joblog.png]]
Changed line 14 from:
[-Keywords: TODO keywords here if needed-]
to:
[-Keywords: TODO keywords here if needed-]
Added lines 1-12:
(:title Troubleshooting GCP Issues:)



!!Subheading

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

----
''Categories:'' [[Category.TODOFirstCategory|+]], [[Category.TODOSecondCategoryIfNeeded|+]]
----
[-Keywords: TODO keywords here if needed-]

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 November 22, 2019, at 03:52 AM
Printable View   |   Article History   |   Edit Article