| Previous | Next |
| hrCreateIndexFailed | hrwrnDataHasChanged |
hrColumnMaxTruncated
The exact boundary reported here
For hrColumnMaxTruncated, this code narrows the investigation to one engine boundary and should not be flattened into a generic exception. The decisive boundary is the requested maximum column length exceeded the supported limit and the engine reduced it.
The stored Value is 0x880005E8 (positive JET status 1512; 1512). The HRESULT carries a warning, so the call may have useful output or a valid cursor state that must be inspected. Current ESE documentation uses JET_wrnColumnMaxTruncated for the corresponding published JET condition.
The first useful distinction is that this changes schema metadata; hrBufferTruncated concerns one retrieval buffer and does not redefine the column. Start by compare the requested and effective maximum, column type, page size, code page, and API structure returned after creation. That separates a reproducible incident from a later generic cleanup or service error.
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 boundary | the requested maximum column length exceeded the supported limit and the engine reduced it |
| Narrow corrective direction | read back the effective definition and reject the migration if application data can exceed it |
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.
Adjacent conditions
This result specifically means that this changes schema metadata; hrBufferTruncated concerns one retrieval buffer and does not redefine the column. Related values below can appear in the same workflow but require a different response:
hrCreateIndexFailed | a compound table-creation operation could not complete one of its requested index definitions |
|---|---|
hrSeekNotEqual | a less-than-or-equal or greater-than-or-equal seek positioned the cursor without finding an exact key match |
hrLogFileCorrupt | ESE detected structural or checksum corruption while reading a transaction log |
Keep the original constant and hexadecimal value in telemetry. Replacing this result with “backup failed” or “database warning” removes the state information needed to select the next legal API call.
Diagnostic record
Preserve the first result before retries, cleanup, service restart, or file replacement changes the evidence. The diagnostic record should identify the exact API phase and the owner of every handle or artifact involved.
- Code-specific observation: compare the requested and effective maximum, column type, page size, code page, and API structure returned after creation.
- Created object IDs: record it together with this result and the timestamp of the first occurrence.
- Cleanup after partial success: record it together with this result and the timestamp of the first occurrence.
- All schema descriptors and result fields: record it together with it and the timestamp of the first occurrence.
- Requested versus effective limits: record it together with it and the timestamp of the first occurrence.
Use hashes, lengths, IDs, generation numbers, and redacted samples instead of copying directory contents or sensitive database values into routine logs. For this it investigation, a complete provenance chain is often more useful than a second automatic retry.
Actions that can make diagnosis worse
- do not assume rollback removed every partially created object.
- do not deploy a schema whose effective limits were not read back.
- do not discard the first lower-level Win32, RPC, or JET result merely because a later cleanup call returned a more familiar error.
Corrective path
- Record it,
0x880005E8, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by compare the requested and effective maximum, column type, page size, code page, and API structure returned after creation.
- Apply only the narrow correction: read back the effective definition and reject the migration if application data can exceed it.
- After it, recreate any context invalidated by the failure; do not carry stale HBC, cursor, file, or restore-map state into the retry.
- repeat the smallest non-destructive test that reaches the same boundary, then verify both the return value and the resulting file, cursor, backup, or database state.
Acceptance criteria for a fix
A useful regression test for this HRESULT should force the condition “the requested maximum column length exceeded the supported limit and the engine reduced it”, call one documented API transition, and assert the exact HRESULT. The corrected the case should change only the decisive precondition and should verify cleanup as well as the primary output. For the result backup or restore path, also prove that the resulting set can be enumerated and that no file handle or context remains active after finalization.
Technical references
- ESE warning and error table — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to it.
- JET_ERR enumeration
- Open-source ESE implementation
Looking for a different code? Search another status or error code.