Site icon EfmSoft

What does HRESULT 0xC00D1B78 (NS_E_UNSUPPORTED_ARCHIVEOPERATION) mean?

 
Previous Next
NS_E_UNSUPPORTED_ARCHIVETYPE NS_E_ARCHIVE_FILENAME_NOTSET

NS_E_UNSUPPORTED_ARCHIVEOPERATION

Where the Encoder produces this result

0xC00D1B78 (NS_E_UNSUPPORTED_ARCHIVEOPERATION) identifies selection of an auto-archive operation invalid for the chosen archive type. 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 unsupported archiveoperation case, an automatic stop operation is configured for a mode that never opened an archive. 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

FieldWhat to preserve
Decisive valuesarchive type and operation enum pair, active group and current archive state
Producing objectIWMEncFile.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 correlationthe same source-group generation, audience index, object identity and callback sequence that produced this result
Lower-level evidencethe first COM, driver, file-system or codec HRESULT observed before the Encoder mapped the condition to this result
Controlled comparisona known-good session that changes only the setting named in the unsupported archiveoperation boundary

How to read the next observation

ObservationHow to interpret it
Observation that supports itThe decisive evidence is archive type and operation enum pair, active group and current archive state. It confirms selection of an auto-archive operation invalid for the chosen archive type in the same object generation.
Observation that points to an earlier failureThe recorded values satisfy the unsupported archiveoperation rule, but a source, driver, COM activation or file operation returns a different HRESULT first.
Observation that points to a later failureThe Encoder passes this boundary (selection of an auto-archive operation invalid for the chosen archive type), but a codec, archive or broadcast sink then fails in a subsequent stage.
Verification after correctionApply this isolated change: use a start/stop operation supported by that archive type and lifecycle state. The original unsupported archiveoperation 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 selection of an auto-archive operation invalid for the chosen archive type. In the representative case where an automatic stop operation is configured for a mode that never opened an archive, keep the first failing call and its object identity so a later wrapper cannot replace the unsupported archiveoperation evidence.

A controlled diagnostic sequence

  1. Record 0xC00D1B78, it, the Encoder version and the exact API call or property access that returned it.
  2. Export the current .wme or .prx configuration, then capture archive type and operation enum pair, active group and current archive state.
  3. verify the archive and local-output configuration precondition without changing the source, profile and output sink at the same time.
  4. Run one controlled comparison in which only this condition changes: use a start/stop operation supported by that archive type and lifecycle state.
  5. After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier unsupported archiveoperation state.

Nearby HRESULTs that mean something else

ResultWhy it is a different boundary
NS_E_UNSUPPORTED_ARCHIVETYPEselection of an archive type not implemented by the Encoder output component
NS_E_ARCHIVE_FILENAME_NOTSETstarting local archival without a destination file name
NS_E_NOTARCHIVINGan archive-only operation issued when no archive sink is active

Corrective action at the right layer

The focused correction is to use a start/stop operation supported by that archive type and lifecycle state. A retry is useful only after the recorded unsupported archiveoperation 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


Looking for a different code? Search another status or error code.

Exit mobile version