| Previous | Next |
| DB_E_TABLEINUSE | DB_E_BADRECORDNUM |
DB_E_NOLOCALE
Meaning
Windows documents DB_E_NOLOCALE as “Locale ID is not supported”. Here, an OLE DB operation requests an LCID the provider does not support.
Relevant OLE DB contract
This result must be interpreted against this contract: OLE DB schema contracts combine DBIDs, provider type metadata, column attributes, constraints and locale rules; current provider metadata is authoritative; cached ordinals or type assumptions can become invalid after a schema or command change.
Start with the table, column, parameter or schema object named by the failing definition or data operation when investigating this result.
Specific conditions that produce the result
- Cause 1: the locale is not installed or recognized by the provider.
- Cause 2: the consumer uses a UI locale for data comparison without checking provider support.
- Cause 3: a persisted LCID is invalid on the current machine or provider version.
Evidence to collect before changing the system
- Evidence 1: the requested LCID and culture name.
- Evidence 2: provider locale capabilities.
- Evidence 3: the property, index or comparison operation using the locale.
Corrective actions
- Action 1: select a locale reported as supported.
- Action 2: define a documented invariant fallback when semantics permit.
- Action 3: avoid silently changing collation-sensitive behavior.
Retry and recovery policy
Retry rule: retry after choosing a supported locale or changing provider configuration.
Practical incident
A sort definition forwards a client-only locale to a server provider that supports a smaller set; negotiating the locale avoids it.
Difference from related HRESULT values
DB_E_BADPROPERTYVALUE can reject a malformed locale property value, while DB_E_NOLOCALE means the requested locale itself is unsupported.
Official Microsoft references
Looking for a different code? Search another status or error code.