| Previous | Next |
| hrInvalidCountry | hrInvalidCodePage |
hrInvalidLanguageId
Locate the failure in the Jet call chain
hrInvalidLanguageId means the requested language identifier cannot define the intended collation behavior.
This is the legacy Directory Service backup/restore HRESULT form of JET_errInvalidLanguageId (0xC8000426).
The key comparison is: hrInvalidCountry concerns a country code; hrInvalidCodePage concerns text encoding. The first useful observation is to record LANGID/LCID, sort version, culture fallback, and the schema object being created or opened. This evidence separates character encoding from language and collation metadata.
The ESE objects in play
| Diagnostic layer | text encoding, locale, and index collation metadata |
|---|---|
| Typical API surface | column and index creation structures, JET_COLUMNDEF, JET_CP, and locale-aware index definitions |
| Code-specific condition | the requested language identifier cannot define the intended collation behavior |
| First corrective direction | use a locale supported by the running OS and plan index rebuilds when collation metadata changes |
Lossy conversion before the API can hide the original invalid value. Encoding and collation are different schema decisions.
Questions the logs must answer
- Code-specific observation: record LANGID/LCID, sort version, culture fallback, and the schema object being created or opened.
- the index definition and encoded sample that exposed the mismatch; associate it with this result rather than with a later generic exception.
- the original LANGID, LCID, country value, JET_CP, and column type.
- the operating-system locale and sort-version data.
Response and verification
- Freeze the failing request context and record
0xC8000426, the Jet API name, and the current instance/session ownership. - Verify the code-specific precondition: record LANGID/LCID, sort version, culture fallback, and the schema object being created or opened.
- Apply the targeted fix: use a locale supported by the running OS and plan index rebuilds when collation metadata changes.
- Before retrying the operation, reconcile encoded values, collation behavior, and rebuilt index ordering.
Distinguishing signals
hrInvalidCountry | a legacy locale/country value is not recognized for collation or index creation |
|---|---|
hrInvalidCodePage | the column or index requests an unsupported or invalid text code page |
Actions that can hide or worsen the problem
- Do not use lossy text conversion to make an unsupported value appear valid.
- Do not change locale or code-page metadata without planning the required index rebuild.
Technical references
- JET_coltyp enumeration.
- JET_CP enumeration
- JetCreateIndex
- JET error codes
- Microsoft: JET_ERR enumeration
Looking for a different code? Search another status or error code.