Frequently Asked Questions: Prevent jobs being released when a printer is in error
Instead of letting users release print jobs to printers reporting an error, you can configure your Find-Me and Secure Print Release environment to provide users with a consistent alert instead. This allows them to choose to either release to an alternative MFD in a Find-Me environment, resolve the printer error, or simply come back later.
Yes...well, nearly all of them. This feature is supported on all types of Release Stations, except for Fast ReleaseFast Release is a print release (Secure/Find-Me Printing) solution that uses off-the-shelf card readers available from multiple manufacturers. A Fast Release terminal is connected to the network (not the printer) allowing it to be used with any printer. A USB card reader is connected to the the Fast Release terminal and users use their proximity card to authenticate. PaperCut releases the users held print jobs to the printer assosiated with the Fast Release terminal. terminals. However, by default, it is disabled. You can easily enable this feature in just a few quick steps. The way in which you do this depends on the type of Release StationPrint Release Stations place a print job on hold and allow users to release it when required. Often a Release Station is a dedicated PC terminal located next to the printers, however, Release Stations can take other forms such as a web browser based interface. Some common examples where Release Stations can be used include secure printing, approved printing, and authentication. In a secure printing environment jobs are only printed when the user arrives at the print area and confirms his or her identity. This ensures the user is there to collect the job and other users can't "accidentally" collect the document. In some organizations it may be appropriate to hold jobs until they are approved by selected individuals. A good example would be a teacher approving printing on an expensive color printer. Hold/Release queues can be used as a form of authentication in an unauthenticated environment. Users must authenticate prior to releasing their jobs allowing PaperCut NG/MF to confirm their identity. you have. For more information, see:
- MFD Release Station
- web-based Release Station interfaces (including the Admin web interface Devices > Jobs Pending Release, User web interfaceThe User web interface provide a range of services for users, including a summary of usage and balance history, a list of the shared accounts that the user can use for printing, the current costs for printing usage, ability to add balance by using a TopUp/Pre-Paid Card or an external payment system (when using the payment gateway module), transfer funds to other users, view a history of balance transactions, view a list of the user's recent printing, and view print jobs pending release (when using a Release Station). > Jobs Pending Release, Release Manager interface, and the Mobile Release interface).
- Standard Release Stations
Yes you can!
In PaperCut MF, you have the flexibility to switch this feature on per supported device.
If a printer has reported an error, the Release Station at which the user attempted to release the job will display a message stating why the print job has not been released. It will contain enough information so they can resolve simple issues themselves, such as a paper jam, or open printer door.
For MFD Release Stations, PaperCut MF checks the SNMPSimple Network Management Protocol (SNMP) is a component of the Internet Protocol Suite as defined by the Internet Engineering Task Force (IETF). It consists of a set of standards for network management, including an application layer protocol, a database schema, and a set of data objects. Devices that typically support SNMP include routers, switches, servers, workstations, printers, modem racks and more. error status every 5 seconds while the user is logged onto the device.
For errors that users can usually fix themselves, such as a paper jam or open door, PaperCut MF web-based and Standard Release Stations check the error status every 10 seconds. For errors that usually require a technician’s assistance, such as offline, PaperCut MF gradually reduces the frequency of resolution checks until once a minute. The reasoning behind this is to find a balance between providing users with the best possible experience at the device, and also minimizing the amount of load on the server in large environments. A user will have to wait 10 seconds at most after they fix a common error, before they can release their print job.
Any print jobs that were released before the printer went into error, are printed when the error is resolved.
If the printer in error cannot be fixed, the user can release the print job at any other printer in a Find-Me environment.
Any job that is released after a printer reports an error will be held. Any job that was released before the printer reported an error will not be held. For example, if a user releases two jobs and the printer reports an error during the first job, both jobs will print after the printer error is fixed, because they were both released before the printer error was reported.
Yes you can! By default, PaperCut MF prevents jobs from being released when one or more errors from a predefined error list occurs, however, you can customize this error list to suit your own needs. For more information, see:
For information about which device types support the prevention of jobs being released on an MFD Release Station, see Prevent jobs being released from an MFD Release Station when a device is in error
All printer brands are supported, however, these Release Stations rely on the print queueA print queue displays information about documents that are waiting to be printed, such as the printing status, document owner, and number of pages to print. You can use the print queue to view, pause, resume, restart, and cancel print jobs. status, as reported by the Operating System (e.g. Windows). This means that the experience might vary depending on the printer and driver in use. Not all printers report all errors. For example, a common error that a few printers do not report, is Out of Paper.
If your printer does not report any errors at all, check that SNMP error reporting is configured on the printer and try a different driver. Some Sharp models will require additional configuration by a Sharp technician.
For more information, contact PaperCut MF Support.
If you automatically release a job on login, there is not enough time for the device to poll the SNMP error status, which means the job will always be released due to the 5 second polling interval. The alternative was to hold release of the job on login until the SNMP error status has been polled, causing delays in the release of every job. We decided to provide the best user experience by not causing delays to the release of every error.