| Previous | Next |
| OSS_BAD_TABLE | OSS_CONSTRAINT_VIOLATED |
OSS_TOO_LONG
OSS_TOO_LONG (0x80093010) is an OSS ASN.1 runtime result for value exceeds SIZE while strong checking is disabled. The encoder encounters a value longer than the ASN.1 SIZE constraint in a configuration where the dedicated strong-checking path was not used. Because actual element or string length 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 declared SIZE constraint and extension marker, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
Where processing stopped
At the value exceeds SIZE while strong checking is disabled 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 constraint-checking flags used for this call; 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 |
|---|---|
| actual element or string length | Locates the concrete message, allocation, module, or API boundary |
| declared SIZE constraint and extension marker | Separates payload-dependent behavior from build and process state |
| constraint-checking flags used for this call | Makes the comparison reproducible without rewriting the original artifact |
Similar names, different faults: the result
CONSTRAINT_VIOLATED is the general checked failure; TOO_LONG highlights an oversized value found during encoding under different checking behavior.
Isolation sequence
- encode exactly the upper-bound length
- enable explicit constraint checking in a test build
- trace where the collection count is assigned
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 actual element or string length can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use declared SIZE constraint and extension marker 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 encode exactly the upper-bound length. A change in declared SIZE constraint and extension marker after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When constraint-checking flags used for this call 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 |
|---|---|
| encode exactly the upper-bound length | A changed outcome isolates the first proposed control instead of a blind retry |
| actual element or string length differs between success and failure | The difference localizes the value exceeds SIZE while strong checking is disabled 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
Validate lengths when constructing the value and ensure runtime flags match the application validation policy. A recovery test built around encode exactly the upper-bound length 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 actual element or string length 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.