| Previous | Next |
| OSS_MORE_INPUT | OSS_BAD_ARG |
OSS_DATA_ERROR
OSS_DATA_ERROR (0x80093005) is an OSS ASN.1 runtime result for encoded octets rejected as invalid. The runtime can read the buffer but the tag, length, value, or encoding-rule requirements do not form a valid value for the selected schema. Because first failing offset and nearby octets 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 selected BER, DER, PER, or other rule set, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
Locate the exact codec boundary
At the encoded octets rejected as invalid 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 independent decoder result against the same schema; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Keep the original bytes or object graph unchanged while testing separate transport decoding from ASN.1 decoding. A change in selected BER, DER, PER, or other rule set after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When independent decoder result against the same schema points to one message, retain a cryptographic hash and the smallest safe sample instead of logging certificate, subscriber, credential, or private-key material.
Evidence worth preserving
| Record | Diagnostic value |
|---|---|
| first failing offset and nearby octets | Locates the concrete message, allocation, module, or API boundary |
| selected BER, DER, PER, or other rule set | Separates payload-dependent behavior from build and process state |
| independent decoder result against the same schema | Makes the comparison reproducible without rewriting the original artifact |
A controlled way to reproduce it
- separate transport decoding from ASN.1 decoding
- try one known-good sample from the same producer
- compare schema revision before modifying bytes
What not to confuse it with: the result
This broad data status should not be replaced by a certificate-chain diagnosis: trust evaluation starts only after the object decodes.
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 first failing offset and nearby octets can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use selected BER, DER, PER, or other rule set together with OSS module paths and versions logged once per process so packaging differences can be correlated without flooding normal diagnostics.
Decision matrix
| Controlled observation | Conclusion it supports |
|---|---|
| separate transport decoding from ASN.1 decoding | A changed outcome isolates the first proposed control instead of a blind retry |
| first failing offset and nearby octets differs between success and failure | The difference localizes the encoded octets rejected as invalid 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 |
Exit criteria: the result
Fix the producer, framing, or schema mismatch and keep the original binary as regression evidence. A recovery test built around separate transport decoding from ASN.1 decoding 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 first failing offset and nearby octets 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.