| Previous | Next |
| OSS_BAD_ENCRULES | OSS_CANT_OPEN_TRACE_WINDOW |
OSS_UNAVAIL_ENCRULES
OSS_UNAVAIL_ENCRULES (0x80093017) is an OSS ASN.1 runtime result for recognized encoding rules not linked into the build. The requested rule set is known to the runtime but the generated/runtime modules needed to execute it were not included. Because requested rule and operation direction 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 compiler options used to generate code, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
Interpretation at runtime
At the recognized encoding rules not linked into the build 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 actual modules and static libraries linked into the process; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Keep the original bytes or object graph unchanged while testing switch temporarily to a rule known to be present. A change in compiler options used to generate code after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When actual modules and static libraries linked into the process points to one message, retain a cryptographic hash and the smallest safe sample instead of logging certificate, subscriber, credential, or private-key material.
Diagnostic record
| Record | Diagnostic value |
|---|---|
| requested rule and operation direction | Locates the concrete message, allocation, module, or API boundary |
| compiler options used to generate code | Separates payload-dependent behavior from build and process state |
| actual modules and static libraries linked into the process | Makes the comparison reproducible without rewriting the original artifact |
Small experiments with high signal
- switch temporarily to a rule known to be present
- inspect the link map rather than source project settings
- regenerate with the intended BER/DER/PER options
Avoid the wrong workaround: the result
A valid protocol cannot be silently encoded with another rule: BER, DER, and PER produce different wire representations and interoperability requirements.
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 requested rule and operation direction can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use compiler options used to generate code together with OSS module paths and versions logged once per process so packaging differences can be correlated without flooding normal diagnostics.
Decision matrix
| Controlled observation | Conclusion it supports |
|---|---|
| switch temporarily to a rule known to be present | A changed outcome isolates the first proposed control instead of a blind retry |
| requested rule and operation direction differs between success and failure | The difference localizes the recognized encoding rules not linked into the build 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 |
Proof of recovery: the result
Add the exact rule implementation, regenerate compatible code, and verify with an independent decoder. A recovery test built around switch temporarily to a rule known to be present 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 requested rule and operation direction 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.