Veeam Availability Orchestrator stops collecting vCenter asset information

Veeam Availability Orchestrator
Last Modified:


There is an issue with the embedded Veeam ONE component of Veeam Availability Orchestrator 1.0 release. The issue results in Veeam ONE not recognizing new VMware vCenter assets approximately 90 days after installation.


There is a synchronization issue between Veeam ONE Monitor and Veeam ONE Reporter components.


The issue can be easily resolved by following the steps below:

For new VAO installations:
Download the updated ISO image from our website. The ISO already contains the patch and can be installed normally.

For existing VAO installations:
1. Download VAO updater
MD5: 734167ff040d6b399970d5d57bf50f26
2. Run the updater

NOTE: The updater should be run on every Veeam Availability Orchestrator server.

The patch installation on an existing system can be confirmed by checking the modified timestamp on the following files: 
%PROGRAMFILES%\Veeam\Availability Orchestrator\Veeam ONE Reporter Server\SchedulingService.exe <created date 07.08.2018>
%PROGRAMFILES%\Veeam\Availability Orchestrator\Veeam ONE Reporter Web\Bin\ReporterApp.dll <created date 07.08.2018>

More Information

Should you have any questions, contact Veeam Support.

Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.


Rate the quality of this KB article: 
5 out of 5 based on 2 ratings

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: