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;Veeam Smart Plug-in (SPI) for VMware
Version:
5.6
Published:
Last Modified:
2011-11-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.

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

OK

Rate the quality of this KB article: 
5 out of 5 based on 3 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:

Submit