| Previous | Next |
| NS_E_NOSTATSAVAILABLE | NS_E_INVALIDCALL_WHILE_ENCODER_STOPPED |
NS_E_NOTARCHIVING
The failing boundary in the Encoder object model
The useful reading of NS_E_NOTARCHIVING (0xC00D1B7E) is not merely the standard message shown above. It locates an archive-only operation issued when no archive sink is active inside archive and local-output configuration.
Archive output is configured separately from source capture and broadcast delivery in a session that returns this result. The encoder validates archive type, operation, destination path, collision with input files, available disk space and whether an archive session is actually active at the notarchiving checkpoint.
Evidence that separates this code from a wrapper error
A live broadcast may continue while local archival fails, because the broadcast sink and archive sink have different paths and state in a session that returns this result. For example, status code attempts to stop archiving after a previous start failed. Preserve the result distinction before a UI layer converts the result into a broad start, capture or profile failure.
| Field | What to preserve |
|---|---|
| Decisive values | archive state, active group, auto-archive setting and last archive start/stop event |
| Producing object | IWMEncFile.LocalFileName, auto-archive type and operation, canonical input/output paths, free and reserved disk space, temporary record queue, archive state and file-system HRESULT |
| Session correlation | the same source-group generation, audience index, object identity and callback sequence that produced this result |
| Lower-level evidence | the first COM, driver, file-system or codec HRESULT observed before the Encoder mapped the condition to this result |
| Controlled comparison | a known-good session that changes only the setting named in the notarchiving boundary |
Interpret the next measurement
| Observation | How to interpret it |
|---|---|
| Observation that supports it | The decisive evidence is archive state, active group, auto-archive setting and last archive start/stop event. It confirms an archive-only operation issued when no archive sink is active in the same object generation. |
| Observation that points to an earlier failure | The recorded values satisfy the notarchiving rule, but a source, driver, COM activation or file operation returns a different HRESULT first. |
| Observation that points to a later failure | The Encoder passes this boundary (an archive-only operation issued when no archive sink is active), but a codec, archive or broadcast sink then fails in a subsequent stage. |
| Verification after correction | Apply this isolated change: start an archive before the operation or remove the archive-only call. The original notarchiving call should then advance past the same checkpoint. |
The operational impact of it is limited to the archive and local-output configuration transition that owns an archive-only operation issued when no archive sink is active. In the representative case where status code attempts to stop archiving after a previous start failed, keep the first failing call and its object identity so a later wrapper cannot replace the notarchiving evidence.
Test the condition without rewriting the session
- Record
0xC00D1B7E, it, the Encoder version and the exact API call or property access that returned it. - Export the current
.wmeor.prxconfiguration, then capture archive state, active group, auto-archive setting and last archive start/stop event. - verify the archive and local-output configuration precondition without changing the source, profile and output sink at the same time.
- Run one controlled comparison in which only this condition changes: start an archive before the operation or remove the archive-only call.
- After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier notarchiving state.
Interpret neighboring results carefully
| Result | Why it is a different boundary |
|---|---|
NS_E_ARCHIVE_FILENAME_NOTSET | starting local archival without a destination file name |
NS_E_ARCHIVE_SAME_AS_INPUT | canonical path comparison detects that archive output would overwrite an input |
NS_E_UNSUPPORTED_ARCHIVEOPERATION | selection of an auto-archive operation invalid for the chosen archive type |
Resolution and verification
The direct repair for this occurrence is to start an archive before the operation or remove the archive-only call. Recreate the affected source group, profile or output object, repeat the same operation, and confirm that the first failing HRESULT no longer comes from the notarchiving checkpoint.
Do not overwrite or delete the partial archive before recording its path, size and timestamps; those details distinguish naming, disk-space and writer failures in a session that returns it.
References for the boundary
- WMEncoder.File and archive output.
- IWMEncStatistics.IndexerStats.
- WMEncoder.Broadcast.
- WMEncoder.Flush.
Looking for a different code? Search another status or error code.