| Previous | Next |
| OSS_BAD_TIME | OSS_MEM_ERROR |
OSS_INDEFINITE_NOT_SUPPORTED
OSS_INDEFINITE_NOT_SUPPORTED (0x8009300D) is an OSS ASN.1 runtime result for indefinite-length BER encountered on an unsupported path. The input uses BER indefinite-length encoding, but the selected runtime mode or generated decoder accepts only definite lengths. Because outer and nested length 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 whether DER or a constrained decoder was requested, 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 indefinite-length BER encountered on an unsupported path 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 position of end-of-contents markers; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Evidence worth preserving
| Record | Diagnostic value |
|---|---|
| outer and nested length octets | Locates the concrete message, allocation, module, or API boundary |
| whether DER or a constrained decoder was requested | Separates payload-dependent behavior from build and process state |
| position of end-of-contents markers | Makes the comparison reproducible without rewriting the original artifact |
A controlled way to reproduce it
- re-encode the value with definite lengths
- decode a known definite-length equivalent
- confirm the protocol actually permits BER rather than DER
Keep the original bytes or object graph unchanged while testing re-encode the value with definite lengths. A change in whether DER or a constrained decoder was requested after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When position of end-of-contents markers points to one message, retain a cryptographic hash and the smallest safe sample instead of logging certificate, subscriber, credential, or private-key material.
What not to confuse it with: the result
DER requires definite lengths, so enabling generic BER is not a valid workaround when the surrounding profile mandates DER.
Decision matrix
| Controlled observation | Conclusion it supports |
|---|---|
| re-encode the value with definite lengths | A changed outcome isolates the first proposed control instead of a blind retry |
| outer and nested length octets differs between success and failure | The difference localizes the indefinite-length BER encountered on an unsupported path 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 |
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 outer and nested length octets can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use whether DER or a constrained decoder was requested together with OSS module paths and versions logged once per process so packaging differences can be correlated without flooding normal diagnostics.
Exit criteria: the result
Make producer and consumer agree on the required encoding rules; do not merely strip end-of-contents bytes. A recovery test built around re-encode the value with definite lengths 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 outer and nested length 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.