NAS Codex › Synology › Synology Active Backup for Business: unable to take a snapshot (0x80042308, 0x80042301, 0x80042316)

Synology Active Backup for Business: unable to take a snapshot (0x80042308, 0x80042301, 0x80042316)

Active Backup for Business backs up a Windows PC or physical server from a Volume Shadow Copy Service (VSS) snapshot taken on that computer. When Windows can't take or keep that snapshot, the task fails or ends partially complete and the log shows an error code. Synology's error code index and its per-code articles say what each code means and what to check on the Windows side.

Written against: Active Backup for Business Agent on Windows, DSM 7 (Synology KB articles last updated Feb 25, 2022, Nov 29, 2023 and Sep 22, 2026). Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.

Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.

Fast Answer

Read the error code in the task log first. For 0x80042308, Synology starts with chkdsk /F /R X: on the affected volume and more shadow storage (Max Usage) in System Protection. For 0x80042301, set the Microsoft iSCSI Initiator Service, Microsoft Software Shadow Copy Provider and Volume Shadow Copy services to Automatic and running. For 0x80042316, remove other backup software and extra VSS providers. For all three, run vssadmin list writers and restart the service behind any writer that is not Stable.

What the codes mean

Synology's index of backup and restore error codes lists these for Windows PCs and physical servers:

The same index lists further snapshot codes, including 0x8004230C (the device fails to take a snapshot for a volume), 0x80042313 (excessive activity on the volume), 0x80070008 (VSS cannot allocate enough system resources) and 1117 (access to snapshots failed due to an I/O device error). Each links to its own Synology article.

0x80042308: the agent can't find the snapshot

Synology's diagnosis: the Active Backup for Business Agent could not find the snapshot that was created during backup. Its four methods:

  1. Check and fix the volume. Open Command Prompt and run chkdsk /F /R X:, replacing X with the letter of the volume where the snapshot failed. If chkdsk says the volume is in use and asks to schedule the check for the next restart, enter Y.
  2. Reserve more shadow storage. Press Windows + R, enter systempropertiesprotection and click OK. On the System Protection tab, select the volume and click Configure. Under Disk Space Usage, set Max Usage; Synology suggests trying 100% first if you are not sure. Click OK and back up again. After the backup, check whether Current Usage almost reaches Max Usage; if it does, Synology says to switch to a larger drive and back up again.
  3. Check the VSS writers. From an administrator account, run vssadmin list writers. Every writer should be Stable. If one is not, go to Control Panel > System and Security > Administrative Tools > Services, right-click the service and select Restart, then run the command again.
  4. Install the latest Windows updates.

0x80042301: Windows failed to take the snapshot

Synology's diagnosis: the device failed to take snapshots for the specific volume. Synology notes this can also happen on volumes larger than 64 TB, which Windows VSS does not support.

  1. Click Start, type services.msc and press Enter. In Windows Services Manager, open each of these and set Startup type to Automatic:
    • Microsoft iSCSI Initiator Service
    • Microsoft Software Shadow Copy Provider
    • Volume Shadow Copy
    Restart the three services with Stop and Start, and make sure all three show Running.
  2. Run vssadmin list writers from a privileged account. If a writer is not stable, restart the related service and check again. Synology says you sometimes need to stop one of the VSS writers to resolve the issue, and gives the Oracle VSS Writer as an example of a writer that can cause snapshots to fail.
  3. Use Microsoft's System File Checker tool.

Synology adds that error code 0x80070008 may also appear when this happens.

0x80042316: another program is taking snapshots

Synology's diagnosis: other applications or systems are creating VSS snapshots at the same time, so the agent cannot take its own.

  1. Check for other backup software running on the computer and remove it before retrying.
  2. From an administrator account, run vssadmin list providers. If there are providers other than Microsoft Software Shadow Copy Provider and Microsoft File Share Shadow Copy Provider, remove them before retrying. If only those two remain and the error continues, Synology names software with compatibility issues to remove or take up with its vendor: Reboot Restore Rx, TuneUp Utilities 2009/2010/2011 and Kaspersky Removal Tools.
  3. Run vssadmin list writers and restart the service behind any writer that is not Stable.
  4. Restart the computer and retry the backup.
  5. Check that snapshot-taking works on Windows. If it fails there too, Synology says the device may not be able to take snapshots and to contact Microsoft Support.

When to stop and get help

Synology's last step for 0x80042316 applies to all three: if snapshot-taking fails in Windows itself, the device may not be able to take snapshots, and Synology says to contact Microsoft Support. On volumes larger than 64 TB, Windows VSS is not supported at all.

Questions

What does Active Backup for Business error 0x80042308 mean?

Synology says the Active Backup for Business Agent could not find the snapshot created during backup. Its fixes are chkdsk /F /R on the volume, more shadow storage (Max Usage), stable VSS writers and Windows updates.

How do I fix error 0x80042301 in Active Backup for Business?

Set Microsoft iSCSI Initiator Service, Microsoft Software Shadow Copy Provider and Volume Shadow Copy to Automatic and running, check vssadmin list writers, then run System File Checker.

What causes 0x80042316 in Active Backup for Business?

Synology says another application or system is creating VSS snapshots at the same time. Remove other backup software and any VSS providers other than Microsoft's two.

Sources

Every fact on this page comes from the vendor documents below, opened on 2026-11-17.