BA617: Volume Shadow Copy writer metadata could not be collected¶

Error code	Product	Applies to
BA617	BackupAssist	For BackupAssist 15.0.5 or later.

Description¶

To produce an application-consistent backup, BackupAssist queries the Windows Volume Shadow Copy Service (VSS) at the start of a System Protection backup to discover which VSS writers (for example SQL Server, Exchange and Hyper-V) are present and which volumes they require. This step is called gathering writer metadata.

BA617 is reported when that query cannot be completed: the VSS writer infrastructure on the machine is unavailable, or one or more writers are unresponsive or in an error state, so Windows cannot return the writer metadata. BackupAssist first attempts to recover the VSS-related Windows services automatically; BA617 is raised only when the backup still cannot query the writers after that recovery, and the backup is stopped.

Common causes:

A Windows update left a VSS writer (for example SqlServerWriter) in a non-retryable error state.
A writer-host service (SQL Server, Exchange, Hyper-V Management) is stopped, hung or crashing.
The VSS writer infrastructure itself is unhealthy and needs the VSS-related services to be restarted, or the machine to be rebooted.
A very large or busy writer (for example a SQL Server instance with many databases) takes longer than the allowed time to return its metadata.

Resolution¶

The VSS writer infrastructure usually recovers when its services are restarted. The simplest reliable fix is to reboot the machine and run the backup again.

If you cannot reboot immediately, restart the core VSS services:

Open an elevated command prompt (Run as administrator).
Run "net stop VSS" and then "net start VSS".
Restart the writer-host service for the writer that failed - for example the relevant SQL Server (instance) service for SqlServerWriter.
Run the System Protection backup again.

Resolution 2 - Identify and fix the writer in an error state¶

If the problem returns, identify which writer is failing so the underlying application can be addressed.

Open an elevated command prompt.
Run "vssadmin list writers".
Look for any writer whose State is not [1] Stable, or whose Last error is not No error - that writer is the cause.
Restart that writer's application/service, or apply the relevant vendor or Windows fix. If the failure began immediately after a Windows update, check the application vendor's guidance for that update.
Run the backup again and confirm the writer reports No error.

Resolution 3 - Increase the writer metadata query timeout (advanced)¶

Only relevant when BA617 is caused by a slow but otherwise healthy writer (a large or busy SQL Server instance, for example) rather than a broken one. The time allowed for the writer metadata query can be extended with a registry value.

Under HKEY_LOCAL_MACHINE\SOFTWARE\Cortex I.T\BackupAssist\v{major} create or edit the string value VssQueryTimeoutSecs and set it to a number of seconds higher than the default of 600 (all BackupAssist registry values are text/REG_SZ). Run the backup again. Do not use this to mask a writer that is genuinely in an error state - resolve the writer with Resolution 1 or 2 instead.

Note on the backup report¶

The backup report shows this condition as: Could not collect Volume Shadow Copy writer metadata; the VSS writer infrastructure is unavailable or unresponsive. Restart the VSS-related services or reboot, then retry the backup.

The report also includes the underlying Windows VSS error code (for example 0x80042318, VSS_E_WRITER_INFRASTRUCTURE) to help support diagnose the failing writer. When BA617 is reported, the generic condition BA1 ("Unhandled exception in the Backup Executor") is not shown for this failure.

Last updated	Created	Further assistance
6th Aug 2026	6th Aug 2026	BackupAssist Support page

Download a free 30-day trial