| 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.
Diagnostic record
- requested rule and operation direction
- compiler options used to generate code
- actual modules and static libraries linked into the process
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
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.
Proof of recovery: the result
Add the exact rule implementation, regenerate compatible code, and verify with an independent decoder.
Technical references
Looking for a different code? Search another status or error code.