| Previous | Next |
| OSS_FATAL_ERROR | OSS_NULL_TBL |
OSS_ACCESS_SERIALIZATION_ERROR
OSS_ACCESS_SERIALIZATION_ERROR (0x80093013) is an OSS ASN.1 runtime result for failed serialization of shared OSS runtime state. On the legacy Windows runtime path, access to global data could not be serialized correctly in a multithreaded process. Because thread IDs entering the codec concurrently 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 lifetime and sharing of OssControl instances, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
Interpretation at runtime
At the failed serialization of shared OSS 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 initialization and shutdown ordering; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Diagnostic record
- thread IDs entering the codec concurrently
- lifetime and sharing of OssControl instances
- initialization and shutdown ordering
Small experiments with high signal
- run one call at a time as an isolation control
- give each supported context the documented ownership model
- remove codec teardown while worker calls remain active
Avoid the wrong workaround: the result
This code concerns synchronization around runtime-global state; MUTEX_NOT_CREATED identifies failure to create the primitive used for that serialization.
Instrumentation
Where thread IDs entering the codec concurrently can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use lifetime and sharing of OssControl instances 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
Establish deterministic initialization, call ownership, and shutdown, then stress the same workload with concurrency enabled.
Technical references
Looking for a different code? Search another status or error code.