Symptoms
Backup fails with:
Windows error: (0x800705AA) Insufficient system resources exist to complete the requested service
Troubleshooting
Check Event Viewer log on the affected Agent machine. Search for possible errors and warnings from following sources: volsnap, atapi, disk, BitLocker-Driver, Ntfs. For more information on how to use Windows Event log see this article.
Find an appropriate event source and event ID in the table below and proceed as described in the "Troubleshooting" section.
Solution
Check the table below for messages found in Event Viewer and follow the troubleshooting steps
| Provider name | EventID | Message | Troubleshooting |
| Volsnap | 8 | The flush and hold writes operation on volume C: timed out while waiting for a release writes command. | This error means that the machine has too much I/O going on. Check what activities were going on during the backup, e.g. antivirus check, windows update, etc and reschedule either this action or backup task |
| Volsnap | 24 | There was insufficient disk space on volume C: to grow the shadow copy storage for shadow copies of C:. As a result of this failure all shadow copies of volume C: are at risk of being deleted. | There is not enough space for snapshot storage. Free up space on the disk or move the storage to a volume with more free space. See this article for instructions. |
| Volsnap | 25 | Insufficient space on <X> drive to grow the snapshot storage. Snapshot storage is dropped. | There is not enough space for snapshot storage. Free up space on the disk or move the storage to a volume with more free space. See this article for instructions. |
| Volsnap | 27 | The shadow copies of volume <X> were aborted during detection because a critical control file could not be opened. | This issue requires investigation.Collect Acronis system information from the affected machine and contact Acronis Support with a reference to this article |
| Volsnap | 29 | The shadow copies of volume <X> were aborted during detection. | This issue requires investigation.Collect Acronis system information from the affected machine and contact Acronis Support with a reference to this article |
| Volsnap | 35 | The shadow copies of volume <X> were aborted because the shadow copy storage failed to grow. | There is not enough space for snapshot storage. Free up space on the disk or move the storage to a volume with more free space. See this article for instructions. |
| Volsnap | 36 | The shadow copies of volume <Х> were aborted because the shadow copy storage could not grow due to a user imposed limit. | There is not enough space for snapshot storage. Free up space on the disk or move the storage to a volume with more free space. See this article for instructions. |
| Volsnap | 33 | The oldest shadow copy of volume C: was deleted to keep disk space usage for shadow copies of volume C: below the user defined limit. | There is not enough space for snapshot storage. Free up space on the disk or move the storage to a volume with more free space. See this article for instructions. |
| atapi | 11 | The driver detected a controller error on <device_path> | This message appears in case of hardware problems with either the controller, cable or a device that is attached to the controller in question. |
| Disk | 7 | The device, <device_path>, has a bad block. | Check and fix errors on the disk with chkdsk: click Start, in Search type cmd, right-click cmd.exe -> Run as administrator. At a command prompt, type the following command: |
| Disk | 11 | The driver detected a controller error on <device_path>. | This message appears in case of hardware problems with either the controller, cable or a device that is attached to the controller in question. |
| Disk | 15 | The device, <device_path>, is not ready for access yet. | Ensure that drivers for this disk are correct and up to date. Verify that disk is accessible and initialized. |
| Disk | 51 | An error was detected on device <device_path> during a paging operation. | This message usually means a hardware problem with the drive or its controller. Test the hard drive with diagnostic utility provided by the manufacturer. |
| Disk | 153 | The IO operation at logical block address 0xaf34080 for Disk 0 (PDO name: \Device\00000034) was retried. | Check and fix errors on the disk with chkdsk: click Start, in Search type cmd, right-click cmd.exe -> Run as administrator. At a command prompt, type the following command: |
| Disk | 157 | Disk <X> has been surprise removed. | Do not remove disk during backup. Make sure the drive is not going to Sleep mode: go to Control Panel -> Power Options -> Change Plan settings -> Change advanced power settings. In Power Options box that opens, click the + sign next to the Hard Disk option. Here you will see the required settings under Turn off hard disk after heading. Change the value to 0. |
| Microsoft-Windows-BitLocker-Driver | 24620 | Encrypted volume check: Volume information on cannot be read. | If you are using BitLocker, this error indicates that a volume has bad blocks. If you aren't using BitLocker on this machine, this error appears when BitLocker service tries to enumerate a device but fails. This happens if the one or more disks in the machine are encrypted by a different encryption software. |
| Ntfs | 50 | Windows was unable to save all the data for the file <path_to_the_file>. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. | This issue requires investigation.Collect Acronis system information from the affected machine and contact Acronis Support with a reference to this article |
| Ntfs | 55 | The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume OS. | Ensure the disk controller firmware and drivers are current. Ensure any third-party storage drivers and firmware are up to date. Run chkdsk utility on the affected volume. |
| Ntfs | 137 | The default transaction resource manager on volume <volume label> encountered a non-retryable error and could not start. The data contains the error code. | Check and fix errors on the disk with chkdsk: click Start, in Search type cmd, right-click cmd.exe -> Run as administrator. |
| Microsoft-Windows-Ntfs | 140 | The system failed to flush data to the transaction log. Corruption may occur in VolumeId: C:, DeviceName: \Device\HarddiskVolume2. (The I/O device reported an I/O error.) | Check and fix errors on the disk with chkdsk: click Start, in Search type cmd, right-click cmd.exe -> Run as administrator. |
How to collect system information - see the following articles for instructions: