| 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
- native close or flush error
- filesystem, removable-media, and network-share state
- ownership of the file handle at shutdown
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
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.
Verify the repair: the result
Preserve the underlying OS failure, move tracing to reliable storage, and verify the final bytes are readable after shutdown.
Technical references
Looking for a different code? Search another status or error code.