| Previous | Next |
| ERROR_NO_SPOOL_SPACE | ERROR_NETNAME_DELETED |
ERROR_PRINT_CANCELLED
A print job is an independently managed spooler object. After submission, it can be deleted by the submitting user, an administrator, queue management code, or a spooler operation such as a purge. The application can therefore still hold a printer or job identifier while the queued document it expected to use has already disappeared.
This differs from a device-side print failure: the important event is deletion of the queued work. Windows exposes job deletion and queue purge as explicit control operations, and remote print protocols also include print-job control.
Trace the job lifetime
- Record the job ID returned by the submission path and use it consistently in subsequent logging.
- Correlate cancellation with SetJob job-control operations, printer purges, user actions, and print-server administration.
- Use queue change notifications or periodic EnumJobs/GetJob snapshots to determine when the job vanished.
- Do not automatically resubmit until you know whether deletion was intentional; blind retry can recreate a job the user explicitly cancelled.
Microsoft SetJob job controls · Printer change notifications · MS-RPRN print job control
Looking for a different code? Search another status or error code.