| Previous | Next |
| hrNoWriteLock | hrTableEmpty |
hrColumnSetNull
Operational meaning
For hrColumnSetNull, a correct handler first decides whether the value is success, warning, or failure, then examines the documented outputs. The decisive boundary is a column update resulted in a NULL value as an explicit outcome.
The stored Value is 0x8800042C (positive JET status 1068; 1068). 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_wrnColumnSetNull for the corresponding published JET condition.
The first useful distinction is that this is an update-side warning; hrColumnNull is normally observed while retrieving a NULL value. Start by record the column definition, set flags, input pointer and length, default rules, and whether the update was intended to delete the value. That separates a reproducible incident from a later generic cleanup or service error.
Before altering files or retrying
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 definition, set flags, input pointer and length, default rules, and whether the update was intended to delete the value.
- 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.
- 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.
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.
Comparison points
It specifically means that this is an update-side warning; hrColumnNull is normally observed while retrieving a NULL value. Related values below can appear in the same workflow but require a different response:
hrColumnNull | column retrieval found a genuine NULL value and therefore no payload bytes exist for that column |
|---|---|
hrBufferTruncated | the caller-provided output buffer did not hold the complete value even though the engine identified the value |
hrTooManyIO | the engine reached its outstanding-I/O throttle and refused to queue more storage work |
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.
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 | a column update resulted in a NULL value as an explicit outcome |
| Narrow corrective direction | confirm that NULL is intended, then keep the distinction from empty data through serialization and validation |
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.
Recommended handling
- Record it,
0x8800042C, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by record the column definition, set flags, input pointer and length, default rules, and whether the update was intended to delete the value.
- Apply only the narrow correction: confirm that NULL is intended, then keep the distinction from empty data through serialization and validation.
- 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 “a column update resulted in a NULL value as an explicit outcome”, 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.
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.