| 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
| Record | Diagnostic value |
|---|---|
| compiler banner embedded in generated artifacts | Locates the concrete message, allocation, module, or API boundary |
| loaded DLL path and file version | Separates payload-dependent behavior from build and process state |
| cross-compilation asn1dflt identity and architecture | Makes the comparison reproducible without rewriting the original artifact |
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
Keep the original bytes or object graph unchanged while testing rebuild a clean sample with one tool installation. A change in loaded DLL path and file version after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When cross-compilation asn1dflt identity and architecture points to one message, retain a cryptographic hash and the smallest safe sample instead of logging certificate, subscriber, credential, or private-key material.
Avoid the wrong workaround: the result
Changing the ASN.1 input data cannot resolve BAD_VERSION because decoding has not reached the message semantics.
Decision matrix
| Controlled observation | Conclusion it supports |
|---|---|
| rebuild a clean sample with one tool installation | A changed outcome isolates the first proposed control instead of a blind retry |
| compiler banner embedded in generated artifacts differs between success and failure | The difference localizes the generated-code and runtime version mismatch 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 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. A recovery test built around rebuild a clean sample with one tool installation 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 compiler banner embedded in generated artifacts 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.