What does HRESULT 0x87AF010E (SQLITE_E_CANTOPEN_NOTEMPDIR) mean?

 
Previous Next
SQLITE_E_CORRUPT_VTAB SQLITE_E_CONSTRAINT_CHECK

SQLITE_E_CANTOPEN_NOTEMPDIR

SQLITE_E_CANTOPEN_NOTEMPDIR is the extended SQLite cannot-open result for a missing or unusable temporary directory.

What to check for SQLITE_E_CANTOPEN_NOTEMPDIR

  • Check the process temporary-directory configuration, service account permissions, and available space.
  • Check container and sandbox policies that may omit a writable temporary directory.
  • Fix the runtime environment rather than redirecting temporary files into the live database directory without considering its security and capacity limits.
PRAGMA temp_store;

SQLite: Result and Error Codes

SQLite: PRAGMA statements

Diagnostic interpretation of SQLITE_E_CANTOPEN_NOTEMPDIR

SQLITE_E_CANTOPEN_NOTEMPDIR has the HRESULT value 0x87AF010E. AllStat records the condition as “SQLITE_CANTOPEN_NOTEMPDIR”. For SQLITE_E_CANTOPEN_NOTEMPDIR, in practice, interpret that wording at the boundary owned by the Windows component or COM interface that returned the HRESULT, rather than treating the value as a generic Windows message.

Evidence to capture for SQLITE_E_CANTOPEN_NOTEMPDIR

  • Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x87AF010E value before a wrapper converts it to an exception or Boolean result.
  • Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions SQLITE_E_CANTOPEN_NOTEMPDIR or the sqlite / cantopen / notempdir operation.
  • For SQLITE_E_CANTOPEN_NOTEMPDIR, compare the failing machine with a working one at the same configuration boundary: component version, policy, registration, identity, and target resource.

Retry and recovery for SQLITE_E_CANTOPEN_NOTEMPDIR

Retry SQLITE_E_CANTOPEN_NOTEMPDIR only when the owning API documents a transient state or after the condition described as “SQLITE_CANTOPEN_NOTEMPDIR” has changed. For SQLITE_E_CANTOPEN_NOTEMPDIR, configuration, policy, format, and authorization failures normally require correction first; an immediate loop can hide the original call site and add secondary errors.


Looking for a different code? Search another status or error code.