duplicati/duplicati · warning · UserInformationException

HandleCloseError

HandleCloseError

Error message

Failed to close file handle on CreateFolderAsync with status {status}

What it means

Thrown in the CreateFolderAsync finally block when CloseFile on a just-created directory handle returns non-SUCCESS. Reported under code HandleCloseError. The directory may have been created, but the handle did not close cleanly, so resource state is uncertain.

Source

Thrown at Duplicati/Library/Backend/SMB/SMBShareConnection.cs:216

                            AccessMask.GENERIC_WRITE | AccessMask.SYNCHRONIZE,
                            FileAttributes.Normal,
                            ShareAccess.None,
                            CreateDisposition.FILE_CREATE,
                            CreateOptions.FILE_DIRECTORY_FILE | CreateOptions.FILE_SYNCHRONOUS_IO_ALERT,
                            null
                        );
                        if (status != NTStatus.STATUS_SUCCESS &&
                            status != NTStatus.STATUS_OBJECT_NAME_COLLISION) // Ignore if directory already exists
                            throw new UserInformationException($"{LC.L("Failed to create directory")} {currentPath} with status{status}", "CreateDirectoryError");
                    }).ConfigureAwait(false);
                }
                finally
                {
                    if (fileHandle != null)
                    {
                        var status = _smbFileStore.CloseFile(fileHandle);
                        if (status != NTStatus.STATUS_SUCCESS)
                            throw new UserInformationException($"{LC.L("Failed to close file handle on CreateFolderAsync")} with status {status.ToString()}", "HandleCloseError");
                    }
                }
            }
        }
        finally
        {
            _semaphore.Release();
        }
    }

    /// <summary>
    /// Lists the folder contents of the share and path specified in the connection parameters.
    /// </summary>
    /// <param name="path">Path to list</param>
    /// <param name="cancellationToken">Cancellation Token</param>
    /// <exception cref="UserInformationException">Exception to be displayed to user</exception>
    public async Task<List<IFileEntry>> ListAsync(string path, CancellationToken cancellationToken)
    {

View on GitHub (pinned to 3f348be3e3)

Solutions

1. Verify the directory was actually created via GetEntryAsync before treating the error as fatal.
2. Retry CreateFolderAsync once; COLLISION handling makes it idempotent for existing segments.
3. Reconnect the SMB session if close failures persist (the session may be broken).
4. Update/inspect the target server for known close-status bugs if it is reproducible.

Example fix

// before: a close error aborts the whole folder creation
await conn.CreateFolderAsync(path, ct);

// after: tolerate a close error if the directory now exists
try { await conn.CreateFolderAsync(path, ct); }
catch (UserInformationException ex) when (ex.HelpID == "HandleCloseError")
{ if (await conn.GetEntryAsync(path.TrimEnd('/') + "/", ct) is null) throw; }

// after a create+close, confirm the directory now exists
var ok = await conn.GetEntryAsync(currentPath.TrimEnd('/') + "/", ct);

static bool IsHandleCloseError(UserInformationException e) => e.HelpID == "HandleCloseError";

try { await conn.CreateFolderAsync(path, ct); }
catch (UserInformationException ex) when (ex.HelpID == "HandleCloseError")
{ if (await conn.GetEntryAsync(path.TrimEnd('/') + "/", ct) is { IsFolder: true }) return; throw; }

When it happens

Trigger: After a CreateFile for a directory segment, the finally block calls _smbFileStore.CloseFile(fileHandle) and gets a status other than STATUS_SUCCESS.

Common situations: Transient network drop during the close; server under load; handle already torn down by a transport reset; recurring server firmware/driver bug returning non-SUCCESS on directory closes.

Related errors

• CloseFileError
• CreateDirectoryError
• DirectoryOpenError
• CIFSConfig
• ConnectionError

AI-assisted analysis of duplicati/duplicati@3f348be3e3 (2026-08-13). Data as JSON: /api/errors/88e0d79d469712fc. Report an issue: GitHub.