| Previous | Next |
| OSS_TOO_LONG | OSS_FATAL_ERROR |
OSS_CONSTRAINT_VIOLATED
OSS_CONSTRAINT_VIOLATED (0x80093011) is an OSS ASN.1 runtime result for ASN.1 constraint rejected the value. The value fails a range, size, permitted-alphabet, table, presence, or other constraint compiled from the schema. Because constraint text and generated 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 actual value or length at the boundary, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
Locate the failing codec stage
At the ASN.1 constraint rejected the 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 whether the constraint is extensible; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Evidence worth preserving
- constraint text and generated type
- actual value or length at the boundary
- whether the constraint is extensible
A controlled way to reproduce it
- Test the exact lower and upper bounds
- run the generated constraint checker before encoding
- Compare schemas on both communicating endpoints
What not to confuse it with: the result
Valid BER syntax does not make a value valid for its ASN.1 type; this status concerns abstract-value rules rather than tag/length parsing.
Instrumentation
Where constraint text and generated type can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use actual value or length at the boundary together with OSS module paths and versions logged once per process so packaging differences can be correlated without flooding normal diagnostics.
Exit criteria: the result
Correct the value or deploy the intended schema revision, then preserve positive and negative boundary cases.
Technical references
Looking for a different code? Search another status or error code.