none
an error occurred while trying to retrieve a list of virtual switches

    Question

  • Hello all

    Trying to install Hyper V machines to win server 2012

    ANd i activated the Hyper V role and assigned the network card of the server to be used a virtual card for the virtual machines.

    BUt when i add the machines i get the not connected option for the machines.

    And when accessing the switch manager i get the error 

    an error occurred while trying to retrieve a list of virtual switches.

    http://prntscr.com/lr0ndm

    Please help, stuck on this for a week now. Tried almost all the tricks found on the net.

    Wednesday, December 5, 2018 12:36 PM

All replies

  • "Tried almost all the tricks found on the net."

    This is not very definitive, so we have to ask.  Did you try removing and re-installing the Hyper-V option on the host?  Is your system a supported system?  See www.windowsservercatalog.com and search for your system for support of Windows Server 2012.

    "i activated the Hyper V role and assigned the network card of the server to be used a virtual card for the virtual machines."

    I understand that you are new to Hyper-V and may not know all the proper terminology.  One does not assign a physical network card of the host "to be used a virtual card for the virtual machines".  One creates a virtual switch on a physical NIC, and virtual NICs assigned to that virtual switch can then be created for the virtual machines.  Could you give a synopsis of the steps you followed to create the virtual switch and assign the NIC to the VM? 


    tim

    Wednesday, December 5, 2018 2:31 PM
  • Add roles and features > Hyper V> extra features> assign network> finish >restart

    Yes tried removing and reinstalling an all

    Same steps followed in a win 2016 server and all works fine without any issues.

    Nothing different from my part and it works in 2016 http://prntscr.com/lr2uup

    For some reason the DC wont allow me to install anything other than 2012 on the server which is facing the issue.


    Wednesday, December 5, 2018 2:49 PM
  • "For some reason the DC wont allow me to install anything other than 2012 on the server which is facing the issue."

    Question remains - is this system a supported system for Windows Server 2012?


    tim

    Wednesday, December 5, 2018 3:17 PM
  • "For some reason the DC wont allow me to install anything other than 2012 on the server which is facing the issue."

    Question remains - is this system a supported system for Windows Server 2012?


    tim

    Not sure how can i know if i ts supported or not. I am not understanding what to do in the https://www.windowsservercatalog.com/.

    The server is use is a Intel Xeon E3-1245v2 4c / 8t 3.4GHz   32GB DDR3 1333 MHz SoftRaid  2x480GB   SSD

    Thursday, December 6, 2018 9:21 AM
  • "Not sure how can i know if i ts supported or not."

    www.windowsservercatalog.com is a repository of systems and components that have been validated by the hardware vendors to run specific versions of the Windows Server operating system.  If a system or a component does not exist for the version of the operating system you are running, you are running an unsupported piece of hardware.  That does not mean it will not work, but it does mean that the hardware vendor has not validated it for that version of the operating system.  This could be a marketing decision by the vendor, i.e. they no longer want to support an older component/system on a newer release, or they have determined there are problems with that component/system and they do not want to invest in building a fix that would overcome the issue.

    The only component you have listed is the Intel processor.  The E3 is an older processor, and it looks like you have an early version (v2) of that processor.  current version of that processor is v6 (https://www.intel.com/content/www/us/en/products/processors/xeon/e3-processors/e3-1245-v6.html).  But since you are trying to install an older version of the OS, you might be OK.

    Since you are listing components, is this a system you built yourself?  If it is a vendor's system, you simply need to search for the vendor's system on Windows Server catalog web site.  If the vendor supports Windows Server on their system, it will list which versions of the OS are supported.

    If it is not found, then the vendor does not support it.  If it is a system which you built, then you need to ensure all the individual components in the system are supported by the individual hardware vendors.  Building systems leaves the responsibility for integration testing up to the system builder.

    Self-built systems that are built from verified components should work fine.  But there may be issues with integration.  The biggest issue with self-built systems is the requirement for self-support.  When an error occurs, about the only recourse is to contact the vendor of the failing component to see if they have any suggestions.

    What you should do is make sure that all firmware and drivers for all components is at the level recommended by the vendor for the operating system version you are running.


    tim

    Thursday, December 6, 2018 1:49 PM
  • "Not sure how can i know if i ts supported or not."

    www.windowsservercatalog.com is a repository of systems and components that have been validated by the hardware vendors to run specific versions of the Windows Server operating system.  If a system or a component does not exist for the version of the operating system you are running, you are running an unsupported piece of hardware.  That does not mean it will not work, but it does mean that the hardware vendor has not validated it for that version of the operating system.  This could be a marketing decision by the vendor, i.e. they no longer want to support an older component/system on a newer release, or they have determined there are problems with that component/system and they do not want to invest in building a fix that would overcome the issue.

    The only component you have listed is the Intel processor.  The E3 is an older processor, and it looks like you have an early version (v2) of that processor.  current version of that processor is v6 (https://www.intel.com/content/www/us/en/products/processors/xeon/e3-processors/e3-1245-v6.html).  But since you are trying to install an older version of the OS, you might be OK.

    Since you are listing components, is this a system you built yourself?  If it is a vendor's system, you simply need to search for the vendor's system on Windows Server catalog web site.  If the vendor supports Windows Server on their system, it will list which versions of the OS are supported.

    If it is not found, then the vendor does not support it.  If it is a system which you built, then you need to ensure all the individual components in the system are supported by the individual hardware vendors.  Building systems leaves the responsibility for integration testing up to the system builder.

    Self-built systems that are built from verified components should work fine.  But there may be issues with integration.  The biggest issue with self-built systems is the requirement for self-support.  When an error occurs, about the only recourse is to contact the vendor of the failing component to see if they have any suggestions.

    What you should do is make sure that all firmware and drivers for all components is at the level recommended by the vendor for the operating system version you are running.


    tim

    Its a so you start server.

    I have two of them same config as above. One runs on win 2016 (has no issues with the virtual switch)

    Second one is on win 2012 which faces this issue.

    I have installed 2012 on same spec servers in the past, but now :(
    Have asked the SYS support, but they take 5-6 days to make one reply.

    Thursday, December 6, 2018 2:01 PM
  • "Its a so you start server."

    I have no idea what this is.


    tim

    Thursday, December 6, 2018 2:18 PM
  • https://www.soyoustart.com/ie/
    Thursday, December 6, 2018 2:19 PM
  • Okay, I had never heard of that organization before.  But it does mean that you have to contact them with your problem.  They need to be able to tell you that the hardware they are providing you supports Hyper-V on Windows Server 2012.

    tim

    Thursday, December 6, 2018 2:26 PM
  • Hi,

    Just want to confirm the current situations.

    Please feel free to let me know if you need further assistance.

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    16 hours 13 minutes ago
    Moderator