| Previous | Next |
| hrOutOfBuffers | hrTooManyKeys |
hrTooManyIndexes
Interpretation in ESE terms
hrTooManyIndexes means a table schema attempted to exceed the supported number of indexes.
This is the legacy Directory Service backup/restore HRESULT form of JET_errTooManyIndexes (0xC80003F7).
The key comparison is: hrTooManyOpenIndexes is runtime descriptor exhaustion; this code is a schema-count limit. The first useful observation is to enumerate current indexes, conditional indexes, and the migration step adding the next definition. This evidence separates index schema, current-index cursor state, key construction, and duplicate data.
The ESE objects in play
| Diagnostic layer | B-tree index definition, key construction, uniqueness, and current-index cursor state |
|---|---|
| Typical API surface | JetCreateIndex, JetDeleteIndex, JetSetCurrentIndex, JetMakeKey, JetSeek, and JetSetIndexRange |
| Code-specific condition | a table schema attempted to exceed the supported number of indexes |
| First corrective direction | remove redundant indexes or redesign the schema before replaying the migration |
Clustered, primary, and unique properties must be interpreted from the actual index flags. Index schema and runtime key-building state are separate diagnostic layers.
Comparison with adjacent failures
hrNullKeyDisallowed | an index definition or inserted row produces a null key where the index contract forbids it |
|---|---|
hrTooManyKeys | an index definition contains more key segments than the engine accepts |
hrNoCurrentIndex | the cursor operation requires an active index but none is selected or available |
What to capture before retrying
- the raw index key definition, flags, locale, and conditional columns; associate it with this result rather than with a later generic exception.
- the current index plus every JetMakeKey segment and grbit.
- the encoded key and existing row when uniqueness is involved.
Actions that can hide or worsen the problem
- Do not drop or rebuild an index before checking uniqueness and table-layout dependencies.
- Do not treat a key-construction or duplicate-key result as database-file corruption.
Operational response
- Freeze the failing request context and record
0xC80003F7, the Jet API name, and the current instance/session ownership. - Apply the targeted fix: remove redundant indexes or redesign the schema before replaying the migration.
- Before retrying the operation, reconcile index definition, selected cursor index, and key or uniqueness outcome.
Technical references
Looking for a different code? Search another status or error code.