267 results:

  1. 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.

  2. Unable to launch AhsayOBM due to missing MSVCP140.dll

    Fix AhsayOBM GUI error caused by Windows CU updates. Apply Ahsay hotfix v10.1.0.24 to CBS and enable Auto-update until official v10.1.2 release.

  3. Microsoft 365 Backup Fails with Multi-Factor Authentication Error

    Seeing "MFA enabled... not authorized" in Microsoft 365 Backup? Microsoft MFA enforcement is the cause. Upgrade to v10.1.0 + HF 10.1.0.25 to resolve

  4. Windows System State Backup error "Enumeration of the files failed"

    This troubleshooting article contains resolution and list of possible cause of "Enumeration of the files failed" error in Windows System State backup

  5. AhsayOBM Windows Backup Error: Temp Path Included in Backup Source

    Windows System backup fails if the temp location is on the same volume as the backup source. Select a different volume to meet WBAdmin requirements.

  6. Hyper-V VSS error: hr=0x80070005, Access is denied

    Troubleshoot Hyper-V Backup/Restore error "Unexpected error querying for the IVssWriterCallback interface. Access is denied (hr=0x80070005)

  7. OBM File Backup errors on OneDrive Folder with Files On-Demand enabled

    Fix OneDrive file backup issues caused by File On-Demand feature and configure settings for successful backups

  8. Missed Backup: Login to ACB/OBM Failed Due to Expired SSL Cert

    Backups failed due to an expired SSL certificate preventing ACB/OBM login. Learn how to renew the certificate and restore connectivity to avoid data loss.

  9. "Microsoft SQL Server not found" warning on Microsoft SQL backup

    Learn how to grant necessary permissions to the backup account to resolve AhsayOBM backup warning "Microsoft SQL Server not found"

  10. MS SQL ODBC Backup Fails: Device Name Length Exceeds Limit

    SQL backup fails due to device name exceeding 259-character limit. Shorten the temp path or DB name, or use VSS mode in AhsayOBM to resolve the issue.