| Previous | Next |
| OSS_COMPARATOR_DLL_NOT_LINKED | OSS_MEM_MGR_DLL_NOT_LINKED |
OSS_COMPARATOR_CODE_NOT_LINKED
OSS_COMPARATOR_CODE_NOT_LINKED (0x80093025) is an OSS ASN.1 runtime result for comparator implementation omitted from the linked image. A comparison operation is requested, but the generated/static comparator code is absent from the executable or library. Because link map and dead-code elimination settings 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 generated comparator source list, 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 comparator implementation omitted from the linked image 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 symbol referenced by the failing type; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Evidence worth preserving
| Record | Diagnostic value |
|---|---|
| link map and dead-code elimination settings | Locates the concrete message, allocation, module, or API boundary |
| generated comparator source list | Separates payload-dependent behavior from build and process state |
| symbol referenced by the failing type | Makes the comparison reproducible without rewriting the original artifact |
A controlled way to reproduce it
- build a minimal target that calls the comparator
- disable whole-program elimination as an isolation step
- ensure generated sources are not from another schema revision
Keep the original bytes or object graph unchanged while testing build a minimal target that calls the comparator. A change in generated comparator source list after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When symbol referenced by the failing type 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
This code-path failure is distinct from COMPARATOR_DLL_NOT_LINKED, which points to dynamic module loading.
Decision matrix
| Controlled observation | Conclusion it supports |
|---|---|
| build a minimal target that calls the comparator | A changed outcome isolates the first proposed control instead of a blind retry |
| link map and dead-code elimination settings differs between success and failure | The difference localizes the comparator implementation omitted from the linked image 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 link map and dead-code elimination settings can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use generated comparator source list 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
Link the generated comparator implementation explicitly and add a post-link functional test. A recovery test built around build a minimal target that calls the comparator 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 link map and dead-code elimination settings 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.