| Previous | Next |
| OSS_NEGATIVE_UINTEGER | OSS_MORE_INPUT |
OSS_PDU_RANGE
OSS_PDU_RANGE (0x80093003) is an OSS ASN.1 runtime result for PDU selector outside the generated control table. The PDU number supplied to the runtime does not identify a top-level type in the control information currently in use. Because numeric PDU selector and symbolic generated constant 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 identity and build hash of the control table, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
Avoid the wrong workaround: OSS_PDU_RANGE
OSS_TABLE_MISMATCH instead means a type is absent from the selected table during a later operation; PDU_RANGE rejects the selector itself.
Interpretation at runtime
At the PDU selector outside the generated control table 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 the OssControl instance passed to the call; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Diagnostic record
| Record | Diagnostic value |
|---|---|
| numeric PDU selector and symbolic generated constant | Locates the concrete message, allocation, module, or API boundary |
| identity and build hash of the control table | Separates payload-dependent behavior from build and process state |
| the OssControl instance passed to the call | Makes the comparison reproducible without rewriting the original artifact |
Keep the original bytes or object graph unchanged while testing encode a known top-level type from the same generated files. A change in identity and build hash of the control table after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When the OssControl instance passed to the call points to one message, retain a cryptographic hash and the smallest safe sample instead of logging certificate, subscriber, credential, or private-key material.
Small experiments with high signal
- encode a known top-level type from the same generated files
- log selector-to-name mapping at the call boundary
- verify that no stale enum was persisted across deployments
Decision matrix
| Controlled observation | Conclusion it supports |
|---|---|
| encode a known top-level type from the same generated files | A changed outcome isolates the first proposed control instead of a blind retry |
| numeric PDU selector and symbolic generated constant differs between success and failure | The difference localizes the PDU selector outside the generated control table 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 numeric PDU selector and symbolic generated constant can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use identity and build hash of the control table together with OSS module paths and versions logged once per process so packaging differences can be correlated without flooding normal diagnostics.
Proof of recovery: the result
Deploy generated headers, control data, and application code as one versioned unit. A recovery test built around encode a known top-level type from the same generated files 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 numeric PDU selector and symbolic generated constant 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.