1-800-691-1991 | 9am - 8pm ET

Collection of historical performance data fails after upgrading to vSphere 5.5 Update 3

KB ID: 2071
Product: Veeam ONE
Version: 8.x
Published: 2015-11-02
Last Modified: 2020-08-13


After update to vCenter 5.5 U3 historical performance collection fails with error "Unable to collect performance. A specified parameter was not correct. querySpec.size".


With vCenter 5.5 Update 3 VMware has limited the size of query in order to protect the vCenter database (more information can be found in this VMware KB article).


At the moment two workarounds are available.

1. Disable the collection of historical information as described in the following KB article. This will effectively turn off the collection of historical data for all vCenter servers added to your installation of Veeam ONE.

or, alternatively,

2. Download and apply build With build the collection of historical information will be disabled for vCenter servers 5.5 Update 3 and later. vCenter versions prior to 5.5 U3 will not be affected. 

To apply build, run the executable file on the machines containing Veeam ONE services, as well as on all machines, where Veeam ONE Monitor Client is installed.

More information

If you have any questions, please contact Veeam Support.
KB ID: 2071
Product: Veeam ONE
Version: 8.x
Published: 2015-11-02
Last Modified: 2020-08-13

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 are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

ty icon

Thank you!

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


error icon

Oops! Something went wrong.

Please go back try again later.