| Previous | Next |
| DB_E_BADSOURCEHANDLE | DB_E_ALREADYINITIALIZED |
DB_E_PARAMUNAVAILABLE
Meaning
Windows documents DB_E_PARAMUNAVAILABLE as “Provider cannot derive parameter information and SetParameterInfo has not been called”. In this case, parameter metadata is requested or used when the provider cannot derive it and the consumer has not supplied it.
Relevant contract
Accessors are created on a specific command or rowset and encode direction, purpose, bound parts and buffer ownership. A valid HACCESSOR on one object is not interchangeable with a parameter accessor, a readable row accessor or an accessor created for another generation.
Investigation of this result should start with the object that created the accessor, its DBACCESSORFLAGS and every DBBINDING entry.
Evidence to collect
When recording diagnostic data involving parameter values, row values and provider-owned storage pointers, use types, lengths, hashes or redacted identifiers rather than secrets or complete business data.
- Evidence 1: the command text or stable hash and dialect.
- Evidence 2: the parameter ordinals, names and expected provider types.
- Evidence 3: the HRESULT and error records from metadata derivation.
Conditions that specifically lead to it
- Cause 1: the command dialect does not expose derivable parameter types.
- Cause 2: the statement uses constructs whose parameter metadata is ambiguous.
- Cause 3: SetParameterInfo was skipped after GetParameterInfo could not derive metadata.
Diagnostic sequence
- Identify the exact failing stage: parameter metadata is requested or used when the provider cannot derive it and the consumer has not supplied it.
Retry and recovery
Retry rule: retry after explicit parameter information has been installed on the current command.
Corrective actions
- Action 1: call SetParameterInfo with complete parameter descriptions.
- Action 2: bind ordinals and types consistently with the supplied metadata.
- Action 3: cache parameter metadata only with the exact command definition.
Practical scenario
A provider cannot infer types for a stored-procedure call; supplying ordinals and native type names allows execution to proceed.
Difference from nearby HRESULT values
DB_E_BADPARAMETERNAME rejects an unrecognized name, while DB_E_PARAMUNAVAILABLE means required metadata was neither derived nor supplied.
Official Microsoft references
Looking for a different code? Search another status or error code.