Carbonite Support > Message: "An Operation Failed ...

Message: "An Operation Failed Unexpectedly"

Summary:

In certain scenarios, an operation in CSSB may fail with a very simple error message that simply says <Operation> failed or The <Operation> failed unexpectedly.

The <Operation> may be a backup, upload, download, or restore. Examples of error messages include:

  • Backup failed
  • Upload failed
  • Download failed
  • Restore failed

These very short, very simple error messages are how CSSB indicates that the operation failed in an unknown or unexpected manner.

Cause:

The two most common reasons for an <Operation> failed error message are:

  • The system was rebooted or powered off during the operation. Learn more...
  • One or more of CSSB's services or processes crashed
To avoid damaging the backup archive, operations that are interrupted by an unexpected failure will not be resumed automatically. In most cases, the operation cannot be resumed manually, for the same reason. If there is a chance the backup archive was damaged, the options to resume will be greyed out and cannot be selected.

This article applies to:

Carbonite Plans Products Platforms
Power and Ultimate (Not sure?) Carbonite Safe Server Backup (Not sure?) Windows

Solution:

  • If an incremental or differential backup failed unexpectedly, you should start a new differential or full backup in order to ensure you have a complete backup cycle.
  • If a full backup failed, start a new full backup.

Although rare, it is possible for one of CSSB's processes to crash. If a process crashes in the middle of an operation, the <Operation> failed error message may occur.

If you have received the <Operation> failed error message, and the system was not rebooted while the operation was in progress, please open your Windows Application Event Logs. Look for events related to crashes and faults in any combination of CSSB's processes. Please refer to our List of CSSB Services and Processes.

If any MSVCR*.dll is listed as the faulting module, please refer to One of CSSB's Processes Crash: The Faulting Module is MSVCR*.dll. If ntdll.dll is listed as the faulting module, ensure you're running the latest version of CSSB.

Feedback