What does HRESULT 0x8009300D (OSS_INDEFINITE_NOT_SUPPORTED) mean?

 
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 failing codec stage

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

  • outer and nested length octets
  • whether DER or a constrained decoder was requested
  • position of end-of-contents markers

A controlled way to reproduce it

  1. re-encode the value with definite lengths
  2. decode a known definite-length equivalent
  3. Confirm the protocol actually permits BER rather than DER

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.

Instrumentation

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.

Technical references


Looking for a different code? Search another status or error code.