https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMjUwIiwiaGFzaCI6ImFiNDRkZTk3LWExMGEtNDgyNS1iY2NiLTA2MzEwNDZhNWQ3MSJ9
1-800-691-1991 | 9am - 8pm ET
EN

Version string portion was too short or too long

Challenge

When trying to configure Veeam ONE Reporter data collection tasks, the following error message pops up:
Version string portion was too short or too long

Cause

The issue is due to manual Veeam ONE database deployment that leaves blank fields in the common.serversettings table required for correct product functioning.

Solution

Before applying the instructions below, make sure you have a full backup of Veeam ONE SQL database.

To find out the Windows version, on Veeam ONE server open CMD and run ver command. Use the x.x.x.x format.

Run the following queries against Veeam ONE database, substituting the fields marked in red with appropriate values:

exec common.SetSetupDataReporterURI 'https://reporterfqdn:1239/'
go

exec common.SetSetupDataBusinessViewURI 'https://businessviewfqdn:1340/'
go
exec common.SetSetupDataWindowsVersion '%WINVERSION%'
go


 

More information

If you have any questions, contact Veeam Support.
KB ID:
2250
Product:
Veeam ONE
Version:
since v6.0
Published:
2017-03-01
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.