| Previous | Next |
| hrTaggedNotNULL | hrKeyIsMade |
hrNoCurrentIndex
Diagnostic focus
hrNoCurrentIndex means the cursor operation requires an active index but none is selected or available.
This is the legacy Directory Service backup/restore HRESULT form of JET_errNoCurrentIndex (0xC80005EB).
The key comparison is: hrIndexNotFound is a named lookup failure; this code describes cursor state after lookup/selection. The first useful observation is to record current-index changes, table type, index deletion/migration, and cursor initialization. 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 | the cursor operation requires an active index but none is selected or available |
| First corrective direction | select a valid index before key construction, seeking, or ordered navigation |
Index schema and runtime key-building state are separate diagnostic layers. Key bytes depend on segment order, column representation, collation, null rules, and sort direction.
Evidence that resolves the ambiguity
- Code-specific observation: record current-index changes, table type, index deletion/migration, and cursor initialization.
- 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; associate it with this result rather than with a later generic exception.
- the encoded key and existing row when uniqueness is involved.
Nearby results that mean something different
hrKeyNotMade | a seek or range operation was invoked before a complete search key was constructed |
|---|---|
hrNullKeyDisallowed | an index definition or inserted row produces a null key where the index contract forbids it |
hrKeyIsMade | a new key-building sequence was started or modified after the current search key was already complete |
A disciplined correction path
- Freeze the failing request context and record
0xC80005EB, the Jet API name, and the current instance/session ownership. - Verify the code-specific precondition: record current-index changes, table type, index deletion/migration, and cursor initialization.
- Apply the targeted fix: select a valid index before key construction, seeking, or ordered navigation.
- Before retrying the operation, reconcile index definition, selected cursor index, and key or uniqueness outcome.
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.
Technical references
Looking for a different code? Search another status or error code.