Web Print Status Messages - and what they mean
Last modified on 13 September 2021 08:51 PM
“Help! I’m a PaperCut Administrator and my users report a specific error message when they try to submit print jobs through Web Print. What does this Status message mean and how do we get documents printing?”
This means that the job has been successfully uploaded to Web Print and sent to the printer. If you’re not seeing the job after this, check to see if this issue happens without Web Print when simply printing from the server. For additional troubleshooting ideas, check out Missing Or Disappearing Print Jobs.
This means that the job has been successfully uploaded to Web Print, submitted to the printer, and is now held by PaperCut because Hold/Release or Find-Me Printing has been configured. In order to release the job, the user must authenticate at the release panel.
PaperCut may be configured to deny print jobs for a lot of different reasons. One common example is that the user has run out of balance and their account is set to restricted, which would result in the message
Print jobs may also be denied for being too large, for having too many pages, for having a disallowed file extension, or being in color or duplex. Usually this happens because the printer in PaperCut was configured this way on purpose. These settings are managed for each printer in PaperCut under Printers > [printer name] > Filters & Restrictions.
Seen to happen when a print script is enabled and requires a pop-up. Web Print works with Print Scripting but does not support pop-up notifications. You will either need to disable Print Scripting for this printer, or rewrite the script to ignore documents when the source is Web Print.
This means that Web Print is not able print the job because the printer cannot be found, which can happen for a few different reasons.
In most of those scenarios Web Print is unable to submit the print job, because the name of the “printer” in PaperCut does not actually match the name of a print queue that exists on the server or Sandbox.
To resolve, log onto the PaperCut server running the Web Print Service or workstation running the Web Print Sandbox application and make sure that the print queue still exists and that the name matches what is in PaperCut. If the print queue or print server was renamed recently, then follow these steps in How to Rename a Printer to make sure the printer has also been renamed in PaperCut.
This message will be preceded by
It has been seen to happen in a couple situations:
To resolve, log onto the PaperCut server running the Web Print Service or workstation running the Web Print Sandbox application and make sure that the “PaperCut Print Provider” service is started following these steps. Also if you are encountering this message with an older version of PaperCut, try upgrading.
If this is a Web Print Sandbox, log on as the workstation as the Web Print user account and ensure that you can print an Office document normally and there are no prompts or dialog boxes blocking the application from printing.
The WebPrint Service or Sandbox is supposed to copy the print job to the
The exact steps to get this working will depend on whether this is the Web Print Service or Web Print Sandbox. If this is the Web Print service running as SYSTEM, then this directory will be located in
Check the server where Web Print is running to ensure there is adequate disk space. Also if Web Print is running as a service account or if this is the Web Print Sandbox then check the permissions on the
This has been seen to happen for the same reason as the Unable copy print data file when preparing print job error, but when an image file is uploaded to Web Print instead of a PDF. We believe this happens when the “image handler” used by Web Print for images (like .png and .jpeg files) fails to print the job for some reason. We know from testing that you can encounter this error if the Service or Sandbox is unable to write to the Windows
Cannot access network printer - Reason #1
This happens when the Web Print Service, which runs as local system by default, tries to submit a print job to a queue hosted on another print server but lacks permission. In the world of Windows the local system account has full admin rights on the local server, but cannot interact with anything on the network, including a print queue on another server, hence the error.
Resolving this error depends on whether your PaperCut implementation is supposed to be using the Web Print Service (default) or Web Print Sandbox.
Curiously, you may also see that Office documents will succeed but PDFs and image files won’t. This is because office documents are printed through the Web Print Sandbox which runs as a domain user account, and PDFs fail because are printed by the Web Print Service which might be running as local system.
Cannot access network printer - Reason #2
This also has been seen to happen when someone edits the line