265 results:

  1. Invalid backup source shown for Exchange 2007 set after upgrade

    After upgrading AhsayOBM v6 to v7.3.2.0–7.5.0.2, Exchange 2007 backup sets may show invalid (red) source paths in the backup source selection.

  2. VMware backup job fails to complete with schedule disabled

    VMware backup job fails with "Backup Interrupted by Scheduler" if no schedule is set and job runs longer than 5 minutes in AhsayOBM

  3. 0 KB files accumulate on OneDrive during replication proces

    Replicating to OneDrive for Business may generate many 0 KB files in the root directory when set as a Predefined Destination.

  4. Encryption defaults to Custom in v6 New Backup Set Wizard

    When using the New Backup Set Wizard in AhsayOBM/ACB v6 with CBS v7.3.2.0–7.5.0.6, the encryption setting defaults to "Custom" by default.

  5. Incorrect "Another backup job is running" error on Exchange Mail Level

    Exchange Mail-Level backup shows incorrect "Another backup job is still running. Backup skipped." message in client interface or report, despite no job running.

  6. Incorrect client and add-on usage shown for Sub Admin account

    AhsayCBS web console may show 0 usage for client and add-on module quotas under Sub Admin account settings, even when quotas are actively in use.

  7. MS Exchange backup fails: Job interrupted with no schedule set

    MS Exchange backup jobs over 5 minutes fail with "Backup Interrupted by Scheduler" if no backup schedule is configured in the set.

  8. No database file found error on MS SQL Server backup

    MS SQL Server backup using AhsayOBM shows "No database file found for 'SERVER\DB_NAME'" warning in the backup report.

  9. Cannot customize AhsayACB/OBM names on Client download page

    Client download page still shows AhsayOBM/ACB names despite changes to %OBM_SHORT_NAME% and %ACB_SHORT_NAME%. Known issue in AhsayCBS version 7.5.0.0.

  10. UpdateFilter.do returns incorrect "Filter name in use" error

    Calling UpdateFilter.do API always returns "Filter name is already in use" error, even when updating an existing filter. Error message is incorrect.