Skip to main content

NinjaOne Backup — VSS Error 132: Overview & General Triage

Audience: T2 Use when: Backup fails with "VSS Error (132)..." or any error message referencing Volume Shadow Copy Service.

VSS errors are Windows OS errors — not NinjaOne errors. NinjaOne cannot take a backup of open files without a successful VSS snapshot. The error code after "132" identifies the specific VSS failure condition.

What VSS Is and Why It Matters

VSS (Volume Shadow Copy Service) is a Windows feature that allows backup software to snapshot a volume while files are in use. Without a successful VSS snapshot, Lockhart cannot safely read open files like dental databases (Dentrix Actian, Eaglesoft SQL Anywhere, Open Dental MySQL). These files are always open during business hours — and often after hours too.

When VSS fails, the backup either fails entirely or completes with warnings about skipped open files.

General Triage — Always Start Here

# Step 1: List all VSS writers and their status
vssadmin list writers

# Step 2: Check for shadow copies on the volume
vssadmin list shadows

# Step 3: Verify VSS service is running
Get-Service VSS, SWPRV | Select DisplayName, Status, StartType

Healthy VSS writer output looks like:

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {...}
   State: [1] Stable
   Last error: No error

Any writer showing State: [6] Failed or State: [5] Waiting for completion (stuck) needs attention.

VSS Error Sub-Codes After 132

The full error message contains a hex code after "VSS Error (132)". Match it here:

Hex Code Meaning First Action
0x80042302 Provider not registered — VSS DLLs corrupt Re-register VSS DLLs (see DLL page)
0x80042301 Shadow copy set missing provider Re-register VSS DLLs
0x80042306 Writer timed out Check which writer; restart its service
0x8004230c Snapshot limit reached — old shadows not pruned Run vssadmin delete shadows /all /quiet
0x80070070 Insufficient disk space for shadow copy Free space on the source volume (see Error 307)
0x8004230f XML document invalid Windows Update pending or failed — ensure clean reboot state
0x80042313 Object not found — VSS DLL issue Re-register VSS DLLs

General Resolution Path

Step 1 — Reboot (resolves the majority of VSS errors)

Most VSS writer failures clear on reboot. Schedule after-hours:

  • Confirm no users active
  • Reboot the server
  • After reboot: vssadmin list writers — confirm all writers show [1] Stable
  • Let the next scheduled backup run; verify success

Step 2 — Restart the specific failing writer's service

If a named writer is in failed state:

# Common writers and services
# SqlServerWriter → MSSQLSERVER (or named instance)
# NTDS Writer → Active Directory (requires DC reboot — see Error 309 page)
# System Writer → CryptSvc
# Hyper-V Writer → vmms
# WMI Writer → Winmgmt

# Example: restart SQL Server writer
Restart-Service -Name MSSQLSERVER -Force

# Re-check
vssadmin list writers

Step 3 — Check for conflicting backup software

Old MSP360/CloudBerry VSS providers frequently conflict:

Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*",
"HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*" |
Where-Object {$_.DisplayName -like "*MSP360*" -or $_.DisplayName -like "*Cloudberry*" -or $_.DisplayName -like "*Online Backup*"} |
Select DisplayName, DisplayVersion

If found: uninstall, reboot, retry.

Step 4 — Re-register VSS DLLs

See dedicated page: NinjaOne Backup — VSS DLL Re-registration & Writer Repair

Escalate to T3 If:

  • Multiple writers simultaneously failed — may indicate deeper Windows corruption
  • VSS errors return within days of a reboot and DLL re-registration
  • This is the only DC at the site and NTDS writer is failing (no safe reboot window)
Back to top