Edit

Troubleshooting Configuration of Driver Deployment, Testing and Debugging

  • Article

Provisioning a target computer is described in Provision a computer for driver deployment and testing (WDK 8.1). Here we give some troubleshooting tips for the provisioning process.

General tips

Provisioning fails

Debugger won't connect or break in

Configure Computers menu command is inactive

When you first start Microsoft Visual Studio, the Test > Configure Computers command on the Driver menu might be inactive (greyed out). If you wait about 20 seconds, and then select the Driver menu again, the Test > Configure Computers command will be available.

Provisioning fails: General tips

If provisioning fails, read the sequence of messages in the Computer Configuration window. Typically, this window also displays the location of the configuration log. View the log and make a note of its location so you can refer to it later.

The path to the log might contain a hidden folder. For example, in the following path, AppData is a hidden folder.

C:\Users\currentUser\AppData\Roaming\Microsoft\DriverTest\Install

The log file will have a name similar to this:

Driver Test Computer Configuration 20121115130459167.log

Provisioning fails: The network path was not found

When you start to provision a target computer, you might see a message that says The network path was not found.

On the target computer, make sure that you have turned on Network Discovery and that you have turned on File and Printer Sharing for the appropriate network profile. For example, if the host and target computers are joined to a network domain, you must turn on network discovery and file and printer sharing for the Domain network profile. For more information, see Provision a computer for driver deployment and testing (WDK 8.1).

Make sure you can ping the target computer from the host computer. On the host computer, open a Command Prompt window, and enter ping targetComputerName, where targetComputerName is the name of the target computer.

Note   You might see several messages before you see the message The network path was not found. Some of those messages might make you think that the network path was found and the first steps of provisioning were succeeding. In fact, the network path was not found and no portion of provisioning succeeded. For example, you might see this:

Connecting to computer "MyComputer"
Installing driver test automation service
Getting computer system information
Copying driver test automation files
The network path was not found.

Provisioning fails: The network name cannot be found

When you start to provision a target computer, you might see a message that says The network name cannot be found. Double check the name of the target computer. If the computer name you entered originally was incorrect, start the provisioning wizard again (Driver > Test > Configure Computers). Select the incorrect computer name, and select Next. For Computer name, enter the correct name of the target computer, and complete the wizard.

Note   You might see several messages before you see the message The network name cannot be found. Some of those messages might make you think that the computer name was found and the first steps of provisioning were succeeding. In fact, the computer name was not found, and no portion of provisioning succeeded. For example, you might see this:

Connecting to computer "NonExistentComputer"
Installing driver test automation service
Getting computer system information
Copying driver test automation files
The network name cannot be found.

Note   The messages that are displayed when you enter an incorrect target computer name can vary. For example, you might see a message about enabling network discovery.

Connecting to computer "NonExistentComputer"
Installing driver test automation service
Could not access remote machine "NonExistentComputer" over the network. 
Error:53. Automatic configuration of machines over the network requires
that network discovery and file and print sharing be enabled on the 
target machine.

Or you might be prompted to enter credentials.

Enter your password to connect to: NonExistentComputer

Provisioning fails: Could not access remote machine

When you start to provision a target computer, you might see a message that says Could not access the remote machine "computerName" over the network. This message can be displayed for several reasons. Verify that your host and target computers are both joined to the same domain or the same workgroup. For more information, see Provision a computer for driver deployment and testing (WDK 8.1). Verify that you entered the correct name for the target computer. Verify that you have enabled network discovery and file and print sharing on the target computer.

Debugger breakpoints are not triggered for kernel-mode driver

  1. Deploy the driver with breakpoints disabled.
  2. Manually break into the kernel-mode debugger.
  3. Set an exception on load of the module: 
    sxe ld <DriverName>
  4. Enable the breakpoint and resume execution.
  5. On the target computer, disable the device node and then re-enable it.

Debugger won't connect or break in: Network connection

Verify that your debugging application is allowed through the firewall for all network types.

Check with network administrator about ports that allow network debugging.

If the target computer has more than one network adapter, you must specify the bus parameters of the network adapter that you intend to use for debugging.

For more information, see Troubleshooting Tips for Debugging over a Network Cable

Debugger won't connect or break in: 1394 connection

If the target computer has more than one 1394 controller, you must specify the bus parameters of the 1394 controller that you intend to use for debugging. For more information, see Troubleshooting Tips for Debugging over a 1394 Cable.

Debugger won't connect or break in : Serial connection

Check the COM port numbers on the host and target computer. Verify that you have configured the same baud rate for debugging on both the host and target computers. For more information, see Troubleshooting Tips for Debugging over a Serial Cable