Sign in
 
HomeWindows Server “8” Beta20082003LibraryForums
Windows Server TechCenter > Windows Server Forums > Hyper-V > Hyper-V - Network Broken after update from beta to rc

Answered Hyper-V - Network Broken after update from beta to rc

    •  
      Sunday, April 27, 2008 4:15 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hello,

       

      Windows update, which i hate since today, has applied KB949219. So as many people here, it results in a complete disaster.

      It's now impossible to create any virtual network. Each time i attempt to create a virtual network, a new interface appears in network connections manager (see). It's also impossible to delete these connections.

       

      My server is a dell PowerEdge with two Physical Network Interfaces.

      Is there any way to clear old hyper-v network connection?

      I precise that i can't setup the entire server.

       

      Thanks by advance for any suggestion.

      Best regards,

       

    Answers

    • Thursday, May 01, 2008 6:01 AM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote

      You can remove the adapters permanently after you do "netcfg -u vms_pp" by following:

      http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3268122&SiteID=17

      Unfortunately, there is no work around in RC that will allow you to create virtual networks when those Exchange Server permissions are present in the services key.  You may be able to remove Exchange or its associated permissions in the services key and at least be able to use Hyper-V.

      This posting is provided "AS IS" with no warranties, and confers no rights
       

    All Replies

    • Sunday, April 27, 2008 10:49 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Try running:

      1) Netcfg -u vms_pp

      2) reboot

      3) netcfg -c p -i vms_pp

       

      Then try createing a new virtual network.  If that fails please include the logs from the "Applictions and Service Logs\Microsoft\Windows\Hyper-V-Network"

       

      Thanks, hope this works for you.

       

       
    • Sunday, April 27, 2008 11:01 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I'm trying but it seems to block on netcg -u vms_pp

       

      so i paste the error from the event log bellow (this error was here before you provide your solution and i have one message of this type for each attemps to create a virtual network.

       

      Thanks.

       

      Code Snippet

       

       

      Log Name:      Microsoft-Windows-Hyper-V-Network-Admin
      Source:        Microsoft-Windows-Hyper-V-Network
      Date:          4/27/2008 8:49:47 AM
      Event ID:      14070
      Task Category: None
      Level:         Error
      Keywords:     
      User:          SYSTEM
      Computer:      ALTHYR-HOST1.althyr.local
      Description:
      Switch set up failed, name='Switch-SM-897e40ee-ac09-428b-9f7a-5318a3dd01d6-0', external port='8d5095d2-2e0a-4e0b-a418-76dd7ac632e6', internal port='24b3f495-1cfc-4ff2-928c-e594aff3ff15', NIC='{2F6E8901-CF1D-4B81-8B0B-35A461AF89B6}', internal name='7922b4b8-5efb-4acc-86e3-e350f502b2c3', internal friendly name='Broadcom NetXtreme Gigabit Ethernet - Virtual Network', error=2147749889, mof code=0.
      Event Xml:
      <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
        <System>
          <Provider Name="Microsoft-Windows-Hyper-V-Network" Guid="{0a18ff18-5362-4739-9671-78023d747b70}" />
          <EventID>14070</EventID>
          <Version>0</Version>
          <Level>2</Level>
          <Task>0</Task>
          <Opcode>0</Opcode>
          <Keywords>0x8000000000000000</Keywords>
          <TimeCreated SystemTime="2008-04-27T15:49:47.244Z" />
          <EventRecordID>77</EventRecordID>
          <Correlation />
          <Execution ProcessID="2696" ThreadID="2728" />
          <Channel>Microsoft-Windows-Hyper-V-Network-Admin</Channel>
          <Computer>ALTHYR-HOST1.althyr.local</Computer>
          <Security UserID="S-1-5-18" />
        </System>
        <UserData>
          <NvspSwitchSetupError xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
            <Switch>Switch-SM-897e40ee-ac09-428b-9f7a-5318a3dd01d6-0</Switch>
            <ExternalPortName>8d5095d2-2e0a-4e0b-a418-76dd7ac632e6</ExternalPortName>
            <InternalPortName>24b3f495-1cfc-4ff2-928c-e594aff3ff15</InternalPortName>
            <NIC>{2F6E8901-CF1D-4B81-8B0B-35A461AF89B6}</NIC>
            <InternalName>7922b4b8-5efb-4acc-86e3-e350f502b2c3</InternalName>
            <InternalFriendlyName>Broadcom NetXtreme Gigabit Ethernet - Virtual Network</InternalFriendlyName>
            <Error>2147749889</Error>
            <MofCode>0</MofCode>
          </NvspSwitchSetupError>
        </UserData>
      </Event>

       

       

       
    • Sunday, April 27, 2008 11:37 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Ok i have run each of these steps but the problem stays entire Sad. It is always impossible to create a new network or delete existing interfaces

       

      here is the error log

       

      Code Snippet

      Log Name:      Microsoft-Windows-Hyper-V-Network-Admin
      Source:        Microsoft-Windows-Hyper-V-Network
      Date:          4/27/2008 4:30:57 PM
      Event ID:      14070
      Task Category: None
      Level:         Error
      Keywords:     
      User:          SYSTEM
      Computer:      ALTHYR-HOST1.althyr.local
      Description:
      Switch set up failed, name='Switch-SM-897e40ee-ac09-428b-9f7a-5318a3dd01d6-0', external port='f92c5201-6e44-4a3a-88fa-f8bd0f153674', internal port='a27b8c7a-dca0-47ee-b351-bc6e08cbd87a', NIC='{2F6E8901-CF1D-4B81-8B0B-35A461AF89B6}', internal name='75bb1166-d51d-4528-b678-18fb7078399e', internal friendly name='Broadcom NetXtreme Gigabit Ethernet - Virtual Network', error=2147749889, mof code=0.
      Event Xml:
      <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
       '>http://schemas.microsoft.com/win/2004/08/events/event">http://schemas.microsoft.com/win/2004/08/events/event">
       ; <System>
          <Provider Name="Microsoft-Windows-Hyper-V-Network" Guid="{0a18ff18-5362-4739-9671-78023d747b70}" />
          <EventID>14070</EventID>
          <Version>0</Version>
          <Level>2</Level>
          <Task>0</Task>
          <Opcode>0</Opcode>
          <Keywords>0x8000000000000000</Keywords>
          <TimeCreated SystemTime="2008-04-27T23:30:57.158Z" />
          <EventRecordID>82</EventRecordID>
          <Correlation />
          <Execution ProcessID="2688" ThreadID="2704" />
          <Channel>Microsoft-Windows-Hyper-V-Network-Admin</Channel>
          <Computer>ALTHYR-HOST1.althyr.local</Computer>
          <Security UserID="S-1-5-18" />
        </System>
        <UserData>
          <NvspSwitchSetupError xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/eventshttp://schemas.microsoft.com/win/2004/08/events">http://schemas.microsoft.com/win/2004/08/events</A< A>>" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
           '>http://www.microsoft.com/Windows/Virtualization/Events">http://www.microsoft.com/Windows/Virtualization/Events">
           ; <Switch>Switch-SM-897e40ee-ac09-428b-9f7a-5318a3dd01d6-0</Switch>
            <ExternalPortName>f92c5201-6e44-4a3a-88fa-f8bd0f153674</ExternalPortName>
            <InternalPortName>a27b8c7a-dca0-47ee-b351-bc6e08cbd87a</InternalPortName>
            <NIC>{2F6E8901-CF1D-4B81-8B0B-35A461AF89B6}</NIC>
            <InternalName>75bb1166-d51d-4528-b678-18fb7078399e</InternalName>
            <InternalFriendlyName>Broadcom NetXtreme Gigabit Ethernet - Virtual Network</InternalFriendlyName>
            <Error>2147749889</Error>
            <MofCode>0</MofCode>
          </NvspSwitchSetupError>
        </UserData>
      </Event>

       

       

       
    • Monday, April 28, 2008 10:05 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I think the first thing to do is to clean network configuration especially these network adapters (see).

      I have found many people with the same problem (see).

      In Fact even in the device Manager it is impossible to delete this network adapters.

      Has anyone an idea of the proper way to clean the network parameters or which dependency prevent us to delete these adapters?

       

      Best regards,

      Cyprien Autexier

       
    • Monday, April 28, 2008 10:37 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      What are the permissions on the following key:

       

      HKLM\SYSTEM\CurrentControlSet\Services

       

      Do you see any for "Exchange Server"?

       

      Your failure to create switches could be due to the permissions on that key.

       

      This posting is provided "AS IS" with no warranties, and confers no rights.

       

       
    • Monday, April 28, 2008 10:48 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Yes i have a lot of key concerning exchange server

      you can see the perms for HKLM\SYSTEM\CurrentControlSet\Services here (part1, part2)

       

      EDIT :

      i also have one key in Services for each network adapter with its GUID

       

      On another hand , the following command is not runing to its proper completion "Netcfg -u vms_pp", i have to use Ctrl+C to end this command. I guess it's the command that is blocking the computer at reboot when i try to unsetup hyper-v using server manager.

       
    • Tuesday, April 29, 2008 5:33 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      The "netcfg -u vms_pp" is probably hanging trying to delete the tcpip parameter settings (the key per network adapter that you mentioned).  You could confirm that in procmon (you would see it spinning querying the same key over and over).  You should be able to "fix" the permissions on the keys (give yourself access) and then try the "netcfg -u vms_pp".

       

      This posting is provided "AS IS" with no warranties, and confers no rights.

       

       
    • Tuesday, April 29, 2008 7:50 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      That's probably a part of the solution :

       

      Using procmon and changing permission manually  allows me to ensure that netcfg complete successfully (i guess that it is a probleme that will be fixed in later release of hyper-v), but at this time i'm not able to setup a new network.

      I have tried to uninstall and setup again hyper-v but the probleme is still here (in fact the old interfaces which where destroyed by ntcfg -u, where there again after the reboot...).

       

      So at this time, i'm able to clean network manager from all this connection using netcfg, regedit, procmon and some patience, but i can't setup a new network.

       

      EDIT :

       

      In fact the command "netcfg -c p -i vms_pp" restores all the old connnections.

       
    • Thursday, May 01, 2008 6:01 AM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote

      You can remove the adapters permanently after you do "netcfg -u vms_pp" by following:

      http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3268122&SiteID=17

      Unfortunately, there is no work around in RC that will allow you to create virtual networks when those Exchange Server permissions are present in the services key.  You may be able to remove Exchange or its associated permissions in the services key and at least be able to use Hyper-V.

      This posting is provided "AS IS" with no warranties, and confers no rights
       
    • Thursday, May 01, 2008 9:15 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      thanks for this tip. If I understand i have to wait for a version that fixes exchange compatibility, or unsinstall exchange?

       

      Is there a way to roll back RC and return to Beta?

       
    • Friday, May 02, 2008 8:08 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      You can’t go back to beta.  Uninstalling Exchange may clear up the problem but I haven’t personally tried that.

       

      This posting is provided "AS IS" with no warranties, and confers no rights.

         

       

       
    • Sunday, May 04, 2008 11:29 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       

      So Uninstalling exchange, the permissions in regedit for exchange no longer exist, but it does not clear up the problem Sad i get always this error :

       

      Code Snippet

      Log Name:      Microsoft-Windows-Hyper-V-Network-Admin
      Source:        Microsoft-Windows-Hyper-V-Network
      Date:          5/4/2008 4:24:27 AM
      Event ID:      14070
      Task Category: None
      Level:         Error
      Keywords:     
      User:          SYSTEM
      Computer:      ALTHYR-HOST1.althyr.local
      Description:
      Switch set up failed, name='Switch-SM-a7d11f2a-399b-476c-bec5-2b594e114a15-0', external port='SwitchPort-SM-a7d11f2a-399b-476c-bec5-2b594e114a15-0-1', internal port='SwitchPort-SM-a7d11f2a-399b-476c-bec5-2b594e114a15-0-0', NIC='{A20A3BFE-073B-45E4-A52F-940769AB7B30}', internal name='Broadcom NetXtreme Gigabit Ethernet - Virtual Network', internal friendly name='Broadcom NetXtreme Gigabit Ethernet - Virtual Network', error=2147749889, mof code=0.
      Event Xml:
      <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
        <System>
          <Provider Name="Microsoft-Windows-Hyper-V-Network" Guid="{0a18ff18-5362-4739-9671-78023d747b70}" />
          <EventID>14070</EventID>
          <Version>0</Version>
          <Level>2</Level>
          <Task>0</Task>
          <Opcode>0</Opcode>
          <Keywords>0x8000000000000000</Keywords>
          <TimeCreated SystemTime="2008-05-04T11:24:27.451Z" />
          <EventRecordID>145</EventRecordID>
          <Correlation />
          <Execution ProcessID="2472" ThreadID="2508" />
          <Channel>Microsoft-Windows-Hyper-V-Network-Admin</Channel>
          <Computer>ALTHYR-HOST1.althyr.local</Computer>
          <Security UserID="S-1-5-18" />
        </System>
        <UserData>
          <NvspSwitchSetupError xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
            <Switch>Switch-SM-a7d11f2a-399b-476c-bec5-2b594e114a15-0</Switch>
            <ExternalPortName>SwitchPort-SM-a7d11f2a-399b-476c-bec5-2b594e114a15-0-1</ExternalPortName>
            <InternalPortName>SwitchPort-SM-a7d11f2a-399b-476c-bec5-2b594e114a15-0-0</InternalPortName>
            <NIC>{A20A3BFE-073B-45E4-A52F-940769AB7B30}</NIC>
            <InternalName>Broadcom NetXtreme Gigabit Ethernet - Virtual Network</InternalName>
            <InternalFriendlyName>Broadcom NetXtreme Gigabit Ethernet - Virtual Network</InternalFriendlyName>
            <Error>2147749889</Error>
            <MofCode>0</MofCode>
          </NvspSwitchSetupError>
        </UserData>
      </Event>

       

       

       
    • Monday, May 05, 2008 5:56 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      1. Are you able to create "internal" switches?

       

      2. Are you still getting the "orphaned" adapters everytime you try to create a switch?

       

      3. What permissions are remaining on the services key?

       

      This posting is provided "AS IS" with no warranties, and confers no rights

       

       
    • Tuesday, May 06, 2008 9:06 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      1 yes Internal works fine

      2 yes each time i try i get a new virtual switch

      3 In fact it appears that there is style Exchange perms shown as "Account Unknown"

       
    • Saturday, May 10, 2008 2:09 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Based on that log message, I'm a little suprised "internal" is working whereas "external" is not -- are you enabling VLANs when you create the switch?

      If you are seeing keys similar to:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\{guid}\parameters\tcpip

      With non-writeable permissions being created for each switch you try to create then there is still an ACL remaining on the services keys that is causing your problems.  You may want to trim the “unknown” ACL.

      This posting is provided "AS IS" with no warranties, and confers no rights.

       

       
    • Friday, May 16, 2008 10:21 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      sorry, i made a mistake internal network does not work, it says creating the internal ethernet port failed.

      i have trimmed ACL

       
    • Friday, May 16, 2008 7:52 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      I had this problem early on with Hyper-v RC0 myself.  Have you updated your NIC driver?  I solved my problem by rolling back to the original Microsoft NIC driver that was installed when I loaded th OS.  On one of my servers, I had to reinstall the OS to get back to that point but, it did solve my problem.  Do you have Broadcom NetXtreme II NICs in you server?  I do and I have found that the drivers from Broadcom are not liked at all by Hyper-v.