Share via

Troubleshooting Storage Tests

  • Article

Note  This content applies to the Windows Logo Kit (WLK). For the latest information using the new Windows Hardware Certification Kit (HCK), see Windows HCK User's Guide on the Windows Hardware Dev Center.

The following list describes some common troubleshooting tips for storage tests:

  • Before you create a submission, make sure your client is in Ready Mode. If the client is not in Ready Mode, right-click the machine, point to Change Status, and then click Reset.

  • If you plug in your device and it does not appear in DTM Studio, click the Refresh button in the Device Console window before you create a submission. If the device still does not appear, restart the client machine and check DTM Studio again.

  • If a job does not succeed verify the job's results and check if the job parameters are getting populated properly, do the following:

    • Verify the results by doing the following.

      1. In the Job Monitor window, select the failing job.
      2. Locate the failed entry in Task Execution Status.
      3. If the failed entry has the Run Job task type, right-click the entry, click Child Job Results. Repeat this step until you find a failed entry that does not have the Run Job task type.
      4. Right-click the failed entry, and click View Task Log to view the test's log.
      5. If the View Task Log option is not available, click View Errors. The errors are likely because of a failure in starting the test.

    • If the preceding step does not help, ensure that the test is receiving the proper parameters by doing the following.

      1. Right-click your device and click View Device XML.
      2. Look for a "StorageDevice or StorageHBA" section at the bottom of the XML code.
      3. If this section is missing, ensure that you completed the steps to configure the machine for testing.
      4. If the StorageDevice or StorageHBA section appears, do the following to check that the job is retrieving the correct parameters:
        • Right-click the job in the Job Execution Status pane of the Job Monitor window, and then click View Result Report.
        • Check the "Effective Parameters" section at the bottom of the report.
        • If the parameters are incorrect, you might have associated the wrong device with the submission, selected the wrong device/channel for launching the test, or misconfigured the hardware.

  • If jobs are appearing incorrectly, do the following to verify that the logo program dimension is properly deployed to the test machine:

  • Ensure that the "Master Config Job" for your logo program ran and passed.

  • Ensure that the device identification data is correct by doing the following.

    1. Right-click your device and click View Device XML.
    2. Look for a "StorageDevice" or "StorageHBA" section at the bottom of the XML code.
    3. If this section is missing, ensure that you completed the steps to configure the machine for testing.
    4. If the information inside the StorageDevice section appears incorrect, ensure that you have selected the correct device and it has been configured. If a secondary window appears that is similar to the following Warning, then some of the parameters required to run the test are missing.
    5. Check the machine to ensure that it is configured according to the Logo Program's setup documentation. Ensure that you have the latest device data by clicking the refresh button in Device Console. If this does not help, try restarting the test machine then clicking the refresh button in Device Console

 

 

Build date: 9/14/2012