| Previous | Next |
| OSS_DATA_ERROR | OSS_BAD_VERSION |
OSS_BAD_ARG
OSS_BAD_ARG (0x80093006) is an OSS ASN.1 runtime result for invalid runtime API argument. At least one call parameter violates the OSS runtime contract, commonly because a required pointer is null or a length, selector, or flag is inconsistent. Because function name and complete nonsecret argument metadata 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 pointer nullness and buffer-length pairs, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
Neighboring statuses: OSS_BAD_ARG
BAD_ARG is detected at the public call boundary; BAD_PTR more often describes a broken pointer inside the value graph being encoded.
What the return code narrows down
At the invalid runtime API argument 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 initialization state of the control object; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Test one variable at a time
- Reduce the call to a documented minimal example
- Validate lengths before crossing the DLL boundary
- enable compiler and page-heap checks in a test process
Build a useful capture
- function name and complete nonsecret argument metadata
- pointer nullness and buffer-length pairs
- initialization state of the control object
Instrumentation
Where function name and complete nonsecret argument metadata can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use pointer nullness and buffer-length pairs together with OSS module paths and versions logged once per process so packaging differences can be correlated without flooding normal diagnostics.
Verify the repair: the result
Repair the call contract and add assertions immediately before the runtime invocation.
Technical references
Looking for a different code? Search another status or error code.