| 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 exact codec boundary
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
| Record | Diagnostic value |
|---|---|
| native error captured when the mutex is created | Locates the concrete message, allocation, module, or API boundary |
| process resource pressure and security context | Separates payload-dependent behavior from build and process state |
| initialization race between threads or modules | Makes the comparison reproducible without rewriting the original artifact |
Keep the original bytes or object graph unchanged while testing initialize the runtime before starting workers. A change in process resource pressure and security context after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When initialization race between threads or modules points to one message, retain a cryptographic hash and the smallest safe sample instead of logging certificate, subscriber, credential, or private-key material.
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
Decision matrix
| Controlled observation | Conclusion it supports |
|---|---|
| initialize the runtime before starting workers | A changed outcome isolates the first proposed control instead of a blind retry |
| native error captured when the mutex is created differs between success and failure | The difference localizes the runtime synchronization primitive creation failed 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 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. A recovery test built around initialize the runtime before starting workers 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 native error captured when the mutex is created 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.