| Previous | Next |
| NS_E_NO_SCRIPT_STREAM | NS_E_INVALIDPACKETSIZE |
NS_E_INVALIDCALL_WHILE_ARCHIVAL_RUNNING
Where the Encoder produces this result
0xC00D1B74 (NS_E_INVALIDCALL_WHILE_ARCHIVAL_RUNNING) identifies attempt to alter archive configuration while the archive sink is active. This is an Encoder validation error; a later “cannot start encoding” dialog can hide the original HRESULT.
WMEncoder exposes configuration, preparation, running, paused, stopped and archival states. Properties that alter graph topology are normally set before Start, while statistics and some control operations are meaningful only after a session reaches the matching state.
What has already succeeded
The same method can be valid in one encoder state and rejected in another without any file, codec or network defect. For example, rotation code changes LocalFileName before ending the current archive segment. Reproduce the condition at the Encoder object that returned the HRESULT rather than treating it as a general codec or operating-system failure.
A controlled diagnostic sequence
- Record
0xC00D1B74, the Encoder version and the exact API call or property access that returned it. - Export the current
.wmeor.prxconfiguration, then capture archive state, method/property name, output file and callback that issued the change. - Verify the encoder state-machine sequencing precondition without changing the source, profile and output sink at the same time.
- Run one controlled comparison that changes only the identified precondition: stop the archive cleanly before changing its destination or mode.
Nearby HRESULTs that mean something else
| Result | Why it differs |
|---|---|
NS_E_NO_ACTIVE_SOURCEGROUP | an operation that requires SourceGroupCollection.Active when no group is selected |
NS_E_SOURCEGROUP_NOTPREPARED | activation or start of a source group that has not completed PrepareToEncode |
NS_E_INVALIDCALL_WHILE_ENCODER_RUNNING | attempt to change a topology-affecting property after WMEncoder.Start |
Corrective action at the right layer
Do not hide the ordering problem behind unconditional retries; log the transition sequence and make the operation occur at the documented lifecycle point.
Technical references
Looking for a different code? Search another status or error code.