| Previous | Next |
| NS_E_UNSUPPORTED_ARCHIVEOPERATION | NS_E_SOURCEGROUP_NOTPREPARED |
NS_E_ARCHIVE_FILENAME_NOTSET
Where the Encoder produces this result
0xC00D1B79 (NS_E_ARCHIVE_FILENAME_NOTSET) identifies starting local archival without a destination file name. The important diagnostic boundary is the Encoder object that validates this state; a later “cannot start encoding” dialog can hide that more precise origin.
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.
What has already succeeded
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. In a representative archive filename notset case, the UI displays a default name that automation never commits to the IWMEncFile object. The result observation should be tested at the producing object instead of being treated as a general codec or operating-system failure.
State snapshot to capture
| Field | What to preserve |
|---|---|
| Decisive values | IWMEncFile.LocalFileName, auto-archive settings, resolved directory and environment-variable expansion |
| 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 archive filename notset boundary |
How to read the next observation
| Observation | How to interpret it |
|---|---|
| Observation that supports it | The decisive evidence is IWMEncFile.LocalFileName, auto-archive settings, resolved directory and environment-variable expansion. It confirms starting local archival without a destination file name in the same object generation. |
| Observation that points to an earlier failure | The recorded values satisfy the archive filename notset 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 (starting local archival without a destination file name), but a codec, archive or broadcast sink then fails in a subsequent stage. |
| Verification after correction | Apply this isolated change: set an absolute writable archive path before starting archival. The original archive filename notset 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 starting local archival without a destination file name. In the representative case where the UI displays a default name that automation never commits to the IWMEncFile object, keep the first failing call and its object identity so a later wrapper cannot replace the archive filename notset evidence.
A controlled diagnostic sequence
- Record
0xC00D1B79, it, the Encoder version and the exact API call or property access that returned it. - Export the current
.wmeor.prxconfiguration, then capture IWMEncFile. - 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: set an absolute writable archive path before starting archival.
- After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier archive filename notset state.
Nearby HRESULTs that mean something else
| Result | Why it is a different boundary |
|---|---|
NS_E_UNSUPPORTED_ARCHIVEOPERATION | selection of an auto-archive operation invalid for the chosen archive type |
NS_E_NOTARCHIVING | an archive-only operation issued when no archive sink is active |
NS_E_UNSUPPORTED_ARCHIVETYPE | selection of an archive type not implemented by the Encoder output component |
Corrective action at the right layer
The focused correction is to set an absolute writable archive path before starting archival. A retry is useful only after the recorded archive filename notset precondition changes.
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.
Technical references
- WMEncoder.File and archive output.
- IWMEncStatistics.IndexerStats.
- WMEncoder.Broadcast.
- WMEncoder.Flush.
Looking for a different code? Search another status or error code.