Print queue and print job error handling improvements in ExtremeZ-IP 5.0.2

1 Star2 Stars3 Stars4 Stars5 Stars
  • Product:
  • Version:
  • Document Type:
  • Revised:
  • Reviewed:


Enhanced Print Server improves queue error management and reporting functionality


With the introduction of ExtremeZ-IP File & Print Server 5.0.2×11, print queues are always available for printing unless manually suspended. When a job fails for any reason (e.g. LPR error code, TCP connection terminated, error from Windows print queue), the print job status will be set to “Offline” and the job will be re-queued. This job will be automatically retried at the configured interval. By default, ExtremeZ-IP will automatically retry offline jobs every 5 minutes until the job prints successfully. This auto-retry interval can be changed through the ExtremeZ-IP Administrator, and can be disabled entirely if desired.

ExtremeZ-IP File & Print Server 5.0.2×11 can also automatically delete jobs that have failed to print or been offline for a specified period of time. This functionality is disabled by default, and when enabled, the default setting is one day. In order to make sure that jobs aren’t automatically deleted because of a queue-wide problem (e.g. network problem, or printer turned off), jobs will only be automatically deleted if at least two other jobs have been successfully printed since the job went offline. To assist in administrative accounting and troubleshooting, the User Name, Computer Name, IP address, and time of the deleted print job are logged in the event log.

Note For users of our performance counters, any queue that has more than one offline job, and has not successfully processed a job since the last job went offline is reported by Perfmon to be an “offline” queue. Having a single offline job in a queue would not trip the counter and would not be reported as an “offline” queue (as it could just be a bad job), but having multiple offline jobs without any recent successful jobs would suggest that there may be a queue-wide problem. A queue that is reported “offline” does not differ from an “online” queue in terms of its processing – the only difference is how it is reported in performance counters. Administrators may use the print queue and print job counters to monitor the general health of the print environment.