| Previous | Next |
| OSS_CONSTRAINT_VIOLATED | OSS_ACCESS_SERIALIZATION_ERROR |
OSS_FATAL_ERROR
OSS_FATAL_ERROR (0x80093012) is an OSS ASN.1 runtime result for unrecoverable internal runtime state. The codec reports a serious internal failure, commonly after memory corruption or a broken generated/runtime combination. Because first failure in the process, not only the final HRESULT 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 full dump with loaded modules and symbols, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
Neighboring statuses: OSS_FATAL_ERROR
Do not classify FATAL_ERROR as ordinary invalid input unless a minimal malformed sample reproducibly triggers it without prior corruption.
What the return code narrows down
At the unrecoverable internal runtime state 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 recent writes near codec control and value objects; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Test one variable at a time
- reproduce in a clean process with one PDU
- run memory diagnostics before retry loops
- verify generated files and runtime version as a set
Build a useful capture
| Record | Diagnostic value |
|---|---|
| first failure in the process, not only the final HRESULT | Locates the concrete message, allocation, module, or API boundary |
| full dump with loaded modules and symbols | Separates payload-dependent behavior from build and process state |
| recent writes near codec control and value objects | Makes the comparison reproducible without rewriting the original artifact |
Keep the original bytes or object graph unchanged while testing reproduce in a clean process with one PDU. A change in full dump with loaded modules and symbols after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When recent writes near codec control and value objects points to one message, retain a cryptographic hash and the smallest safe sample instead of logging certificate, subscriber, credential, or private-key material.
Decision matrix
| Controlled observation | Conclusion it supports |
|---|---|
| reproduce in a clean process with one PDU | A changed outcome isolates the first proposed control instead of a blind retry |
| first failure in the process, not only the final HRESULT differs between success and failure | The difference localizes the unrecoverable internal runtime state 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 first failure in the process, not only the final HRESULT can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use full dump with loaded modules and symbols 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
Resolve the underlying corruption or binary mismatch and require repeated clean-process success before closing the incident. A recovery test built around reproduce in a clean process with one PDU 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 first failure in the process, not only the final HRESULT 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.