| Previous | Next |
| hrTooManyOpenIndexes | hrColumnDoesNotFit |
hrColumnLong
Locate the failure in the Jet call chain
hrColumnLong means a supplied value exceeds the operation or column path intended for ordinary-sized data.
This is the legacy Directory Service backup/restore HRESULT form of JET_errColumnLong (0xC80005DD).
The key comparison is: hrColumnTooBig is the declared column maximum; hrColumnDoesNotFit is remaining record space. The first useful observation is to measure the encoded byte length and identify whether the schema expects a long-value column. This evidence separates schema definition, row-size accounting, null semantics, multivalue selection, and stale column IDs.
The ESE objects in play
| Diagnostic layer | column schema, row-size accounting, tagged/multivalued storage, and column identifiers |
|---|---|
| Typical API surface | JetAddColumn, JetDeleteColumn, JetSetColumn, JetRetrieveColumn, and JET_COLUMNDEF |
| Code-specific condition | a supplied value exceeds the operation or column path intended for ordinary-sized data |
| First corrective direction | store large data in the supported long-value representation or enforce a smaller application limit |
Null, zero-length, deletion, and missing multivalue instances are distinct states. Fixed, variable, tagged, and long-value columns consume row space differently.
Questions the logs must answer
- Code-specific observation: measure the encoded byte length and identify whether the schema expects a long-value column.
- the complete row-size contribution from fixed, variable, tagged, and long-value data; associate it with this result rather than with a later generic exception.
- JET_COLUMNDEF fields, flags, code page, maximum length, and column ID origin; associate it with this result rather than with a later generic exception.
- the encoded value length, null/empty state, and itag sequence.
Response and verification
- Freeze the failing request context and record
0xC80005DD, the Jet API name, and the current instance/session ownership. - Verify the code-specific precondition: measure the encoded byte length and identify whether the schema expects a long-value column.
- Apply the targeted fix: store large data in the supported long-value representation or enforce a smaller application limit.
- Before retrying the operation, reconcile column metadata, row layout, and the exact stored value state.
Distinguishing signals
hrColumnIndexed | a column cannot be removed because one or more indexes reference it |
|---|---|
hrColumnNotFound | the requested column name or ID is absent from the current table schema |
hrColumnInUse | a schema change targets a column that an index or other active definition still depends on |
Actions that can hide or worsen the problem
- Do not alter the column schema in place without a migration and rollback plan.
- Do not collapse null, zero-length data, missing value, and tagged-value deletion into one state.
Technical references
Looking for a different code? Search another status or error code.