Reason 442: Failed to enable Virtual Adapter

I've installed version 4.8.02.0010 of the VPN client onto a Dell Latitude D820 laptop. When I attempt to connect, I get this message. There are no firewalls running (I disabled the Windows XP firewall) and I'm running under Service Pack 2 with all of the latest security patches from Microsoft.
I even tried un-installing the client and using an older version (4.8.00.0440) and it reports a similar error in the Log file.
I'd prefer to NOT have to wipe the laptop and reinstall the O/S if I don't have to. This is the only laptop that I've experienced this problem with but it's also the first Dell Latitude D820 that I've attempted to install the client on.
Is there a problem with the Dell Latitudes and the VPN Client? Is there another way around this other than a wipe and re-install?
I've already tried replacing the profiles and still get the same problem.

Hi,
There is another thing that you can try temporarily.
Goto device manager on the computer and manually enable the virtual adapter and see if it works.
There might be some other adapters / softwares installed that you might have uninstall. Those could be some wireless adapters, personal firewall or internet security package, any other kind of adapter that you installed after installing the VPN cliemt.
HTH,
Kamal

Similar Messages

  • Reason 442: Failed to Enable Virtual Adapter - Windows 7 64 bit

    Some details about the issue.
    I'm trying to connect to my client's network using VPN Client version 5.0.07.0290. The user authetication is done by providing RSA SecureID token value. After entering proper credentials, the client window gets struck at 'Securing Communication Channels...' message in status bar and reports 'Reason 442: Failed to Enable Virtual Adapter' error after few mintues. I have confirmed that this version works for other people in my team , so I'm guessing it has something to do with my system settings than the client itself.
    Below are the trobleshooting tips that I have already tried.
    1. Uninstall and Reinstall the client.
    2. Enable WinXP SP2 compatability for ipsecdialer.exe and vpngui.exe.
    3. Clicking 'Diagnose' on the Citrix Virtaul Adapter connection in Networks and Sharing centre, reports no issues.
    4. Enabling Network sharing for Local Area Network and disaling Wireless Networks
    I'm running Windows 7 64 bit Enterpise OS.
    Appreciate any suggestions to resolve this issue.
    Thanks,
    PVNSKC
    Update: 9/7/2011
    OK, things look much better after a good vacation, always!!!
    I tried to connect today by reinstalling the client after a weekend shutdown (I don't believe the cold reboot stuff, but hey, worth a try! ) and it did work. The only change I did today was to disable the Wireless Connection adapter in Networks Connections. I'm not sure whether that fixed or not cause I had tried that already. Anyway, below is my current configuration which is working for now!
    1. Below executables are running in the XP compatability mode.
    cvpnd.exe, VAInst64.exe, vpngui.exe
    2. Local Area Connection is allowed for 'Sharing'
    3.  Registry is updated with below entry.
    HKLM\System\CurrentControlSet\Services\Tcpip\Parameters /v ArpRetryCount /t REG_DWORD /d 0 /f
    4. Wireless Connection is disabled.
    Thank you all for the responses.
    PVNSKC

    Hi,
    Duplicate IP Address Triggers Error 442 on Windows 7 and Vista
    The following error "Reason 442: failed to enable virtual adapter"  appears after Windows 7 and Vista reports a duplicate IP address  detected. Subsequent connections fail with same message, but the OS does  not report a duplicate IP address detected.
    To work around error 442, do the following steps:
    Step 1 Open "Network and Sharing Center".
    Step 2 Select "Manage Network Connections".
    Step 3 Enable the Virtual Adapter ("VA"—Cisco VPN Adapter).
    Step 4 Right-click on Cisco VPN Adapter and select "Diagnose" from the context menu.
    Step 5 Select "Reset the network adapter Local Area Connection X".
    If this procedure does not work, run the following command from cmd:
    reg add HKLM\System\CurrentControlSet\Services\Tcpip\Parameters /v ArpRetryCount /t REG_DWORD /d 0 /f
    Then reboot.
    This resolves the issue until the OS reports a duplicate IP address again. Follow the preceding steps to resolve it again.
    If that doesn't work, you might have UAC enabled. If so, you must run  cmd as administrator and repeat the previous registry workaround.
    NOTE: You mentioned step 4 already, try the whole sequence again, if the steps does not work then try the registry key.
    Hope this helps,
    Sian

  • 64bit vpn client issue /error :reason -442:failed to enable virtual adapter.

    Hi All of you ,
    I m using vpn client for windows64bit  -  file name - vpnclient-winx64-msi-5.0.07.0290-k9.exe and installing it on windows 2003 server .
    But while connecting via vpn client to f/w , Virtual Adapter is taking the ip address but not connecting .getting error message on screen -
    reason -442:failed to enable virtual adapter.
    Is it possible some configuration or image issue from ASA as its first time we are trying to use 64bit OS , vpn client for 32bit OS working fine .
    Below are the logs from vpn clinet when i tried to connect to ASA5520 . Version 7.0(8) -
    Cisco Systems VPN Client Version 5.0.07.0290
    Copyright (C) 1998-2010 Cisco Systems, Inc. All Rights Reserved.
    Client Type(s): Windows, WinNT
    Running on: 5.2.3790 Service Pack 2
    Config file directory: C:\Program Files (x86)\Cisco Systems\VPN Client\
    1      15:38:03.921  01/27/11  Sev=Info/4 CM/0x63100002
    Begin connection process
    2      15:38:03.937  01/27/11  Sev=Info/4 CM/0x63100004
    Establish secure connection
    3      15:38:03.937  01/27/11  Sev=Info/4 CM/0x63100024
    Attempt connection with server "203.199.30.190"
    4      15:38:04.125  01/27/11  Sev=Info/4 CM/0x6310000E
    Established Phase 1 SA.  1 Crypto Active IKE SA, 0 User Authenticated IKE SA in the system
    5      15:38:04.140  01/27/11  Sev=Info/4 CM/0x63100015
    Launch xAuth application
    6      15:38:09.515  01/27/11  Sev=Info/4 CM/0x63100017
    xAuth application returned
    7      15:38:09.515  01/27/11  Sev=Info/4 CM/0x6310000E
    Established Phase 1 SA.  1 Crypto Active IKE SA, 1 User Authenticated IKE SA in the system
    8      15:38:10.562  01/27/11  Sev=Info/4 CM/0x63100019
    Mode Config data received
    9      15:38:10.781  01/27/11  Sev=Warning/2 CVPND/0xE340002C
    Unable to enable the 64-bit VA after timeout
    10     15:38:10.781  01/27/11  Sev=Warning/3 CVPND/0xE3400029
    The Client failed to enable the Virtual Adapter on 64-bit Windows
    11     15:38:10.781  01/27/11  Sev=Warning/2 CM/0xE310000A
    The virtual adapter failed to enable
    12     15:38:10.781  01/27/11  Sev=Info/6 CM/0x6310003A
    Unable to restore route changes from file.
    13     15:38:10.781  01/27/11  Sev=Info/6 CM/0x63100037
    The routing table was returned to original state prior to Virtual Adapter
    14     15:38:10.859  01/27/11  Sev=Info/4 CM/0x63100035
    The Virtual Adapter was disabled
    15     15:38:10.859  01/27/11  Sev=Warning/2 IKE/0xE300009B
    Failed to active IPSec SA: Unable to enable Virtual Adapter (NavigatorQM:936)
    16     15:38:10.859  01/27/11  Sev=Warning/2 IKE/0xE30000A7
    Unexpected SW error occurred while processing Quick Mode negotiator:(Navigator:2263)
    17     15:38:11.546  01/27/11  Sev=Info/4 CM/0x63100012
    Phase 1 SA deleted before first Phase 2 SA is up cause by "Unknown".  0 Crypto Active IKE SA, 0 User Authenticated IKE SA in the system
    18     15:38:11.546  01/27/11  Sev=Info/5 CM/0x63100025
    Initializing CVPNDrv
    19     15:38:11.578  01/27/11  Sev=Info/6 CM/0x63100046
    Set tunnel established flag in registry to 0.
    20     15:38:40.953  01/27/11  Sev=Info/4 CM/0x63100002
    Begin connection process
    21     15:38:40.953  01/27/11  Sev=Warning/2 CVPND/0xA3400019
    Error binding socket: -21. (DRVIFACE:1234)
    22     15:38:40.968  01/27/11  Sev=Info/4 CM/0x63100004
    Establish secure connection
    23     15:38:40.968  01/27/11  Sev=Info/4 CM/0x63100024
    Attempt connection with server "203.199.30.190"
    24     15:38:41.156  01/27/11  Sev=Info/4 CM/0x6310000E
    Established Phase 1 SA.  1 Crypto Active IKE SA, 0 User Authenticated IKE SA in the system
    25     15:38:41.171  01/27/11  Sev=Info/4 CM/0x63100015
    Launch xAuth application
    26     15:39:08.031  01/27/11  Sev=Info/4 CM/0x63100017
    xAuth application returned
    27     15:39:08.046  01/27/11  Sev=Info/4 CM/0x6310000E
    Established Phase 1 SA.  1 Crypto Active IKE SA, 1 User Authenticated IKE SA in the system
    28     15:39:09.093  01/27/11  Sev=Info/4 CM/0x63100019
    Mode Config data received
    29     15:39:09.312  01/27/11  Sev=Warning/2 CVPND/0xE340002C
    Unable to disable the 64-bit VA after timeout
    30     15:39:09.312  01/27/11  Sev=Warning/3 CVPND/0xE340002A
    The Client failed to disable the Virtual Adapter on 64-bit Windows
    31     15:39:19.937  01/27/11  Sev=Warning/3 CVPND/0xA340000D
    The virtual adapter was not recognized by the operating system.
    32     15:39:19.937  01/27/11  Sev=Warning/2 CM/0xE310000A
    The virtual adapter failed to enable
    33     15:39:19.937  01/27/11  Sev=Info/6 CM/0x6310003A
    Unable to restore route changes from file.
    34     15:39:19.937  01/27/11  Sev=Info/6 CM/0x63100037
    The routing table was returned to original state prior to Virtual Adapter
    35     15:39:20.109  01/27/11  Sev=Warning/2 CVPND/0xE340002C
    Unable to disable the 64-bit VA after timeout
    36     15:39:20.109  01/27/11  Sev=Warning/3 CVPND/0xE340002A
    The Client failed to disable the Virtual Adapter on 64-bit Windows
    37     15:39:20.281  01/27/11  Sev=Warning/2 CVPND/0xE340002C
    Unable to disable the 64-bit VA after timeout
    38     15:39:20.281  01/27/11  Sev=Warning/3 CVPND/0xE340002A
    The Client failed to disable the Virtual Adapter on 64-bit Windows
    39     15:39:20.578  01/27/11  Sev=Warning/2 CVPND/0xE340002C
    Unable to disable the 64-bit VA after timeout
    40     15:39:20.578  01/27/11  Sev=Warning/3 CVPND/0xE340002A
    The Client failed to disable the Virtual Adapter on 64-bit Windows
    41     15:39:20.953  01/27/11  Sev=Warning/2 CVPND/0xE340002C
    Unable to disable the 64-bit VA after timeout
    42     15:39:20.953  01/27/11  Sev=Warning/3 CVPND/0xE340002A
    The Client failed to disable the Virtual Adapter on 64-bit Windows
    43     15:39:21.437  01/27/11  Sev=Info/4 CM/0x63100035
    The Virtual Adapter was disabled
    44     15:39:21.437  01/27/11  Sev=Warning/2 IKE/0xE300009B
    Failed to active IPSec SA: Unable to enable Virtual Adapter (NavigatorQM:936)
    45     15:39:21.437  01/27/11  Sev=Warning/2 IKE/0xE30000A7
    Unexpected SW error occurred while processing Quick Mode negotiator:(Navigator:2263)
    46     15:39:22.046  01/27/11  Sev=Info/4 CM/0x63100012
    Phase 1 SA deleted before first Phase 2 SA is up cause by "Unknown".  0 Crypto Active IKE SA, 0 User Authenticated IKE SA in the system
    47     15:39:22.046  01/27/11  Sev=Info/5 CM/0x63100025
    Initializing CVPNDrv
    48     15:39:22.062  01/27/11  Sev=Info/6 CM/0x63100046
    Set tunnel established flag in registry to 0.
    release notes for vpn client 64bit  -
    http://www.cisco.com/en/US/docs/security/vpn_client/cisco_vpn_client/vpn_client5007/release/notes/vpnclient5007.html#wp63537

    Hi Anisha ,
    Exact version of OS is "Microsoft Windows Server 2003 x64"  .
    I need supported cisco vpn client for this OS .
    =========
    Thanx 4 reply .
    Raj

  • Failed to enable Virtual Adapter in Windows 8

    Hello
    I got a problem when using Cisco VPN client 5.0.04.0300 in Windows 8...today
    Error as following:
    Reason 442: Failed to enable Virtual Adapter.
    Logs here:
    1      20:48:21.787  03/01/12  Sev=Warning/3         CVPND/0xE340000C
    The Client was unable to enable the Virtual Adapter because it could not open the device.
    2      20:48:21.807  03/01/12  Sev=Warning/3         CVPND/0xE340000C
    The Client was unable to enable the Virtual Adapter because it could not open the device.
    3      20:48:21.807  03/01/12  Sev=Warning/2         IKE/0xE300009B
    Failed to active IPSec SA: Unable to enable Virtual Adapter (NavigatorQM:936)
    4      20:48:21.807  03/01/12  Sev=Warning/2         IKE/0xE30000A7
    Unexpected SW error occurred while processing Quick Mode negotiator:(Navigator:2263)
    I'm using a laptop which belongs to the company...this is really urgent.
    Can anybody help me!!?
    Really appreciate any feedback!!!
    Snail

    thank you so much for your reply.
    I'm considering to restore to Windows 7 cuz I use those apps very offen..
    thanks again...

  • 442 Error - Failed to enable Virtual Adapter

    Windows 8, I am  trying to connect on VPN and I only receive this error : 442 - Failed to enable Virtual Adapter.

    Install Citrix Deterministic Network Enhancer to solve Cisco IPSec VPN issue with Windows 8/8.1. Check below guide,
    http://www.vmwareandme.com/2013/12/solved-windows-8-and-windows-81-cisco.html
    www.mytricks.in

  • Vista, Cisco VPN Client 5.0.01.0600 "Failed to enable Virtual Adapter"

    Four times out of five when trying to connect with the VPN client on Vista Business I get a message that the Virtual adapter cannot be enabled.
    When checking the logs there are two entries that always is seen together with this failure:
    123 09:21:36.026 12/27/07 Sev=Warning/2 CVPND/0xA3400015
    Error with call to IpHlpApi.DLL: unable CreateUnicastIpAddressEntry, error 0
    129 09:21:55.709 12/27/07 Sev=Warning/3 CVPND/0xA340001A
    Failed to find VA MAC Address
    Anyone else who have seen this issue on Vista?

    Hi Magnus
    Uninstall VPN client. Restart the PC
    Donwload and run the following software, then restart the PC
    http://www.softpedia.com/get/Tweak/Network-Tweak/WinSockFix.shtml
    Reinstall VPN client
    Regards

  • VPN Virtual Adapter and Vista

    I am running Vista for Business on my notebook and have installed VPN Client version 5.0.02.0090
    Each time I try to connect to my network the VPN client times out and I get the message
    Secure VPN Connection terminated locally by the Client
    Reason 442: Failed to enable Virtual Adapter
    When I go to Device Manager and enable the VPN network adapter, it becomes disabled once I try to connect again.
    I tried the softpedia.com/Tweak fix and it worked the first time I tried to connect, but once I disconnected the error came back again at subsequent tries.
    This is pretty frustrating. Plse help. Thanx.
    Tony

    OK, I have come a little bit further with this problem. Some recent automatic updates by Windows Vista caused the client to stop working when it was working before.
    I uninstalled all the updates (most were critical security patches which now leaves me vulnerable) and uninstalled the Cisco VPN client including scouring the Registry for anything remotely associated with the VPN such as any reference to 'CVPN' or 'Cisco'.
    I then installed the latest VPN client (V 5.0.03.0560), and I DIDN'T reboot as it asked me too. The reason I thought this was a good idea is because after a reboot, the Network Connections are reset and re-assigned IPs which was, I started to think, part of the problem.
    It Worked! I was able to start the client (that was already an achievement!) and, lo and behold, was able to connect without problems... I thought!
    Now I have the following... when I connected to the VPN, I have limited access to the internet. Some sites are fine, others only load half-way and still others I can absolutely not connect to. The ones I can connect to load very very slow.
    For now I have left it this way since I can (albeit handicapped) connect to the VPN so I have to keep connecting/disconnecting etc. It is still very frustrating.
    However, I believe I know what the problem is, but I don't know how to solve it. If anyone here can use this information to take this one step further, we may get somewhere.
    I believe it has to do with the TCP/IP settings where we now have both v4 and v6 running. I think the VPN is using one of these only, and when it is using it, it is not allowing any other traffic through it. I don't know how to solve this. I tried disabling one or the other in either Network Connection, but it either gives me no connection or limited connection.
    The reason I think this is it is because some sites are loading/half loading when the VPN is connected... in other words, one of the TCP/IP protocals is open to the Internt traffic, the other is used by the VPN exclusively.
    I tried looking for sharing and tunneling options in my VPN client and the Network Connections settings, but I can't find anything.
    I am very hesitant to change any more settings since I do have a half-baked solution that at least allows me to meet the deadlines I have for my client.
    Let's get this solved!

  • "enable" the Virtual Adapter

    Under Vista with VPN Client 5.0.01.0600 I always have to go into Manage Network connections and "enable" the Virtual Adapter. Why can't the virtual adapter just stay enabled?
    UAC and Windows firewall are disabled, I'm logged in as full administrator.

    There is not a newer version of VPN Client than this, seems to coorelate to when I close my lid and laptop goes into sleep and then awakes later. Sometimes I have to reboot for the Virtual Adapter to stay enabled. I'll enable it and hit F5 and it will be back at Disabled. Most of the time it stays Enabled. No Firewalls and I don't think AV would Disable a Virtual Adapter, my wireless or ethernet never Disable. Annoying caveat!
    Jason Aarons
    MCSE/CCVP/CCNP/CCDP

  • Hyper-V failed to enable replication for virtual machine 'Machinename': Incorrect funciton. (0x8007001)

    When enabling replication on several VM's, I receive Hyper-V failed to enable replication for virtual machine "virtualmachinename": Incorrect funciton. (0x8007001). However this error doesn't happen to all VM's and it isn't related to any
    particular host.
    I've traced this down to a VSS error, however when running ">vssadmin list providers", I receive the following indicating there are no errors:
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2012 Microsoft Corp.
    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error
    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error
    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error
    Writer name: 'Cluster Shared Volume VSS Writer'
       Writer Id: {1072ae1c-e5a7-4ea1-9e4a-6f7964656570}
       Writer Instance Id: {fab685fb-d333-4744-b46a-c63fc6360737}
       State: [1] Stable
       Last error: No error
    Writer name: 'Microsoft Hyper-V VSS Writer'
       Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
       Writer Instance Id: {5583acc3-a218-4ce6-bce9-93ff551ad8aa}
       State: [1] Stable
       Last error: No error
    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {dd5f1635-d7ce-434b-84f7-9aaf216d5339}
       State: [1] Stable
       Last error: No error
    Writer name: 'Cluster Database'
       Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
       Writer Instance Id: {0a0f16ab-b57a-4403-9059-1ea7aa3abc90}
       State: [1] Stable
       Last error: No error
    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {ce09aaff-1515-4240-b5a5-8c2710a4163a}
       State: [1] Stable
       Last error: No error
    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {faee5f76-086d-454c-afdb-4f8391c0ed7d}
       State: [1] Stable
       Last error: No error
    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {2b649ed6-9451-40d8-b45d-e11f171aca87}
       State: [1] Stable
       Last error: No error
    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {3cd0e01a-62a9-4ba4-b6dc-277a66719ae0}
       State: [1] Stable
       Last error: No error
    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {f10f17aa-c8e7-42ee-84df-ed2bbf3ac187}
       State: [1] Stable
       Last error: No error
    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {45e94e87-c253-45d5-942a-462f3fece288}
       State: [1] Stable
       Last error: No error
    The providers I'm using are:
    Provider name: 'Microsoft CSV Shadow Copy Helper Provider'
       Provider type: Software
       Provider Id: {26d02d81-6aac-4275-8504-b9c6edc5261d}
       Version: 1.0.0.1
    Provider name: 'Microsoft CSV Shadow Copy Provider'
       Provider type: Software
       Provider Id: {400a2ff4-5eb1-44b0-8a05-1fcac0bcf9ff}
       Version: 1.0.0.1
    Provider name: 'Microsoft File Share Shadow Copy provider'
       Provider type: Fileshare
       Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
       Version: 1.0.0.1
    Provider name: 'Microsoft Software Shadow Copy provider 1.0'
       Provider type: System
       Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
       Version: 1.0.0.7
    Provider name: 'Dell EqualLogic VSS HW Provider'
       Provider type: Hardware
       Provider Id: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
       Version: 4.6.0
    Has anyone run into this before?
    -Jeremy Houp

    Hi Jeremy,
    Hyper-v replica broker is needed if you want to enable replica for hyper-v cluster .
    Please refer to following link:
    http://technet.microsoft.com/en-us/library/jj134153.aspx
    Also:
    http://blogs.technet.com/b/yungchou/archive/2013/01/10/hyper-v-replica-explained.aspx
    Best Regards
    Elton JI
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • AGPDMA fails to enable for unknown reasons

    This seems to happen on a semi-random basis... Either it doesn't happen to begin with and never happens again, or it happens when I first use Xorg and sticks around for a while, possibly disappearing, possibly not. As of yet, I haven't found any cause or any solution. I just get this message in Xorg.0.log:
    (EE) VIA(0): [drm] drmAgpAcquire failed 1023
    (EE) VIA(0): [drm] Failed to initialize DMA ring-buffer: 1005
    and AGPDMA fails to enable, reducing OpenGL performance very significantly. This happens with both the Via and Unichrome drivers. Has anyone else experienced this, and is there any way around it?

    That little yellow triangle icon means that the DVR detected a conflict in your scheduled recordings or a recording was "bumped due to deletion". 
    In the first case either there was an overlap with the other 2 recordings or something was causing the DVR to think that it should try to record 3 things (or more) at once - maximum of 2 simultaneous recordings allowed.
    In the second case, it is possible the guide data changed and the program is no longer listed - remember that the DVR is a program based system, not time slot, and Verizon's guide tends to be wrong a lot.
    One way to assure your recordings is to set them up as recurring manual recordings as opposed to a specific show.
    Hope that helps.
    If a forum member gives an answer you like, give them the Kudos they deserve. If a member gives you the answer to your question, mark the answer as Accepted Solution so others can see the solution to the problem.

  • Solved: I cannot manage (bring online, initialize, partition, format, or write to) a VHDX hard drive once it has "Enable Virtual Hard Disk Sharing" enabled.

    Hello,
    Issue:
    On a Virtual Machine with a secondary VHDX attached, I cannot manage (bring online, initialize, partition, format, or write to) the VHDX hard drive once it has "Enable Virtual Hard Disk Sharing (VHD Sharing)" enabled.
    Questions:
    Should I be able to manage (bring online, initialize, partition, format, and write to) a VHDX hard drive once it has VHD Sharing enabled? If I should be able to manage it, what am I missing?
    Topography:
    One SuperMicro Cluster In a Box (CIB) with 2012 R2 Data Center on each node. Microsoft Failover Cluster installed and working on each node. The Failover Cluster Servers on each host passes all cluster validation tests. Two Hyper-V 2012 R2 Data Center Virtual
    Machine (VM) servers, one on each node. 1 common Cluster Shared Volume (CSV) and 1 Generation 2 Scale-Out File Server (SOFS) shared volume both Resilient File System (REFS) formatted. One 5 Gigabit (Gb) Virtual Hard Drive Type X (VHDX) file on the CSV and/or
    SOFS. Integrity bit and read only turned off on VHDX file.
    Each of the two Hyper-V VMs have one 127Gb VHDX Generation 2 primary hard drive and 1 VHDX secondary hard drive attached, both on SCSI Controller #1.
    Background:
    If I start VM1 without the VHD Sharing enabled on the secondary hard drive, I can bring the drive online, initialize, partition, format, and write to the drive.
    If I enable VHD Sharing, I can no longer modify the drive in Disk Management in any way. With or without VM2 running.
    Both VMs and the CSV and SOFS are on the same host cluster server, or not, no difference…
    The VHDX is referenced either by the CSV name C:\ClusterStorage\Volume1\TEST1.VHDX
     or a Shared Folder name
    \\sharedfolder\folder\Test1.VHDX .
    If I start VM1 with VHD Sharing disabled and I format the drive, then shut down and enable VHD Sharing, the drive is offline and requests initialization which fails with an "I/O device error", every other attempt to manage the drive fails with
    the same "I/O device error", error.
    Events:
    VDS fails to write boot code on a disk during clean operation. Error code: 8007045D@02070008
    Log Name:      System
    Source:        Virtual Disk Service
    Date:          3/3/2015 11:39:18 AM
    Event ID:      10
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Server1.Domain.local
    Description:
    VDS fails to write boot code on a disk during clean operation. Error code: 8007045D@02070008
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Virtual Disk Service" />
        <EventID Qualifiers="49664">10</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-03-03T19:39:18.000000000Z" />
        <EventRecordID>27318</EventRecordID>
        <Channel>System</Channel>
        <Computer> Server1.Domain.local </Computer>
        <Security />
      </System>
      <EventData>
        <Data>8007045D@02070008</Data>
      </EventData>
    </Event>
    AND
    Log Name:      System
    Source:        disk
    Date:          3/3/2015 12:16:42 PM
    Event ID:      153
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      Server1.Domain.local
    Description:
    The IO operation at logical block address 0x0 for Disk 1 (PDO name: \Device\MPIODisk1) was retried.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="disk" />
        <EventID Qualifiers="32772">153</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-03-03T20:16:42.017090000Z" />
        <EventRecordID>27333</EventRecordID>
        <Channel>System</Channel>
        <Computer>Server1.Domain.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>\Device\Harddisk1\DR1</Data>
        <Data>0x0</Data>
        <Data>1</Data>
        <Data>\Device\MPIODisk1</Data>
        <Binary>0F01040004002C00000000009900048000000000000000000000000000000000000000000000000000020488</Binary>
      </EventData>
    </Event>
    Thanks again for any help,
    Robert

    Hi All,
    I had to buy a Willy Wonka bar and spend a golden ticket to get an answer to this one.
    We found that the default LogicalSectorSizeBytes of a VHDX is 512b. It needs to be 4kb.
    The Host drive doesn't seem to matter CSV or SOFS. Below is a way to create a VHDX with the correct LogicalSectorSizeBytes.
    In Power Shell, type --> New-VHD -Path C:\ClusterStorage\Volume4\Cluster2DataDisks\Cluster2Disk1.vhdx -SizeBytes 200Gb -PhysicalSectorSizeBytes 4kb -LogicalSectorSizeBytes 4kb
    Attach the resulting file to your guest cluster servers and set the Enable Virtual Hard Disk Sharing option on both server. You should now be able to bring the drives on-line and initialize them. They will also add to the guest cluster pool.
    Change the size, path and file name above to fit your Cluster Servers configuration.
    Thank You 
    Sachin Kumar Support Engineer | Windows Server Setup Team | Microsoft Enterprise Platform for finding the answer to this one.
    Hope this helps others.
    Robert

  • Failed while creating virtual Ethernet switch. Failed to connect Ethernet switch port

    Hello Folks
    I am completely stuck with the configuration of my virtual networks. I have one logical switch left to add to one of my Hyper-V 2012 R2 hosts when I started getting the error below when I try to add logical switches to either Hyper-V Host. I have been using
    the document. 'Hybrid Cloud with NVGRE (Cloud OS)' to implement the virtual networking. Basically using the exact configuration that is in the document. I have added the PA Logical Network and the Network adapters and added the logical switch for it to my
    hyper-v 2012 R2 host and everything was fine. I am now trying to add my ISCSI Logical Switch to the host and this is the error I get. My other Hyper-V host I get this error for any logical switch I am trying to add. Can someone help me with this error. I haven't
    been able to find any information about it.
    Also a some quick info on tracing an error like this so I can figure out what is causing it.
    Thsi is my configuration so far
    So as far as I know everything is peachy untill the error below. Dead stop now
    Error (12700)
    VMM cannot complete the host operation on the 08-NY-VHOST01.accounts.ccac-ont.ca server because of the error: Failed while creating virtual Ethernet switch.
    Failed to connect Ethernet switch port (switch name = '******', port name = '88C16766-ED02-4AC0-8CD7-660AC9D424DD', adapter GUID = '{FAF431D8-0124-4E40-BB3B-9234BAA02973}'): The system cannot find the file specified. (0x80070002).
    Unknown error (0x800b)
    Thank you for your time
    Christopher
    Christopher Scannell

    notice your GUID?  you may want to consider ensuring that is the same GUID associated in your database.  Sometimes during data corruption theres a smidge of a chance your sql database kind of either pulls old guids esp if this was reverted to snapshot
    without it being powered off etc.  
    I would try that first.  then i would consider if you get to configure that with your current liscense associated with the host.  I would need way more info to help any further

  • Re-enable Nteowk Adapter

    I accidentally disabled the network adapter while remotely controlling my server. Is there anyway to re-enable the adapter remotely? It's 800 miles away.

    Hi,
    If the server is a virtual machine, as Dave said, you can use console to enable it.
    If it's a physical server, you may use out-of-band management (such as HMC,iDRAC) to enable it.
    If you haven't configured the out-of-band management or the server doesn't have a out-of-band management , you may ask local site administrator for help.
    Steven Lee
    TechNet Community Support

  • The Messaging Engine failed to register the adapter for "WCF-BasicHttp" for the receive location

    Could anyone please help in resolving the following
    error:
    Server Error in '/BizTalkXXXMyAppWcfService' Application.
    The Messaging Engine failed to register the adapter for "WCF-BasicHttp" for the receive location "/BizTalkXXXMyAppWcfService/XXXMyApp.svc".
    Please verify that the receive location exists.
    It does exist: When I go to All Artifacts >> Receive Locations I can see: WcfService_BizTalkXXXMyAppWcfService/XXXMyApp
    Also it is Enabled, green, up and running.
     …and that the isolated adapter runs under an account that has access to the BizTalk databases. – Checked, the BizTalkUser has all the permissions to access BizTalk databases.
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
    Exception Details: System.Runtime.InteropServices.COMException: The Messaging Engine failed to register the adapter for "WCF-BasicHttp" for the receive location "/BizTalkXXXMyAppWcfService/XXXMyApp.svc". Please verify that the receive
    location exists, and that the isolated adapter runs under an account that has access to the BizTalk databases.
    Source Error:
    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 
    Stack Trace:
    [COMException (0xc0c01666): The Messaging Engine failed to register the adapter for "WCF-BasicHttp" for the receive location "/BizTalkXXXMyAppWcfService/XXXMyApp.svc". Please verify that the receive location exists, and that the isolated
    adapter runs under an account that has access to the BizTalk databases. ]
       Microsoft.BizTalk.TransportProxy.Interop.IBTTransportProxy.RegisterIsolatedReceiver(String url, IBTTransportConfig callback) +0
       Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfIsolatedReceiver`2.RegisterIsolatedReceiver(Uri uri) +318
    [AdapterException: Failed to register isolated receiver for address "/BizTalkXXXMyAppWcfService/XXXMyApp.svc"; receive location does not exist or is disabled.]
       Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfIsolatedReceiver`2.RegisterIsolatedReceiver(Uri uri) +875
       Microsoft.BizTalk.Adapter.Wcf.Runtime.WebServiceHostFactory`3.CreateServiceHost(String constructorString, Uri[] baseAddresses) +363
       System.ServiceModel.HostingManager.CreateService(String normalizedVirtualPath) +1423
       System.ServiceModel.HostingManager.ActivateService(String normalizedVirtualPath) +50
       System.ServiceModel.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath) +1132
    [ServiceActivationException: The service '/BizTalkXXXMyAppWcfService/XXXMyApp.svc' cannot be activated due to an exception during compilation.  The exception message is: Failed to register isolated receiver for address "/BizTalkXXXMyAppWcfService/XXXMyApp.svc";
    receive location does not exist or is disabled..]
       System.Runtime.AsyncResult.End(IAsyncResult result) +890624
       System.ServiceModel.Activation.HostedHttpRequestAsyncResult.End(IAsyncResult result) +180062
       System.Web.AsyncEventExecutionStep.OnAsyncEventCompletion(IAsyncResult ar) +107

    Hi,
    This seems  to be a permission issue.
    Makesure account used in the application pool is a member of the BizTalk Isolated Host Users group.
    Also its working considering either make the ASPNET user account a member of your BizTalk Isolated Host Users group to make sure it has access to the biztalk databases (or change the asp.net services to run under a different account, which would need
    to be done from the framework's core .config files)
    Regards
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.

  • Seeking to fix this error: "Failed while adding virtual Ethernet switch connections."

    I am getting the error below when trying ot make modifications to my Hyper-V.
    I am trying to add a new Virtual Adaptor.
    Hoping someone may have a suggestion on how to fix this.
    Error:
    New-VMSwitch : Failed while adding virtual Ethernet switch connections.
    Failed to connect Ethernet switch port (switch name = 'XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX', port name =
    'XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX', adapter GUID = '{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}'): The system cannot
    find the file specified. (0x80070002).
    The operation failed because the file was not found.
    At line:1 char:1
    + New-VMSwitch -Name "LAN1" -NetAdapterName "Ethernet" -AllowManagementOS $True
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : ObjectNotFound: (Microsoft.HyperV.PowerShell.VMTask:VMTask) [New-VMSwitch], Virtualizati
       onOperationFailedException
        + FullyQualifiedErrorId : ObjectNotFound,Microsoft.HyperV.PowerShell.Commands.NewVMSwitchCommand

    Alex just a quick response to your advice re disabling AV, this did not work for me, after more searching the internet for a solution I found a post from 2013 where one poster offered the advice to go one step further, and it was to remove the AV package
    completely, the package in question was KIS2013. I have KIS2015 and figured I would try it as I was getting a little frustrated with the constant failure to create a virtual switch.
    Anyway, it worked for me, I removed KIS, rebooted, and the VS was created on the first attempt without any issue. So simply pausing/disabling the AV from within the AV program may not be enough, I suspect that some may work and others not, as in the case
    of KIS. I wonder also if you disable the AV services at start-up if this would also work but I did not try it.
    Anyway to other people experiencing this issue, I suggest disabling AV first as per Alex's advice, and if this does not work for you then suggest trying to remove the AV before doing anything more drastic like re-installation of OS as I have seen suggested
    in more than one place.
    Thanks
    Mr Bee
    --EDIT--
    Just wanted to add, it is also worth 'excluding' any Hyper-V folders from the AV engine, I did not try this before removing KIS2015 so it may work without the need to remove your AV product, but on re-install I have now exluded the folders as suggest by
    a few folks in various posts...

Maybe you are looking for