| Previous | Next |
| OSS_OPEN_TYPE_ERROR | OSS_CANT_CLOSE_TRACE_FILE |
OSS_MUTEX_NOT_CREATED
OSS_MUTEX_NOT_CREATED (0x8009302D) is an OSS ASN.1 runtime result for runtime synchronization primitive creation failed. The Windows runtime could not create the mutex used to serialize access to shared OSS state. Because native error captured when the mutex is created 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 process resource pressure and security context, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
What not to confuse it with: OSS_MUTEX_NOT_CREATED
ACCESS_SERIALIZATION_ERROR occurs while using shared state; MUTEX_NOT_CREATED says the guard itself was never established.
Locate the failing codec stage
At the runtime synchronization primitive creation failed 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 race between threads or modules; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Evidence worth preserving
- native error captured when the mutex is created
- process resource pressure and security context
- initialization race between threads or modules
A controlled way to reproduce it
- initialize the runtime before starting workers
- Repeat in a clean process under the same identity
- count handles during repeated load/unload cycles
Instrumentation
Where native error captured when the mutex is created can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use process resource pressure and security context together with OSS module paths and versions logged once per process so packaging differences can be correlated without flooding normal diagnostics.
Exit criteria: the result
Create and own the runtime context deterministically, fix resource or lifecycle leaks, and stress initialization under concurrency.
Technical references
Looking for a different code? Search another status or error code.