| Previous | Next |
| hrTableEmpty | hrColumnMaxTruncated |
hrCreateIndexFailed
Interpretation in the backup state machine
hrCreateIndexFailed means a compound table-creation operation could not complete one of its requested index definitions.
The stored value is 0x88000581 (positive JET status 1409; 1409). The HRESULT carries a warning, so the call may have useful output or a valid cursor state that must be inspected. The legacy symbolic name comes from the Windows Directory Service backup/restore message header.
The first useful distinction is that the top-level warning can coexist with partial object creation, so checking only the table handle loses the failing index detail. Start by capturing every table, column, and index descriptor plus the per-object result fields returned by the compound API.
Start with these observations
- Code-specific observation: capture every table, column, and index descriptor plus the per-object result fields returned by the compound API.
Objects and state involved
| Diagnostic layer | partial schema creation and effective column/index definitions |
|---|---|
| Relevant API surface | compound table/column/index creation and schema inspection |
| Code-specific condition | a compound table-creation operation could not complete one of its requested index definitions |
| Narrow corrective direction | inspect per-index results, remove any partial schema deliberately, and retry only the corrected definition |
Compound schema APIs can report object-specific results rather than one all-or-nothing outcome. The effective schema returned by ESE is the contract the application must verify.
Recovery or retry plan
- Record it,
0x88000581, the API name, the current phase, and all live context or file owners. - Verify the condition by capturing every table, column, and index descriptor plus the per-object result fields returned by the compound API.
- Apply only the targeted fix: inspect per-index results, remove any partial schema deliberately, and retry only the corrected definition.
Not the same as
It specifically means that the top-level warning can coexist with partial object creation, so checking only the table handle loses the failing index detail. Related values below can appear in the same workflow but require a different response:
hrColumnMaxTruncated | the requested maximum column length exceeded the supported limit and the engine reduced it |
|---|---|
hrColumnSetNull | a column update resulted in a NULL value as an explicit outcome |
hrLogFileNotFound | an incremental Directory Service backup cannot assemble the required transaction-log set |
Actions that can make diagnosis worse
- Do not deploy a schema whose effective limits were not read back.
- Do not assume rollback removed every partially created object.
Acceptance criteria for a fix
A useful regression test should force the condition “a compound table-creation operation could not complete one of its requested index definitions”, call one documented API transition, and assert the exact HRESULT.
Technical references
- ESE warning and error table — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to this HRESULT.
- JET_ERR enumeration
- Open-source ESE implementation
Looking for a different code? Search another status or error code.