What does HRESULT 0x80093022 (OSS_COPIER_DLL_NOT_LINKED) mean?

 
Previous Next
OSS_OUT_OF_RANGE OSS_CONSTRAINT_DLL_NOT_LINKED

OSS_COPIER_DLL_NOT_LINKED

OSS_COPIER_DLL_NOT_LINKED (0x80093022) is an OSS ASN.1 runtime result for generated-value copier DLL absent. The application requests an OSS value-copy operation but the optional copier module was not packaged or loaded. Because copy API used and source type 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 copier module path, architecture, and version, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.

What the return code narrows down

At the generated-value copier DLL absent 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 ownership model expected for nested allocations; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.

Build a useful capture

  • copy API used and source type
  • copier module path, architecture, and version
  • ownership model expected for nested allocations

Neighboring statuses: the result

A raw memcpy is not a safe production replacement for a generated deep copier because nested strings and lists have separate ownership.

Test one variable at a time

  1. Compare with a schema-aware encode/decode copy only as a test
  2. Inspect loader diagnostics
  3. Verify deep-copy behavior on pointer-bearing fields

Instrumentation

Where copy API used and source type can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use copier module path, architecture, and version together with OSS module paths and versions logged once per process so packaging differences can be correlated without flooding normal diagnostics.

Verify the repair: the result

Deploy the matching copier module and verify that source and copy can be freed independently.

Technical references


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