| Previous | Next |
| NS_E_INVALIDCALL_WHILE_ARCHIVAL_RUNNING | NS_E_PLUGIN_CLSID_INVALID |
NS_E_INVALIDPACKETSIZE
Diagnostic meaning beyond the standard text
For NS_E_INVALIDPACKETSIZE (0xC00D1B75), the actionable event is validation of the configured maximum packet size for encoded output.
Why the session can reach this point
The Encoder can expose an HTTP broadcast and can push to Windows Media Services. Packet sizing, publishing-point data and announcement generation are output-distribution concerns, separate from source capture and codec selection.
A stream can encode correctly to a file yet fail distribution because the broadcast sink or announcement metadata cannot represent the selected profile. One concrete way to reach the condition is that a configuration parser treats an empty field as zero or a byte count as kilobytes.
Decision path
- Record
0xC00D1B75, the Encoder version and the exact API call or property access that returned it. - Export the current
.wmeor.prxconfiguration, then capture numeric packet-size value, transport mode, profile bitrate and API that supplied the value. - Verify the broadcast and packet-output setup precondition without changing the source, profile and output sink at the same time.
- Run one controlled comparison that changes only the identified precondition: use a packet size in the range accepted by the selected output transport.
Codes with similar symptoms but different owners
| Result | Why it differs |
|---|---|
NS_E_CANNOT_GENERATE_BROADCAST_INFO_FOR_QUALITYVBR | announcement or stream-format generation cannot represent quality-based VBR output before encoding |
Safe recovery
Use a packet size in the range accepted by the selected output transport.
Do not change the source and codec while testing a distribution-only failure; first prove that the same profile writes a local file and preserve the output configuration.
Source material
Looking for a different code? Search another status or error code.