KB Home | Troubleshooting the PaperCut Fiery Program
If you are using Fiery devices and are using PaperCut to Track Jobs on Fiery, and you’re running into issues, this is hopefully a useful set of troubleshooting steps to try and remedy the problem.
How to enable debug mode (when requested by Support)
Run the following command line for each of your Fierys. The -y option will perform a dry run. It
will read job records from the Fiery but not write those records to PaperCut. This will check if
fiery_papercut works with that Fiery. The -d option is useful for troubleshooting to capture debug-level log messages.
Fiery Dry Run (no jobs will be recorded in PaperCut):
This means that incorrect credentials for the Fiery are being used. Make sure the correct admin username and password for the Fiery are being used. Test by attempting to log into the web interface of the Fiery with those credentials.
503 Service Unavailable Error
If you see an error like this in the papercut.fiery.log file:
PaperCut uses the Fiery REST APIS that are published by the Fiery controllers on the “live” URL. If this service is not running then the PaperCut server will not be able to connect successfully.
To resolve, ensure that the Fiery is a Fiery system FS100 or later. Also, if you have a Windows Fiery System 9 Rel2 or later then you must download “Fiery Extended Applications Package 4.0” from http://w3.efi.com/, or contact EFI if the download is not available in your region.
Here’s how you can check the Fiery version and make sure that the Live URL is running and accessible:
Make sure you can browse to the live URL https://<fiery-IP-address>/live. If you don’t get a response from this address, make sure that you have the EFI Extended Applications Package installed on the Fiery workstation. Contact EFI, or check their website to download ‘Fiery Extended Applications Package 4.0’ or later.
Make sure you can browse to the status URL, https://<fiery-IP-address>/live/status
You can also check the version by browsing to https://<fiery-IP-address>/live/version. The output will look something like this:
This release contains an updated Java version which no longer supports 32-bit workstations. If you have any 32-bit users launching the User Client or Release Station from a network share, see this Knowledge Base article for more information.