- Veeam Support Knowledge Base
- After the "maindb.xml" file has been re-created the collector gets lost in nworks Enterprise Manager
After the "maindb.xml" file has been re-created the collector gets lost in nworks Enterprise Manager
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
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.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please try again later.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.