| 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
| Record | Diagnostic value |
|---|---|
| copy API used and source type | Locates the concrete message, allocation, module, or API boundary |
| copier module path, architecture, and version | Separates payload-dependent behavior from build and process state |
| ownership model expected for nested allocations | Makes the comparison reproducible without rewriting the original artifact |
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
- compare with a schema-aware encode/decode copy only as a test
- inspect loader diagnostics
- verify deep-copy behavior on pointer-bearing fields
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 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.
Keep the original bytes or object graph unchanged while testing compare with a schema-aware encode/decode copy only as a test. A change in copier module path, architecture, and version after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When ownership model expected for nested allocations points to one message, retain a cryptographic hash and the smallest safe sample instead of logging certificate, subscriber, credential, or private-key material.
Decision matrix
| Controlled observation | Conclusion it supports |
|---|---|
| compare with a schema-aware encode/decode copy only as a test | A changed outcome isolates the first proposed control instead of a blind retry |
| copy API used and source type differs between success and failure | The difference localizes the generated-value copier DLL absent 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 |
Verify the repair: the result
Deploy the matching copier module and verify that source and copy can be freed independently. A recovery test built around compare with a schema-aware encode/decode copy only as a test 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 copy API used and source type 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.