Topology construction failing due to a NullReferenceException

Management Pack fails to build the environmental topology. The vmspi.log (default location: C:\Program Files\Veeam\Veeam Virtualization Extensions for System Center\Collector\Log) contains the following entries:
 

+** System.NullReferenceException: Object reference not set to an instance of an object. at nworksCore.TopologyNode.Clone()

Some host hardware objects may fail to return mandatory properties, such as NIC MAC address or NIC name. In this case Veeam Colelctor would fail to process such objects.
 

The hotfix prevents Veeam Collector from crashing and provides additional output about the object with missing properties.

Follow these steps to apply the fix.

1. Stop Veeam VMware Collector service.
2. Make a backup of VeeamCollector.Core.dll (default path: C:\Program Files\Veeam\Veeam Virtualization Extensions for System Center\Collector).
3. Open a cmd prompt on the collector host and run the command: 
   C:\Windows\Microsoft.NET\Framework\v4.0.30319\installutil.exe /u “<the collector folder path>\VeeamCollector.Core.dll”
   In case you have several collectors, run the command for each one.
4. Unpack the downloaded .zip and replace VeeamCollector.Core.dll with the file from the archive.
5. Make sure that you have full access right to the replaced .dll file (Permissions: Full Control) and the Unblock option is not activated in the file properties (Properties: General).
6. Open a cmd prompt on the collector host and run the command: 
   C:\Windows\Microsoft.NET\Framework\v4.0.30319\installutil.exe /i “<the collector folder path>\VeeamCollector.Core.dll”
   "The transacted install has completed" message should appear in case of correct .dll installation. If you have several collectors, run the command for each one. 
7. Start Veeam VMware Collector service.

NOTE: In case you installed the Update 5 for Veeam Management Pack and the issue occurred again, reapply the hotfix from this KB article.

DOWNLOAD THE HOTFIX

MD5 checksum for KB2130.zip is 7f7ba9bd970563b8af0d8e7ef1a058a8

Should have any questions, contact Veeam Support.