Security Compliance

Hyper-V network interface error: Unsupported configuration in SEM

The following error is typically logged in the Hyper-V-Worker log Hyper-V Data Exchange connected to virtual machine 'SolarWinds Security Event Manager', but the version does not match the version expected by Hyper-V (Virtual machine ID <ID String>). Framework version: Negotiated (3.0) - Expected (3.0); Message version: Negotiated (3.0) - Expected (5.0).

First published date

10/9/2018 5:44 PM

Last published date

10/9/2018 5:44 PM

Overview

This article applies to Security Event Manager (formerly Log & Event Manager).

The following error is found in the Hyper-V-Worker log (SEM installations to Hyper-V 2012):

Hyper-V Data Exchange connected to virtual machine 'SolarWinds Security Event Manager', but the version does not match the version expected by Hyper-V (Virtual machine ID <ID String>). 
Framework version: Negotiated (3.0) - Expected (3.0); Message version: Negotiated (3.0) - Expected (5.0). 
This is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

 

Product section

Security Event Manager

Cause

This error occurs when Hyper-V 2012 uses Network Adapter instead of the Legacy Network Adapter.

Resolution

  1. Shut down SEM.
  2. On the Hyper-V Manager, go to Settings.
  3. Highlight Network Adapter and select Remove.
  4. Select Add Hardware > Legacy Network Adapter.
  5. Click Add.
  6. Verify that the correct Virtual Switch is selected.
  7. Click OK.
  8. Restart SEM.

 

Note:  If you get an error that no IP address is assigned this is due to Hyper-V changing the MAC address for the SEM. Follow this article to resolve the issue - Error: No IP address is assigned