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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxNjY0IiwiaGFzaCI6IjE5ZWE4ZWJhLTEyMTMtNDc1YS1hYjkzLWY3M2MzMmJhZWJlMSJ9
1-800-691-1991 | 9am - 8pm ET
EN

Virtual Infrastructure topology is not available in SCOM console

Challenge

Despite everything seems to be normal in Veeam Extension Services, the Veeam Collector log does not contain errors, and file OmTopology.xml is created in the Collector installation folder,  Veeam views in SCOM are empty.

OperationsManager logs on the Collector server contain events 999, with the following message:

Error Loading XML document C:\Program Files\Veeam\Veeam Virtualization Extensions for System Center\Collector\Log\OmTopology.xml - No data is available for the requested resource.​

Cause

Run as account Default Action Account (default Monitoring Agent Action Account) does not have permissions to read from the location where the Collector is installed, typically C:\Program Files\Veeam\Veeam Virtualization Extensions for System Center\Collector​

Solution

You should either add permissions to read from Collector installation folder for the SCOM Run as account or add this account to the local administrator group on the Veeam Collector server.

More information

If you have any questions, please contact Veeam Support at www.veeam.com/support
KB ID:
1664
Product:
Veeam Management Pack for Microsoft System Center
Version:
all
Published:
2012-07-20
Last Modified:
2020-08-28
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.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later