| Previous | Next |
| OSS_BAD_PTR | OSS_INDEFINITE_NOT_SUPPORTED |
OSS_BAD_TIME
OSS_BAD_TIME (0x8009300C) is an OSS ASN.1 runtime result for invalid ASN.1 or XML time value. A UTCTime, GeneralizedTime, or XML time representation violates the lexical or calendar rules understood by the runtime. Because original time text and ASN.1 type 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 timezone suffix, fractional seconds, and precision, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
Similar names, different faults: OSS_BAD_TIME
This is not a certificate-expiration decision; it says the time value itself cannot be represented or parsed correctly.
Where processing stopped
At the invalid ASN.1 or XML time value 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 calendar validity including leap day and field ranges; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Isolation sequence
- round-trip a known UTC boundary value
- test the same instant without optional fractions
- compare the protocol profile with the generic ASN.1 allowance
Facts that change the conclusion
| Record | Diagnostic value |
|---|---|
| original time text and ASN.1 type | Locates the concrete message, allocation, module, or API boundary |
| timezone suffix, fractional seconds, and precision | Separates payload-dependent behavior from build and process state |
| calendar validity including leap day and field ranges | Makes the comparison reproducible without rewriting the original artifact |
Keep the original bytes or object graph unchanged while testing round-trip a known UTC boundary value. A change in timezone suffix, fractional seconds, and precision after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When calendar validity including leap day and field ranges 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 |
|---|---|
| round-trip a known UTC boundary value | A changed outcome isolates the first proposed control instead of a blind retry |
| original time text and ASN.1 type differs between success and failure | The difference localizes the invalid ASN.1 or XML time value 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 original time text and ASN.1 type can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use timezone suffix, fractional seconds, and precision together with OSS module paths and versions logged once per process so packaging differences can be correlated without flooding normal diagnostics.
Completion check: the result
Emit the profile-required lexical form and retain tests for timezone, century, leap-day, and fractional-second edges. A recovery test built around round-trip a known UTC boundary value 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 original time text and ASN.1 type 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.