| Previous | Next |
| OSS_BAD_ARG | OSS_OUT_MEMORY |
OSS_BAD_VERSION
OSS_BAD_VERSION (0x80093007) is an OSS ASN.1 runtime result for generated-code and runtime version mismatch. The compiler-generated files, control data, target defaults, or runtime library are from incompatible OSS tool builds. Because compiler banner embedded in generated artifacts 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 loaded DLL path and file version, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
Interpretation at runtime
At the generated-code and runtime version mismatch 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 cross-compilation asn1dflt identity and architecture; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Diagnostic record
- compiler banner embedded in generated artifacts
- loaded DLL path and file version
- cross-compilation asn1dflt identity and architecture
Small experiments with high signal
- rebuild a clean sample with one tool installation
- Inspect the actual loaded module rather than PATH alone
- remove stale generated objects before relinking
Avoid the wrong workaround: the result
Changing the ASN.1 input data cannot resolve BAD_VERSION because decoding has not reached the message semantics.
Instrumentation
Where compiler banner embedded in generated artifacts can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use loaded DLL path and file version 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
Recompile and relink every generated unit against the intended runtime, then verify the loaded binary set.
Technical references
Looking for a different code? Search another status or error code.