What does Windows error code 6644 (ERROR_LOG_PINNED) mean?

ERROR_LOG_PINNED

Log space cannot be reclaimed because the log is pinned.

ERROR_LOG_PINNED is Win32 error 6644 (0x000019F4) in Common Log File System (CLFS). Interpret this result at the call that produced it and use the system message above as the immediate condition rather than as a complete root cause.

Windows assigns decimal 6644 and hexadecimal 0x000019F4 to this result. The decisive subject is CLFS log-space reclamation blocked by pinned records; the value alone does not reveal which object, server, file, session, or transition failed.

Where the result appears

• handling a log-full condition.
• shrinking a log.
• removing old containers.
• advancing the base log after checkpoint or archive.

State boundary to prove

This result applies to CLFS log-space reclamation blocked by pinned records and does not by itself prove that the entire server, directory, disk, session, or application is unavailable. The state boundary to prove for this Win32 error is whether all records below the proposed base log sequence number are no longer required by any client. Use oldest required LSN for every client, base LSN and last flushed LSN, and restart-area ownership as independent evidence. When evidence for this Win32 error disagrees, preserve timestamps and investigate the transition instead of selecting the most convenient value.

Likely causes

• a client has not advanced its base LSN.
• an outstanding restart area still references old records.
• archive progress has not released the range.
• a failed or hung client retains a reservation or pin.
• management attempts reclamation before dependent state is durable.

Diagnostic sequence

1. capture error 6644 immediately at the API boundary and record the operation that was attempted.
2. identify the exact owner of CLFS log-space reclamation blocked by pinned records, including object generation, server, path, session, replica, or client context.
3. collect oldest required LSN for every client before restarting a service or changing configuration.
4. compare base LSN and last flushed LSN with the documented or observed precondition.
5. correlate restart-area ownership with the owning application log, CLFS-related System events, storage events, and any transaction or recovery trace.
6. determine whether side effects occurred and verify recovery after changing one responsible condition.

Evidence to collect

• oldest required LSN for every client.
• base LSN and last flushed LSN.
• restart-area ownership.
• reservation and archive state.
• client health and last checkpoint time.

Correlate it with the owning application log, CLFS-related System events, storage events, and any transaction or recovery trace. Keep the first detailed status even when a later wrapper translates it to error 6644; the first status often distinguishes transport, authorization, storage, schema, state, and application-integrity causes that share the same final Win32 result.

Handling, retry, and recovery

The recovery objective is to identify the client that owns the oldest required record, complete its checkpoint or archive, advance its base LSN, and let CLFS reclaim space without deleting container files manually.

Retry it only after the recorded condition changes and completion state is known. Idempotent queries may be repeated after recovery, but mutations require a state check first; backoff cannot repair malformed input, corruption, missing structure, or policy rejection.

Telemetry and support fields

• record log_pinned_api for the producing function or management operation.
• record log_pinned_target for the file, log, session, replica, object, or server identity.
• record log_pinned_state_before and log_pinned_requested_transition.
• record log_pinned_first_status for the earliest lower-level diagnostic.

For support escalation involving it, retain decimal 6644, hexadecimal 0x000019F4, the API, UTC time, target identity, and first subsystem-specific status. Include the smallest reproducible request and evidence that distinguishes this condition from nearby codes. In the context of it, clfs clients can run in user mode or kernel mode, so the same win32 result may be returned through an application wrapper, a service, or a driver-facing management path.

Difference from nearby results

This result_RESERVATION identifies reservations as the dominant reason for the pin; this code can also result from active recovery or restart records.

Practical validation scenario

A service stops checkpointing after a worker failure. CLFS cannot recycle the oldest container because that client still advertises an old base LSN; restarting the worker and completing a checkpoint releases the range. The negative test should preserve the responsible condition and reproduce it; the recovery test should change only the identified cause, repeat the same operation, and verify both success and the absence of an unintended partial side effect.

Developer and administrator guidance

Administrators handling it should preserve the complete CLFS set—base log, containers, security metadata, and application checkpoint state—before repair. Developers should never delete or recreate a container merely because its path appears in the error; the owning recovery protocol determines whether that data is still required. Code that exposes it through RPC, JSON, REST, PowerShell, or another protocol should preserve the Win32 domain, decimal 6644, hexadecimal 0x000019F4, and original component diagnostic.

References

• Microsoft: Win32 system error range containing this code — official context relevant to it.
• Microsoft: Common Log File System — official context relevant to it.
• Microsoft: Creating a Log File — official context relevant to it.
• Microsoft: Introduction to CLFS — official context relevant to it.

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