| Previous | Next |
| DB_S_NORESULT | DB_S_GOALCHANGED |
DB_S_CANTRELEASE
OLE DB lock cannot be released or downgraded before transaction end
DB_S_CANTRELEASE is HRESULT 265930 (0x00040ECA) from Microsoft OLE DB. AllStat describes DB_S_CANTRELEASE as “Server cannot release or downgrade a lock until the end of the transaction.” The high-order severity bit is clear, so this is a success result, but it carries more information than plain S_OK.
The requested lock release or downgrade did not occur because the server must retain the lock until the transaction completes.
Evidence and telemetry to preserve
- For
DB_S_CANTRELEASE, preserve transaction identifier and isolation level. - For
DB_S_CANTRELEASE, preserve row or object locked. - For
DB_S_CANTRELEASE, preserve requested and actual lock modes. - For
DB_S_CANTRELEASE, preserve blocking sessions. - For
DB_S_CANTRELEASE, preserve commit or rollback timing.
Also record db_s_cantrelease_operation, db_s_cantrelease_object, db_s_cantrelease_state_before, db_s_cantrelease_state_after, UTC time, process and thread identifiers, and a correlation ID. For DB_S_CANTRELEASE, keep secrets out of logs while retaining GUIDs, CLSIDs, media subtypes, property IDs, row identities, and hashes needed to distinguish objects.
Where this result is encountered
DB_S_CANTRELEASEcan appear in rowset lock management; record the producing interface and method rather than inferring behavior from the symbolic name alone.DB_S_CANTRELEASEcan appear in transactional update cursors; record the producing interface and method rather than inferring behavior from the symbolic name alone.DB_S_CANTRELEASEcan appear in providers exposing explicit lock-strength operations; record the producing interface and method rather than inferring behavior from the symbolic name alone.
For DB_S_CANTRELEASE, the same numeric success value can be mishandled when a wrapper exposes only a Boolean. For DB_S_CANTRELEASE, keep the original HRESULT until the code-specific outputs and state transition have been evaluated.
State boundary that must be proved
The central question for DB_S_CANTRELEASE is whether the caller understands that the transaction still owns the stronger lock and accounts for its blocking impact. For DB_S_CANTRELEASE, the HRESULT alone confirms neither unrelated work nor the quality of optional outputs.
A reliable interpretation of DB_S_CANTRELEASE names the exact method contract, the object generation, and the outputs that remain valid. For DB_S_CANTRELEASE, this prevents a success-with-information result from being promoted to full success or demoted to a generic error.
Diagnostic sequence
- For
DB_S_CANTRELEASE, capture the raw HRESULT0x00040ECAimmediately after the returning method and record whether the caller usedSUCCEEDED,FAILED, equality testing, or exception translation. - Identify the exact owner of
DB_S_CANTRELEASE: interface, method, object instance, provider or filter version, thread or apartment, and operation phase. - Validate the decisive contract boundary for
DB_S_CANTRELEASE: the caller understands that the transaction still owns the stronger lock and accounts for its blocking impact. - For
DB_S_CANTRELEASE, inspect every output parameter, count, status array, returned interface, or side effect that the method documentation associates with this success-with-information result. - Compare the observed state before and after
DB_S_CANTRELEASE; do not assume that a success severity bit means every optional sub-operation completed. - For
DB_S_CANTRELEASE, reproduce the smallest request with the same object state and then change only the condition identified by the evidence before repeating the operation.
Difference from nearby HRESULT values
DB_S_LOCKUPGRADED reports a stronger acquired lock; DB_S_CANTRELEASE reports that an existing lock must remain.
For DB_S_CANTRELEASE, this distinction determines whether the caller should consume partial outputs, stop iteration, wait, reconfigure, notify the user, or perform no error recovery at all.
Correct handling, retry, and recovery
Finish or shorten the transaction when safe. Repeating the same downgrade request inside the unchanged transaction will not release the lock.
Retry DB_S_CANTRELEASE only when the recorded state can change the documented outcome. For DB_S_CANTRELEASE, repeating the same call is inappropriate for a stable end marker, cancellation, unsupported format, adjusted property, or partial result whose completed side effects have not been reconciled.
Practical validation scenario
A long transaction requests a row-lock downgrade after reading. The provider keeps the lock, so the application completes validation and commits promptly instead of spinning on release.
The negative test should preserve the condition that produces DB_S_CANTRELEASE; the recovery test should alter only that condition and verify the final state as well as the HRESULT.
Developer and administrator guidance
For DB_S_CANTRELEASE, application telemetry should separate terminal failure, ordinary success, partial completion, continuation, cancellation, and warning-like success. For DB_S_CANTRELEASE, support bundles should contain the smallest reproducible call and the effective configuration seen by the owning component.
A support report for DB_S_CANTRELEASE should include decimal 265930, hexadecimal 0x00040ECA, the AllStat meaning, the owning API, and the first detailed status or output that explains why the method did not return ordinary S_OK.
References
- Microsoft: OLE DB return codes — official documentation relevant to
DB_S_CANTRELEASE. - Microsoft: OLE DB Driver return codes — official documentation relevant to
DB_S_CANTRELEASE. - Microsoft: OLE DB error records — official documentation relevant to
DB_S_CANTRELEASE.
Looking for a different code? Search another status or error code.