locked
System - Sleep and PNP (disable and enable) with IO Before and After (Certification) - FAILED RRS feed

  • Question

  • Hi,

    I have a problem with my testing on System - Sleep and PNP (disable and enable) with IO Before and After (Certification), System - Sleep with IO Before and After (Certification) and System - PNP (disable and enable with IO before and after (Certification) they are all failing.

    Those 3 failing test has the same error.

    This is the error that I got.

    "WDTF_SIMPLE_IO : - PerformIO(Intel(R) 82579V Gigabit Network Connection PCI\VEN_8086&DEV_1503&SUBSYS_20328086&REV_04\3&11583659&0&C8 ) Failed : IcmpSendEcho() had too many consecutive timeouts while pinging the gateway address or the remote system IP address. Win32=11003 - A non-recoverable error occurred during a database lookup. Count 1"

    I hope you guys can help me.. Thanks



    Thursday, December 6, 2012 6:38 AM

Answers

  • Hi Hyasmine,

    Use IPv4 address of controller machine as a gateway address in IPv4 configuration of client machine,

    And

    Use IPv6 address of controller machine as a gateway address in IPv6 configuration of client machine.

    Now it works! :)

    • Marked as answer by Hyasmine Tuesday, December 11, 2012 7:21 AM
    Monday, December 10, 2012 10:52 AM

All replies

  • Hi Hyasmine,

    I have the same error, just finished reading the stuff related to the Sleep and Pnp test, came to know that this test requires IPv6 to be configured along with IPv4 on the system. Have you configured IPv6 on your system along with IPv4? Try it and let me know here. Even I'm going to try it now and will let you know the results.

    Thursday, December 6, 2012 8:10 AM
  • Hi Nilesh.Mali,

    On the error that I posted above the only configured is the IPv6. Then after I read your reply I try to put an IP on my IPv4 but still have the same problem.

    How bout you? Have you passed this error?

    Friday, December 7, 2012 5:37 AM
  • Hi Hyasmine,

    Error didnt go away but HCK applied errata filter on this error and it passed, but I'm getting an error in DisableDV stage of sleep and pnp test. Its something like, verify.exe is returning problem code 2, do you have any idea about this?

    Friday, December 7, 2012 6:55 AM
  • Hi Nilesh.Mali,

    Sorry I don't have any idea on that problem. I am still trying to find solution in our problem.

    Friday, December 7, 2012 10:23 AM
  • Hmm! Did you run the complete test after failure? If not, let it complete, HCK applies filter on it, then check whether you are getting an error in DisableDv as I'm.
    Friday, December 7, 2012 11:34 AM
  • Hi Hyasmine,

    Did you find any solution to our problem?

    Monday, December 10, 2012 7:19 AM
  • Hi Nilesh,

    I don't have solution yet. I try to change my BIOS configuration coz i have two units that is under testing with the different model the other one is already passed but the other one is still have this error.

    What do you mean run the complete test? I will wait the test up to finish the test?

    Monday, December 10, 2012 9:09 AM
  • Yes, wait untill the test finishes. Please let it complete, and let me know what results have you got.

    I was wondering why ICMPSendEcho() would fail to ping the gateway address, so I tried to ping the gateway address (in my case it is 192.168.2.2) manually, and worked fine. I dont understand whats going wrong.

    Monday, December 10, 2012 9:38 AM
  • Hi Hyasmine,

    Use IPv4 address of controller machine as a gateway address in IPv4 configuration of client machine,

    And

    Use IPv6 address of controller machine as a gateway address in IPv6 configuration of client machine.

    Now it works! :)

    • Marked as answer by Hyasmine Tuesday, December 11, 2012 7:21 AM
    Monday, December 10, 2012 10:52 AM
  • Hi Hyasmine,

    Use IPv4 address of controller machine as a gateway address in IPv4 configuration of client machine,

    And

    Use IPv6 address of controller machine as a gateway address in IPv6 configuration of client machine.

    Now it works! :)

    Hi Nilesh,

    About IPv6 part, you mean Client IPv6 gateway is Server IPv6 address? What about the Server gateway? null?

    Thank you

    Tuesday, December 11, 2012 6:44 AM
  • Hey Felix,

    Yes thats right. Both IPv4 and IPv6 gateways on server should be null.

    Tuesday, December 11, 2012 6:53 AM
  • Hi Nilesh,

    The test is already passed.

    Thanks a lot

    Tuesday, December 11, 2012 7:24 AM
  • Hi Nilesh,

    I have encounter new error on the same test but with the different hardware.

    WDTF_SIMPLE_IO : NetworkSimpleIO.Network.1 SetTarget() ERROR : NetworkPlugin: SetTarget() - The Network interface operation status is not IfOperStatusUp. It is: The network interface is down and not in a condition to pass packets (IfOperStatusDown). HRESULT=0x80040200 HRESULT=0x80040200

    Have you encounter this error?

    Thanks

    Tuesday, December 11, 2012 7:26 AM
  • Hi Hyasmine,

    No I have not.

    But looks like network card is not working properly.

    Make sure you have not disabled/uninstalled any network related driver, and then try pinging server manually on its both IPv4 and IPv6 addresses...if any of the ping fails, change the respective address on server and update client machines getway address as well...for confirmation ping again to both of the addresses of server...and then run the test...let me know if the error comes again.

    Regards,

    Nilesh

    Tuesday, December 11, 2012 7:59 AM
  • Hi Nilesh,

    NIC is on board.

    I have Last two errors left to make a submission..

    Wednesday, December 12, 2012 2:35 AM
  • Hi Nilesh,

    Have you passed the USB xHCI Transfer Speed Test?

    please go to this link http://social.msdn.microsoft.com/Forums/en-US/whck/thread/06927e96-6486-42b6-a9ed-16237e630d9b

    Thanks

    Wednesday, December 12, 2012 2:43 AM
  • Hi Hyasmine,

    Sorry! I have never run this test as it falls under "SYSTEM" category of targets. In my case targets are always "Filter Devices".

    But the error like this,

    "C\usbtest\ usbtcd.exe 'is not recognized as an internal or external command, operable program or batch file."

    occures when the file is missing from the location specified.

    This test is device specific. It can be the case that when you plug-in SuperMUTT device, it automatically installs the drivers for itself [like most of the USB drives do], thus creating "C\usbtest\ usbtcd.exe" file on the disk. And then the test will run as expected.

    If you do not have this device then try disabling/uninstalling its related drivers from device manager.

    Thanks,

    Nilesh

    Wednesday, December 12, 2012 6:36 AM
  • Hey Felix,

    Yes thats right. Both IPv4 and IPv6 gateways on server should be null.

    Thanks,

      We have fixed the NIC problem.

    Thursday, December 13, 2012 1:54 AM
  • I have a problem with my other unit with this testing.

    WDTF_SIMPLE_IO : NetworkSimpleIO.Network.1 SetTarget() ERROR : NetworkPlugin: SetTarget() - The Network interface operation status is not IfOperStatusUp. It is: The network interface is down and not in a condition to pass packets (IfOperStatusDown). HRESULT=0x80040200 HRESULT=0x80040200


    WDTF_TARGETS : WDTF2.Action.SimpleIOStressEx.1 SetTarget() ERROR : Device not configured properly for basic testing: The network device is not operational (it is not in a state to send and/or receive packets) HRESULT=0x80040200 HRESULT=0x80040200

    my firewall is already off.

    Thursday, December 13, 2012 8:35 AM
  • Hyasmine,

    All the profiles of firewall should have the state "ON".

    use this:

    netsh advfirewall set allprofiles state on

    Try this

    Regards,

    Nilesh


    • Edited by Nilesh90 Thursday, December 13, 2012 9:52 AM
    Thursday, December 13, 2012 9:30 AM
  • I used "netsh advfirewall set allprofiles state on" and run but still the failing is still the same.

    Friday, December 14, 2012 1:36 AM
  • Okay...Can you ping the server machine on its both IPs (v4 & v6) from the client machine on which the test is failing?
    Monday, December 17, 2012 7:41 AM
  • Yes, I can ping both v4 & v6 even the server can ping the client machine. Still they are failed.
    Tuesday, December 18, 2012 1:25 AM
  • If those machines can ping each other, that means network devices are working properly. In which test you are getting this errors?
    Tuesday, December 18, 2012 7:00 AM
  • Yes, they can ping each other that is why I'm thinking why me error is not send/received packets.

    System - Sleep and PNP (disable and enable) with IO Before and After (Certification), System - Sleep with IO Before and After (Certification) and System - PNP (disable and enable with IO before and after (Certification) they are all failing.

    Those 3 testing where am I getting that error.

    Wednesday, December 19, 2012 12:53 AM
  • I have no idea of what is going wrong then. I hope MSFT people can help us here.

    Thursday, December 20, 2012 9:26 AM
  • How many LAN ports do you have on the system? Do you have an Ethernet cable connected to all of them (connecting them to your network)? The line above the error will identify the network device the test is complaining about.

    Please share output of ipconfig.exe /all when you reply.


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

    Tuesday, January 1, 2013 12:20 AM
  • I use a switch to connect the client to the server. I have 1 port and the other one is 2 ports, on the two ports I tried both port with same configuration but I got the same error.
    Thursday, January 3, 2013 9:21 AM
  • I have 1 port and the other one is 2 ports, on the two ports I tried both port with same configuration but I got the same error.
    Sorry, I don't follow what you are trying to convey. Please explicitly answer questions I asked in my previous reply (and post the output of ipconfig.exe /all as requested earlier). Thanks.

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

    Thursday, January 3, 2013 9:30 AM
  • Hi srepaka,

    Here is the result.

    Friday, January 4, 2013 3:43 AM
  • If you look at the output above, you see that "Media State" of "Ethernet Adapter Ethernet"  is "Media disconnected". This is consistent with the error messages you are seeing from the test.

    So, again.....

    How many LAN ports do you have on the system? Do you have an Ethernet cable connected to all of them (connecting them to your network)?

    This is a configuration issue that you can very simply address by connecting ALL Ethernet ports to your internet network. This is not a test issue.


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

    Saturday, January 5, 2013 2:06 AM
  • I have 2 ports but 1 port is I'm using. Yes I have.

    So what configuration should I do? Do I need to put a LAN connection on the other port?

    Monday, January 7, 2013 5:37 AM
  •  Hit  a similiar issue as well ,while using static ip instead dhcp will make the job pass 

    Mike


    Best Regards, Mike

    Monday, January 7, 2013 5:51 AM
  • What configuration did you do?

    Monday, January 7, 2013 5:59 AM
  • Specify  Static IP for all network adapter.

    Best Regards, Mike

    Monday, January 7, 2013 6:14 AM
  • Put a LAN connection on the two LAN ports?
    Monday, January 7, 2013 6:25 AM
  • hm..I am replying your original issue you hit about "IcmpSendEcho() had too many consecutive timeouts "

    I did not hit your new found issue . BTW  why your "Ethernet Adapter  Ethernet" media status is disconnect ? 


    Best Regards, Mike

    Monday, January 7, 2013 6:37 AM
  • Hi all,

    I'm trying to run the Sleep and PNP test using WHCK on Hyper-V, but the DeviceStatusCheck test fails with the fllowing error:

    WDTF_SIMPLE_IO : NetworkSimpleIO.Network.1 SetTarget() ERROR : NetworkPlugin: SetTarget() - The

    network interface does not have an IPv6 address. HRESULT=0x80040200 HRESULT=0x80040200

    On the test machine (Hyper-V) I have the following network configuration:

    C:\>ipconfig /all
    
    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : hyperv-4
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
    
    Ethernet adapter vEthernet (External2):
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
       Physical Address. . . . . . . . . : 00-0C-29-5C-AD-B2
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2a02:2f0a:508f:ae00:8db3:d3b7:65b4:31c2(P
    referred)
       Link-local IPv6 Address . . . . . : fe80::8db3:d3b7:65b4:31c2%19(Preferred)
       IPv4 Address. . . . . . . . . . . : 10.1.1.111(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Monday, December 15, 2014 2:29:23 AM
       Lease Expires . . . . . . . . . . : Tuesday, December 16, 2014 2:29:23 AM
       Default Gateway . . . . . . . . . : fe80::221:29ff:feb0:a11f%19
                                           10.1.1.1
       DHCP Server . . . . . . . . . . . : 10.1.1.1
       DHCPv6 IAID . . . . . . . . . . . : 318770217
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-20-62-BF-00-0C-29-BE-D1-9A
    
       DNS Servers . . . . . . . . . . . : 10.1.1.1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Ethernet adapter Ethernet1:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection #
    2
       Physical Address. . . . . . . . . : 00-0C-29-BE-D1-A4
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2a02:2f0a:508f:ae00:850e:40b4:d32b:4fb(Pr
    eferred)
       Link-local IPv6 Address . . . . . : fe80::850e:40b4:d32b:4fb%16(Preferred)
       IPv4 Address. . . . . . . . . . . : 10.1.1.124(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : fe80::221:29ff:feb0:a11f%16
                                           10.1.1.134
       DHCPv6 IAID . . . . . . . . . . . : 419433513
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-20-62-BF-00-0C-29-BE-D1-9A
    
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Tunnel adapter Teredo Tunneling Pseudo-Interface:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:38d2:c4e:faf3:7a3a(Prefe
    rred)
       Link-local IPv6 Address . . . . . : fe80::38d2:c4e:faf3:7a3a%15(Preferred)
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 402653184
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-20-62-BF-00-0C-29-BE-D1-9A
    
       NetBIOS over Tcpip. . . . . . . . : Disabled
    
    Tunnel adapter isatap.{5743D4FC-19E7-404D-B255-1A35AD93C026}:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    
    Tunnel adapter isatap.{37CFAC36-4A4F-48D0-A355-0E0D4565D2BD}:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    
    C:\>

    Any idea how to overcome this?

    Thanks!

    Monday, December 15, 2014 10:47 AM