256 results:

  1. Error 577: Windows can't verify driver during Hyper-V Run Direct

    Hyper-V Run Direct restore fails with Error 577: Windows cannot verify the driver’s digital signature due to unsigned or damaged system file.

  2. Error: NFS service not running during VMware Run Direct restore

    NFS Service must be running and ports 111, 1058, 2049 open for VMware Run Direct restore to work with Ahsay on Windows.

  3. Backup Error: Failed to flush buffer to this destination

    Backup fails with "Failed to flush buffer to this destination" due to unstable network connection between AhsayOBM/AhsayACB client and backup destination.

  4. HTTP Error 400: Download failed during AhsayACB installation

    AhsayACB install fails on Windows or MacOS X with "HTTP error 400: Bad request" when downloading files. Check your internet connection and retry.

  5. Error: Invalid sClientid shown after selecting Google Drive restore

    Restore fails with "[GDriveManager.getAppName] Invalid sClientid: null" error after selecting Google Drive as the backup destination in AhsayOBM/ACB.

  6. File Backup Error: "[IOException] [NixUtil.c][read] Invalid argument"

    AhsayOBM file backup on Linux fails with "[IOException] [NixUtil.c][read] Invalid argument" error shown in the backup log.

  7. Error: invalid_access_token when restoring to Dropbox

    Restore on AhsayOBM fails with "invalid_access_token" error when accessing Dropbox backup destination due to authentication failure.

  8. Hyper-V Granular Restore error "Failed to list file"

    Granular restore of a Hyper-V VM fails with "The volume does not contain a recognized file system" error when mounting the virtual disk in AhsayOBM.

  9. "Connection refused" error when enabling AhsayCBS Replication

    Fix the "Connection refused" replication error in AhsayCBS caused by an incorrect SSL Port or Network configuration settings

  10. Failed to enable replication on AhsayCBS

    "Failed to mkdir" or "Failed to list path" error when enabling replication caused by incorrect replication receiver settings