| Previous | Next |
| D2DERR_NO_SUBPROPERTIES | D2DERR_PRINT_FORMAT_NOT_SUPPORTED |
D2DERR_PRINT_JOB_CLOSED
D2DERR_PRINT_JOB_CLOSED belongs to Direct2D print-control lifetime. AddPage or Close was called after the Direct2D print job had already been closed. The diagnostic goal for D2DERR_PRINT_JOB_CLOSED is to identify the first rejecting object and transition, not merely the final high-level symptom.
Locate the first rejecting layer
For D2DERR_PRINT_JOB_CLOSED, a Direct2D print control has a one-way lifecycle: pages are submitted while the job is open and Close ends that generation. When D2DERR_PRINT_JOB_CLOSED is returned, late asynchronous callbacks or duplicate cleanup can call AddPage or Close after termination even when the page content and printer are valid.
For D2DERR_PRINT_JOB_CLOSED, inspect the following boundary: print-control lifecycle and duplicate or late page submission.
Controlled reproduction
Serialize one AddPage and one Close, tag the job generation, and reject callbacks from completed jobs in the D2DERR_PRINT_JOB_CLOSED path. For D2DERR_PRINT_JOB_CLOSED, create a new print control for a new document instead of attempting to reopen the closed object.
- For D2DERR_PRINT_JOB_CLOSED, submit one page then close exactly once.
- When D2DERR_PRINT_JOB_CLOSED is returned, serialize close with page production.
- Reject late callbacks from an older job generation in the D2DERR_PRINT_JOB_CLOSED path.
- For D2DERR_PRINT_JOB_CLOSED, create a new print control for a new document.
Evidence that changes the diagnosis
| Record | Why it matters here |
|---|---|
| Job creation, AddPage, and Close timestamps | Preserving job creation, AddPage, and Close timestamps provides the evidence needed to test this distinction: this is a state-machine error, not a printer capability or page-content rendering error. |
| Thread and asynchronous print callback | For D2DERR_PRINT_JOB_CLOSED, recording thread and asynchronous print callback separates the Direct2D print-control lifetime boundary from a later wrapper symptom. |
| Spooler result and document generation | In D2DERR_PRINT_JOB_CLOSED diagnostics, recording spooler result and document generation ties the HRESULT to the Direct2D print-control lifetime boundary rather than to the final visible failure. |
| Object generation and cancellation state | Comparing object generation and cancellation state shows whether D2DERR_PRINT_JOB_CLOSED follows input, object state, or environment. |
Comparison tests
| Test | Interpretation | Hold constant |
|---|---|---|
| Same environment, reduced input | If D2DERR_PRINT_JOB_CLOSED disappears with a smaller faithful case, complexity within Direct2D print-control lifetime is implicated. | For D2DERR_PRINT_JOB_CLOSED, keep job creation, AddPage, and Close timestamps fixed while simplifying spooler result and document generation. |
| Same input, fresh object generation | If D2DERR_PRINT_JOB_CLOSED changes after rebuilding state, examine ownership across the caller’s object graph, custom effect or renderer, Direct2D validation layer, backing device, and deferred draw boundary. | For D2DERR_PRINT_JOB_CLOSED, place thread and asynchronous print callback on the timeline of the last successful transition. |
| Same operation on a controlled second path | If D2DERR_PRINT_JOB_CLOSED follows one environment, the failure is not explained by source data alone. | For D2DERR_PRINT_JOB_CLOSED, compare adapter and feature level, factory and device generations, target identity, debug-layer output, and thread ownership while preserving object generation and cancellation state. |
Misleading responses
This is a state-machine error, not a printer capability or page-content rendering error. For D2DERR_PRINT_JOB_CLOSED, do not respond with a universal render-target recreation loop unless the returned status specifically documents device-loss recovery; graph, property, numeric, lifetime, and print-state errors require correcting their contract.
Closure criteria
A correction for D2DERR_PRINT_JOB_CLOSED should let the operation at the Direct2D print-control lifetime boundary complete repeatedly under the original supported conditions. Repeat the control that begins with “Submit one page then close exactly once” and confirm that the following lifecycle step also succeeds. For D2DERR_PRINT_JOB_CLOSED, keep the original failing sample and one deliberate negative case so fallback cannot be mistaken for repair.
Technical references
When D2DERR_PRINT_JOB_CLOSED is returned, these references define the public API family, object model, or error list used to interpret this status.
- Microsoft: Direct2D error codes.
- Microsoft: Printing and command lists with Direct2D.
- Microsoft: Direct2D API overview.
Looking for a different code? Search another status or error code.