| Previous | Next |
| hrRemainingVersions | hrFLDNullKey |
hrFLDKeyTooBig
The exact boundary reported here
For hrFLDKeyTooBig, this code narrows the investigation to one engine boundary and should not be flattened into a generic exception. The decisive boundary is an index key exceeded the legacy key budget and was truncated rather than represented in full.
The stored Value is 0x88000190 (positive JET status 400; 400). The HRESULT carries a warning, so the call may have useful output or a valid cursor state that must be inspected. The legacy this result name comes from the Windows Directory Service backup/restore message header.
The first useful distinction is that this warning differs from a hard key-size error because the operation may continue with a shortened key. Start by log the index definition, normalized key bytes, contributing columns, locale, and whether truncation can merge otherwise distinct values. That separates a reproducible incident from a later generic cleanup or service error.
Objects and state involved
| Diagnostic layer | index key construction, NULL semantics, and legacy key limits |
|---|---|
| Relevant API surface | index definition, key creation, seeks, ranges, and record updates that change indexed values |
| Code-specific boundary | an index key exceeded the legacy key budget and was truncated rather than represented in full |
| Narrow corrective direction | redesign the key or explicitly validate truncation semantics before relying on exact uniqueness or seek behavior |
An index key is derived data whose byte representation depends on schema, locale, and column values., a warning can leave a usable cursor or index entry while changing exact-match or uniqueness assumptions.
Adjacent conditions
This result specifically means that this warning differs from a hard key-size error because the operation may continue with a shortened key. Related values below can appear in the same workflow but require a different response:
hrFLDNullKey | key construction produced a NULL key for the current record or index expression |
|---|---|
hrInvalidRecips | the recipient information supplied to the legacy backup operation failed validation |
hrLogFileCorrupt | ESE detected structural or checksum corruption while reading a transaction log |
Keep the original constant and hexadecimal value in telemetry. Replacing this result with “backup failed” or “database warning” removes the state information needed to select the next legal API call.
Diagnostic record
Preserve the first result before retries, cleanup, service restart, or file replacement changes the evidence. The diagnostic record should identify the exact API phase and the owner of every handle or artifact involved.
- Code-specific observation: log the index definition, normalized key bytes, contributing columns, locale, and whether truncation can merge otherwise distinct values.
- NULL and conditional-index rules: record it together with this result and the timestamp of the first occurrence.
- Seek or insert result: record it together with it and the timestamp of the first occurrence.
- Index definition and segment order: record it together with it and the timestamp of the first occurrence.
- Normalized key length and bytes: record it together with it and the timestamp of the first occurrence.
Use hashes, lengths, IDs, generation numbers, and redacted samples instead of copying directory contents or sensitive database values into routine logs. For this it investigation, a complete provenance chain is often more useful than a second automatic retry.
Actions that can make diagnosis worse
- do not compare only the source text when the stored key is normalized or truncated.
- do not collapse NULL and empty values in diagnostics.
- do not discard the first lower-level Win32, RPC, or JET result merely because a later cleanup call returned a more familiar error.
Corrective path
- Record it,
0x88000190, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by log the index definition, normalized key bytes, contributing columns, locale, and whether truncation can merge otherwise distinct values.
- Apply only the narrow correction: redesign the key or explicitly validate truncation semantics before relying on exact uniqueness or seek behavior.
- After it, recreate any context invalidated by the failure; do not carry stale HBC, cursor, file, or restore-map state into the retry.
- repeat the smallest non-destructive test that reaches the same boundary, then verify both the return value and the resulting file, cursor, backup, or database state.
Acceptance criteria for a fix
A useful regression test for this HRESULT should force the condition “an index key exceeded the legacy key budget and was truncated rather than represented in full”, call one documented API transition, and assert the exact HRESULT. The corrected the case should change only the decisive precondition and should verify cleanup as well as the primary output. For the result backup or restore path, also prove that the resulting set can be enumerated and that no file handle or context remains active after finalization.
Technical references
- ESE warnings and errors — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to it.
- JET_ERR enumeration
- Open-source ESE implementation
Looking for a different code? Search another status or error code.