#1 Global Leader in Data Protection & Ransomware Recovery

Veeam Agent Standalone Backup Fails with "Version string portion was too short or too long"

KB ID: 4421
Product: Veeam Backup & Replication | 12
Veeam Agent for Microsoft Windows | 6.0
Veeam Agent for Linux | 6.0
Veeam Agent for IBM AIX | 4.1
Veeam Agent for Oracle Solaris | 4.0
Published: 2023-03-08
Last Modified: 2023-05-08
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

After upgrading Veeam Backup & Replication to version 12, the following tasks for Standalone Veeam Agent (i.e., Veeam Agent for Microsoft Windows, Veeam Agent for Linux, Veeam Agent for IBM AIX, and Veeam Agent for Oracle Solaris) deployments that existed before the upgrade may fail.

  • Running Standalone Veeam Agent backup job
  • Re-configuration of pre-existing Veeam Agent jobs
  • Attempting to remove Veeam Agent jobs from Veeam Backup & Replication console


Those tasks will fail with the error:

Version string portion was too short or too long
Update: Veeam Backup & Replication 12 P20230412
This issue has been resolved in Veeam Backup & Replication 12 P20230412. If you are upgrading from a previous version (before 12) of Veeam Backup & Replication using the latest install ISO, this issue will not occur. The fix contained in the Cumulative Patch (P20230412) is only preventative. If the error documented in this article does occur, please use the method documented in the Solution section to resolve the issue.

Cause

This issue is caused by a change in how Veeam Backup & Replication 12 tracks OS version information from Standalone Veeam Agent deployments.

This issue only affects standalone Veeam Agent deployments that were communicating with the Veeam Backup Server before the upgrade to version 12.

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:

  1. Back up the Veeam Backup & Replication Configuration Database.
  2. 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='';

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 reuse 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 submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.