| Previous | Next |
| OSS_PDV_DLL_NOT_LINKED | OSS_API_DLL_NOT_LINKED |
OSS_PDV_CODE_NOT_LINKED
OSS_PDV_CODE_NOT_LINKED (0x80093028) is an OSS ASN.1 runtime result for legacy PDV implementation missing from the image. The application reaches a PDV operation whose generated or static implementation was not linked. Because link map and generated PDV source 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 schema types that trigger the path, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
Where processing stopped
At the legacy PDV implementation missing from the image 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 differences between working and failing build targets; 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 |
|---|---|
| link map and generated PDV source | Locates the concrete message, allocation, module, or API boundary |
| schema types that trigger the path | Separates payload-dependent behavior from build and process state |
| differences between working and failing build targets | Makes the comparison reproducible without rewriting the original artifact |
Similar names, different faults: the result
This is the code-link counterpart of PDV_DLL_NOT_LINKED and should be resolved in the build, not by editing encoded data.
Isolation sequence
- force the PDV symbol into a minimal link test
- compare project source lists across configurations
- clean stale objects before rebuilding
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 link map and generated PDV source can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use schema types that trigger the path 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 force the PDV symbol into a minimal link test. A change in schema types that trigger the path after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When differences between working and failing build targets 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 |
|---|---|
| force the PDV symbol into a minimal link test | A changed outcome isolates the first proposed control instead of a blind retry |
| link map and generated PDV source differs between success and failure | The difference localizes the legacy PDV implementation missing from the image 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
Link the intended PDV code and add an executable test that enters the exact operation. A recovery test built around force the PDV symbol into a minimal link test 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 link map and generated PDV source 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.