Veeam Agent for Microsoft Windows Standalone Backup Fails with "Version string portion was too short or too long"
Challenge
After upgrading Veeam Backup & Replication to version 12, the following tasks for Standalone Veeam Agent for Microsoft Windows deployments that existed before the upgrade may fail.
- Running Standalone Veeam Agent for Microsoft Windows backup job
- Re-configuration of pre-existing Veeam Agent for Microsoft Windows jobs
- Attempting to remove Veeam Agent for Microsoft Windows jobs from Veeam Backup & Replication console
Those tasks will fail with the error:
Version string portion was too short or too long
Cause
Solution
Option 1: Support-Assisted Resolution
The resolution to this involves modifying the Veeam Backup & Replication Configuration Database. Veeam Support understands that some customers may not be comfortable performing this task, and we welcome you to contact Veeam Support for assistance. Our Support Engineers will assist with making the database changes necessary to resolve this issue.
Option 2: Self-Service Resolution
Customers with an understanding of how to execute a SQL query and are comfortable with making modifications to their Veeam Backup & Replication Configuration Database directly are welcome to follow these steps to resolve the issue:
- Back up the Veeam Backup & Replication Configuration Database.
- Locate the Veeam Backup & Replication Configuration Database and execute the following query to update all conflicting OS version entries.
- For Microsoft SQL:
update dbo.[Backup.Model.EpHosts] set os_version='0.0' where os_version='' - For PostgreSQL:
UPDATE "backup.model.ephosts" SET os_version='0.0' WHERE os_version='';
- For Microsoft SQL:
Note: Starting with Veeam Backup & Replication 12, the configuration database can be hosted using either MS SQL or PostgreSQL. As this issue only affects environments where Veeam Backup & Replication was upgraded, and an upgrade will always use the existing database engine, most customers facing this issue will still be using Microsoft SQL. If, however, after upgrading to Veeam Backup & Replication 12, the configuration database was migrated to PostgreSQL, use the appropriately formatted query for PostgreSQL.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.