Site icon EfmSoft

What does HRESULT 0xC00D1B77 (NS_E_UNSUPPORTED_ARCHIVETYPE) mean?

 
Previous Next
NS_E_PLUGIN_CLSID_INVALID NS_E_UNSUPPORTED_ARCHIVEOPERATION

NS_E_UNSUPPORTED_ARCHIVETYPE

Diagnostic meaning beyond the standard text

For NS_E_UNSUPPORTED_ARCHIVETYPE (0xC00D1B77), the actionable event is selection of an archive type not implemented by the Encoder output component. Keep the result producing boundary attached to the original Encoder callback or COM call.

Why the session can reach this point

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.

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. One concrete way to reach the condition is that configuration from a different SDK generation contains an unknown archive enum value. The result test should therefore preserve the object generation and numeric settings, not just a screenshot of the final dialog.

Trace fields with diagnostic value

FieldWhat to preserve
Decisive valuesarchive-type enum, Encoder version and the object on which AutoArchive is set
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 archivetype boundary

Decision matrix

ObservationHow to interpret it
Observation that supports itThe decisive evidence is archive-type enum, Encoder version and the object on which AutoArchive is set. It confirms selection of an archive type not implemented by the Encoder output component in the same object generation.
Observation that points to an earlier failureThe recorded values satisfy the unsupported archivetype 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 archive type not implemented by the Encoder output component), but a codec, archive or broadcast sink then fails in a subsequent stage.
Verification after correctionApply this isolated change: select a supported local archive type for this Encoder version. The original unsupported archivetype 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 archive type not implemented by the Encoder output component. In the representative case where configuration from a different SDK generation contains an unknown archive enum value, keep the first failing call and its object identity so a later wrapper cannot replace the unsupported archivetype evidence.

Decision path

  1. Record 0xC00D1B77, 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 enum, Encoder version and the object on which AutoArchive is set.
  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: select a supported local archive type for this Encoder version.
  5. After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier unsupported archivetype state.

Codes with similar symptoms but different owners

ResultWhy it is a different boundary
NS_E_UNSUPPORTED_ARCHIVEOPERATIONselection of an auto-archive operation invalid for the chosen archive type
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

Safe recovery

Resolve the producing condition by ensuring that you select a supported local archive type for this Encoder version. Then rebuild only the portion of the Encoder graph affected by it and verify the original call.

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.

Source material


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

Exit mobile version