| Previous | Next |
| OSS_CANT_OPEN_TRACE_FILE | OSS_TABLE_MISMATCH |
OSS_TRACE_FILE_ALREADY_OPEN
OSS_TRACE_FILE_ALREADY_OPEN (0x8009301C) is an OSS ASN.1 runtime result for duplicate trace-file open request. The control context already owns an open trace destination when the application tries to open it again. Because open and close call sequence 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 control object identity associated with the handle, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
Where processing stopped
At the duplicate trace-file open request 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 configuration reload and retry timestamps; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Facts that change the conclusion
| Record | Diagnostic value |
|---|---|
| open and close call sequence | Locates the concrete message, allocation, module, or API boundary |
| control object identity associated with the handle | Separates payload-dependent behavior from build and process state |
| configuration reload and retry timestamps | Makes the comparison reproducible without rewriting the original artifact |
Similar names, different faults: the result
This is a lifecycle error, unlike CANT_OPEN_TRACE_FILE, which indicates the first open could not acquire a file.
Isolation sequence
- make trace setup idempotent
- close the old sink before replacing it
- serialize configuration changes in a stress test
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 open and close call sequence can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use control object identity associated with the handle 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 make trace setup idempotent. A change in control object identity associated with the handle after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When configuration reload and retry timestamps 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 |
|---|---|
| make trace setup idempotent | A changed outcome isolates the first proposed control instead of a blind retry |
| open and close call sequence differs between success and failure | The difference localizes the duplicate trace-file open request 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 |
Completion check: the result
Define one owner for trace setup and verify reopen behavior during configuration reload. A recovery test built around make trace setup idempotent 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 open and close call sequence 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.