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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxMjY3IiwiaGFzaCI6ImMzMTQ3NGJjLWRjMDMtNDU5Yi05ZjNjLWY1ZjU0NTE2NmU0OSJ9
After the "maindb.xml" file has been re-created the collector gets lost in nworks Enterprise Manager
| KB ID: | 1267 |
| Product: | Veeam Management Pack for Microsoft System Center |
| Version: | 5.6 |
| Published: | 2011-10-06 |
| Last Modified: | 2020-08-28 |
Challenge
The collector gets lost in nworks Enterprise Manager. After the "maindb.xml" file has been recreated, the collector gets lost in nworks Enterprise Manager.
Cause
This can happen if two collectors have the same ID. In this case one of them will not be shown in the nworks UI after "maindb.xml" recreation.
Solution
To resolve this:
1. Stop "Nworks Virtual Infrastructure Collector service" service on the affected collector.
2. Locate the following key in the registry on the collector:
HKEY_LOCAL_MACHINE\SOFTWARE\nworks\VIC\Collector
3. Remove the "CollectorID" value.
4. Start "Nworks Virtual Infrastructure Collector service" on the affected collector.
More information
This is fixed in nworks v5.7.
| KB ID: | 1267 |
| Product: | Veeam Management Pack for Microsoft System Center |
| Version: | 5.6 |
| Published: | 2011-10-06 |
| Last Modified: | 2020-08-28 |
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!
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
