What does HRESULT 0x80093019 (OSS_UNIMPLEMENTED) mean?

 
Previous Next
OSS_CANT_OPEN_TRACE_WINDOW OSS_OID_DLL_NOT_LINKED

OSS_UNIMPLEMENTED

OSS_UNIMPLEMENTED (0x80093019) is an OSS ASN.1 runtime result for requested runtime feature is not implemented. The selected codec, representation, or operation reaches a feature that this runtime edition or version does not provide. Because type representation and encoding rule 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 runtime product, edition, and exact version, 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 requested runtime feature is not implemented 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 compiler directives affecting generated representation; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.

Evidence worth preserving

RecordDiagnostic value
type representation and encoding ruleLocates the concrete message, allocation, module, or API boundary
runtime product, edition, and exact versionSeparates payload-dependent behavior from build and process state
compiler directives affecting generated representationMakes the comparison reproducible without rewriting the original artifact

A controlled way to reproduce it

  1. reduce the schema to the unsupported construct
  2. check a newer supported runtime with identical input
  3. avoid changing wire rules merely to hide the result

Keep the original bytes or object graph unchanged while testing reduce the schema to the unsupported construct. A change in runtime product, edition, and exact version after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When compiler directives affecting generated representation 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

TYPE_NOT_SUPPORTED is tied to an ASN.1 type; UNIMPLEMENTED can identify a broader operation or representation feature.

Decision matrix

Controlled observationConclusion it supports
reduce the schema to the unsupported constructA changed outcome isolates the first proposed control instead of a blind retry
type representation and encoding rule differs between success and failureThe difference localizes the requested runtime feature is not implemented boundary before unrelated settings are changed
An independent decoder accepts the same artifactInspect generated schema, selected rules, ABI, and optional OSS modules before declaring the bytes invalid
A fresh control object changes the outcomeInvestigate 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 type representation and encoding rule can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use runtime product, edition, and exact version 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

Select a supported representation or runtime release and add a compatibility test before deployment. A recovery test built around reduce the schema to the unsupported construct 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 type representation and encoding rule now satisfies the codec contract.

Technical references


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