| Previous | Next |
| hrExistingLogFileIsNotContiguous | hrBufferTruncated |
hrColumnNull
How to read this HRESULT
For hrColumnNull, a correct handler first decides whether the value is success, warning, or failure, then examines the documented outputs. The decisive boundary is column retrieval found a genuine NULL value and therefore no payload bytes exist for that column.
The stored Value is 0x880003EC (positive JET status 1004; 1004). 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_wrnColumnNull for the corresponding published JET condition.
The first useful distinction is that NULL is semantically different from a zero-length value and from hrBufferTruncated. Start by record the column ID, itagSequence, retrieval flags, default-value rules, and returned actual-size field. That separates a reproducible incident from a later generic cleanup or service error.
Objects and state involved
| Diagnostic layer | column NULL state, schema limits, and caller output-buffer contracts |
|---|---|
| Relevant API surface | JetRetrieveColumn, JetSetColumn, column enumeration, and schema creation |
| Code-specific boundary | column retrieval found a genuine NULL value and therefore no payload bytes exist for that column |
| Narrow corrective direction | branch on the warning before decoding the output buffer and preserve NULL in the application model |
JET warnings can carry valid output state and must not be reduced to a boolean failure., nULL, empty, defaulted, and truncated values are distinct application states.
What to collect first
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: record the column ID, itagSequence, retrieval flags, default-value rules, and returned actual-size field.
- Input/output buffer sizes: record it together with this result and the timestamp of the first occurrence.
- Actual returned length: record it together with this result and the timestamp of the first occurrence.
- Retrieval or set flags: record it together with this result and the timestamp of the first occurrence.
- Column ID and type: record it together with this result and the timestamp of the first occurrence.
Controlled remediation
- Record it,
0x880003EC, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by record the column ID, itagSequence, retrieval flags, default-value rules, and returned actual-size field.
- Apply only the narrow correction: branch on the warning before decoding the output buffer and preserve NULL in the application model.
- 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
Boundary with related codes
It specifically means that NULL is semantically different from a zero-length value and from hrBufferTruncated. Related values below can appear in the same workflow but require a different response:
hrBufferTruncated | the caller-provided output buffer did not hold the complete value even though the engine identified the value |
|---|---|
hrColumnSetNull | a column update resulted in a NULL value as an explicit outcome |
hrTableEmpty | the table opened successfully but contains no current record for navigation |
Keep the original constant and hexadecimal value in telemetry. Replacing it with “backup failed” or “database warning” removes the state information needed to select the next legal API call.
Actions that can make diagnosis worse
- do not replace NULL with an empty value without an explicit data-model rule.
- do not decode an undefined or partial buffer as a complete value.
- do not discard the first lower-level Win32, RPC, or JET result merely because a later cleanup call returned a more familiar error.
Technical references
- ESE warning 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.