| Previous | Next |
| OSS_MUTEX_NOT_CREATED | CRYPT_E_ASN1_ERROR |
OSS_CANT_CLOSE_TRACE_FILE
OSS_CANT_CLOSE_TRACE_FILE (0x8009302E) is an OSS ASN.1 runtime result for trace destination failed during close. The runtime cannot close or finalize the configured trace file, so buffered diagnostics may be incomplete even if earlier writes appeared successful. Because native close or flush error 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 filesystem, removable-media, and network-share state, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
What the return code narrows down
At the trace destination failed during close 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 ownership of the file handle at shutdown; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Build a useful capture
| Record | Diagnostic value |
|---|---|
| native close or flush error | Locates the concrete message, allocation, module, or API boundary |
| filesystem, removable-media, and network-share state | Separates payload-dependent behavior from build and process state |
| ownership of the file handle at shutdown | Makes the comparison reproducible without rewriting the original artifact |
Neighboring statuses: the result
Successful opening does not guarantee durable trace output; close can reveal delayed I/O, quota, or handle-lifecycle errors.
Test one variable at a time
- flush and close on the same thread in a test
- use a local file as a control
- ensure no plugin closes the handle behind the runtime
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 close or flush error can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use filesystem, removable-media, and network-share state together with OSS module paths and versions logged once per process so packaging differences can be correlated without flooding normal diagnostics.
Keep the original bytes or object graph unchanged while testing flush and close on the same thread in a test. A change in filesystem, removable-media, and network-share state after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When ownership of the file handle at shutdown 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 |
|---|---|
| flush and close on the same thread in a test | A changed outcome isolates the first proposed control instead of a blind retry |
| native close or flush error differs between success and failure | The difference localizes the trace destination failed during close 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 |
Verify the repair: the result
Preserve the underlying OS failure, move tracing to reliable storage, and verify the final bytes are readable after shutdown. A recovery test built around flush and close on the same thread in a test 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 close or flush error 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.