| 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
- original time text and ASN.1 type
- timezone suffix, fractional seconds, and precision
- calendar validity including leap day and field ranges
Instrumentation
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.
Technical references
Looking for a different code? Search another status or error code.