| Previous | Next |
| OSS_PDU_RANGE | OSS_DATA_ERROR |
OSS_MORE_INPUT
OSS_MORE_INPUT (0x80093004) is an OSS ASN.1 runtime result for premature end of encoded input. The decoder reaches the end of the supplied byte range before a complete PDU can be reconstructed. Because declared frame length and bytes actually received is central to this condition, Microsoft’s HRESULT range and the OSS Nokalva return-code documentation should be read together. Start the investigation by recording decoder offset at exhaustion, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
Where processing stopped
At the premature end of encoded input boundary, capture the first OSS function returning the value and note whether the operation was encode, decode, copy, compare, constraint validation, or trace setup. Preserve the selected PDU, encoding rules, and transport segmentation, base64, or file-read boundaries; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Facts that change the conclusion
| Record | Diagnostic value |
|---|---|
| declared frame length and bytes actually received | Locates the concrete message, allocation, module, or API boundary |
| decoder offset at exhaustion | Separates payload-dependent behavior from build and process state |
| transport segmentation, base64, or file-read boundaries | Makes the comparison reproducible without rewriting the original artifact |
Similar names, different faults: the result
A larger output allocation does not fix this condition; OSS_MORE_BUF concerns destination capacity, whereas this status concerns source completeness.
Isolation sequence
- decode the captured bytes with no transport layer involved
- append only the known missing segment and retry
- test a deliberately truncated message as a negative control
Instrumentation
Record the full 32-bit HRESULT and lower OSS return number together with operation direction, symbolic PDU, encoding rule, byte count, and generated-table identifier. Where declared frame length and bytes actually received can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use decoder offset at exhaustion together with OSS module paths and versions logged once per process so packaging differences can be correlated without flooding normal diagnostics.
Keep the original bytes or object graph unchanged while testing decode the captured bytes with no transport layer involved. A change in decoder offset at exhaustion after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When transport segmentation, base64, or file-read boundaries points to one message, retain a cryptographic hash and the smallest safe sample instead of logging certificate, subscriber, credential, or private-key material.
Decision matrix
| Controlled observation | Conclusion it supports |
|---|---|
| decode the captured bytes with no transport layer involved | A changed outcome isolates the first proposed control instead of a blind retry |
| declared frame length and bytes actually received differs between success and failure | The difference localizes the premature end of encoded input boundary before unrelated settings are changed |
| An independent decoder accepts the same artifact | Inspect generated schema, selected rules, ABI, and optional OSS modules before declaring the bytes invalid |
| A fresh control object changes the outcome | Investigate initialization, lifecycle, allocator ownership, configuration mutation, and concurrent access |
Completion check: the result
Preserve framing across reads and invoke the decoder only with the length promised by the surrounding protocol. A recovery test built around decode the captured bytes with no transport layer involved should replay the same operation under the same schema and encoding rule, retain one deliberately invalid control, and verify ownership and cleanup after both outcomes. Success after an unexamined retry is not proof that declared frame length and bytes actually received now satisfies the codec contract.
Technical references
- Microsoft: OSS ASN.1 HRESULT definitions
- OSS Nokalva: encoder/decoder return codes
- OSS Nokalva: runtime functions and control initialization
- Relevant ASN.1 specification or runtime detail
Looking for a different code? Search another status or error code.