| Previous | Next |
| hrIndexHasPrimary | hrIndexNotFound |
hrIndexDuplicate
Why this is more specific than the message text
hrIndexDuplicate means an index with the requested name or equivalent definition already exists.
This is the legacy Directory Service backup/restore HRESULT form of JET_errIndexDuplicate (0xC800057B).
The key comparison is: hrObjectDuplicate is generic; this code isolates an index collision. The first useful observation is to record normalized index name, key definition, flags, locale, and conditional columns. This evidence separates index schema, current-index cursor state, key construction, and duplicate data.
Related ESE conditions
hrIndexCantBuild | ESE cannot construct the requested clustered index from the existing table and definition |
|---|---|
hrIndexHasClustered | the table already owns a clustered index and cannot accept another clustered layout |
hrTooManyKeys | an index definition contains more key segments than the engine accepts |
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 | an index with the requested name or equivalent definition already exists |
| First corrective direction | verify equivalence and skip idempotently, or version the schema change with an intentional replacement |
Key bytes depend on segment order, column representation, collation, null rules, and sort direction. Clustered, primary, and unique properties must be interpreted from the actual index flags.
Data for a reproducible case
- Code-specific observation: record normalized index name, key definition, flags, locale, and conditional columns.
- 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.
Corrective workflow
- Freeze the failing request context and record
0xC800057B, the Jet API name, and the current instance/session ownership. - Verify the code-specific precondition: record normalized index name, key definition, flags, locale, and conditional columns.
- Apply the targeted fix: verify equivalence and skip idempotently, or version the schema change with an intentional replacement.
- 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.