Skip to main content

Veeam Endpoint Agent Blocks the BDR Upgrade (Outdated Agents, Error 1714)

Field Detail
Audience T2
Version 1.0
Last Updated October 2026
Applies To Veeam B&R 13.1.1.18 BDRs and the Veeam Agent for Windows endpoints they protect
Source HALO 1179664

Signal

  • The upgrade run ends RESULT: ... exit=1603 with SETUP ERROR: Outdated Veeam Agents, followed by one object: line per blocking endpoint — for example object: <endpoint> (Veeam Agent for Windows 6.2.0.121).
  • The NinjaOne script Veeam DB Issues Report prints DBISSUE| lines naming the blocking endpoints.
  • Pushing or upgrading the agent fails with MSI Error 1714 — "The older version of Veeam Agent for Microsoft Windows cannot be removed."

Veeam setup refuses to install while any registered agent is too old to upgrade. One switched-off workstation blocks the whole BDR.

Fix

1. Name every blocking endpoint

Read the object: lines in the BDR's latest upgrade log, or run Veeam DB Issues Report on the BDR. It's read-only: it reads the database-issues report setup leaves behind (C:\ProgramData\DTC\Logs\VeeamUpgrade\VbrDatabaseIssuesSetupReport.xml) and prints each blocking object, with the file's timestamp so you can tell whether it's current.

The upgrade log also says, per endpoint, whether Veeam sees it Online or Offline.

2. Act on each endpoint

The endpoint is Do this
Online Re-run Veeam v13 Upgrade on the BDR. It upgrades online agents first, then installs.
Offline — the PC is switched off Re-run the upgrade during business hours with the PC on.
Online in NinjaOne but Offline to Veeam, or upgrades fail with Error 1714 Run Repair-VeeamAgentRegistration on the endpoint (below).
Agent install is corrupt — Error 1605 Follow Veeam Agent — Corrupt Install: Force Removal & Clean Redeploy.
Decommissioned — the machine is gone for good Remove it from the protection group in the Veeam console, then re-run the upgrade.

Never remove a registration just because it shows Offline. A machine that's merely unreachable may still be a live server. The upgrade script never removes one for the same reason.

3. Repair-VeeamAgentRegistration, on the endpoint

Every Error 1714 seen during the v13 upgrade traced to a pending reboot on the endpoint. The script runs on the protected endpoint, not the BDR:

  1. mode=report (the default) changes nothing and reports what it found.
  2. mode=repair: if a pending reboot is what blocks the agent, it reboots the endpoint with 60 seconds' notice. Otherwise it removes the broken old agent so the BDR can push a current one.

Repair mode reboots user PCs and servers, so run it outside working hours, or coordinate with the office first.

Verify

  • The next upgrade run on the BDR passes the agent check.
  • In the console, each endpoint shows Online with a current agent version.
Version Date Author Change
1.0 October 2026 Z. Boogher Initial release from the v13 upgrade (HALO 1179664).
Back to top