| Previous | Next |
| OSS_REAL_CODE_NOT_LINKED | OSS_COPIER_DLL_NOT_LINKED |
OSS_OUT_OF_RANGE
OSS_OUT_OF_RANGE (0x80093021) is an OSS ASN.1 runtime result for runtime parameter outside its permitted range. An API parameter is numerically valid at the machine level but falls outside the range accepted for that runtime option or operation. Because function name and parameter index 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 value before narrowing or sign conversion, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
What not to confuse it with: OSS_OUT_OF_RANGE
Despite the generic Windows text that groups several OSS values as link errors, OSS documentation identifies this return code as a parameter-range failure.
Locate the exact codec boundary
At the runtime parameter outside its permitted range 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 documented minimum, maximum, and sentinel values; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Evidence worth preserving
| Record | Diagnostic value |
|---|---|
| function name and parameter index | Locates the concrete message, allocation, module, or API boundary |
| value before narrowing or sign conversion | Separates payload-dependent behavior from build and process state |
| documented minimum, maximum, and sentinel values | Makes the comparison reproducible without rewriting the original artifact |
Keep the original bytes or object graph unchanged while testing test both legal boundaries. A change in value before narrowing or sign conversion after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When documented minimum, maximum, and sentinel values points to one message, retain a cryptographic hash and the smallest safe sample instead of logging certificate, subscriber, credential, or private-key material.
A controlled way to reproduce it
- test both legal boundaries
- remove implicit casts at the call site
- assert units such as bytes versus bits
Decision matrix
| Controlled observation | Conclusion it supports |
|---|---|
| test both legal boundaries | A changed outcome isolates the first proposed control instead of a blind retry |
| function name and parameter index differs between success and failure | The difference localizes the runtime parameter outside its permitted range 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 function name and parameter index can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use value before narrowing or sign conversion 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
Correct the caller’s range and units, then keep explicit lower-, upper-, and out-of-range tests. A recovery test built around test both legal boundaries 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 function name and parameter index 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.