EN
Данное содержимое не доступно на вашем языке, используйте версию на английском языке.

Troubleshooting Device.Media Testing

To troubleshoot issues that you encounter in Device.media device tests, perform the following:

  1. Review Troubleshooting Windows HCK Test Failures.

  2. Review one of the following topics, depending on the type of input device that you are testing:

  3. Review the Windows HCK release notes for current test issues.

  4. For a test failure, look for usable information in the Windows HCK Studio test log. If you find usable information, resolve the issue and rerun the test.

Specific information about Device.Media tests

When you run the tests individually, you can avoid pop-up dialogs on the Windows 7 Client if you fill in the NetMediaLogoTest.XML.

The XML file is located at <drive>:\Program Files\Microsoft Driver Test Manager\ tests\x86fre\NTTest\multimediatest\sharing\netmedialogotests where x86fre is the platform you are testing).

The XML contains the following fields that can be edited:

 

Text field Details

<DigitalMediaServerUdn>udn</DigitalMediaServerUdn>

Here the UDN is the unique identified ID of the server for testing. This should only be specified for DMS testing. The UDN must include the dashes.

For example: 4a96edf6-0aa0-11de-904a-00a0b0945bfb

Changing this value for DMR testing may cause failures in testing.

<DigitalMediaRendererUdn>udn</DigitalMediaRendererUdn>

Here the UDN is the unique identified ID of the server for testing. This should only be specified for DMR testing. The UDN must include the dashes.

For example: 4a96edf6-0aa0-11de-904a-00a0b0945bfb

<DLNACertificationID>string</DLNACertificationID >

Here the string value is the certificate ID of the device to be tested.

<DmsMhdCertified>no</DmsMhdCertified>

This value specifies if the server is a mobile hand held device. Valid values are "yes" and "no".

<DMR_AudioCapable>no</DMR_AudioCapable >

This value specifies if the device supports volume control either via remote or physical device. Valid values are "yes" and "no".

Common problems to all devices

The following table list issues that are common to all Device.Media tests.

 

Error message Details

The <device> could not be located.

If all of your NMD tests report "The <device> could not be located," this generally means that you did not enter the UUID correctly in the Device Console. You can confirm this by reviewing the test log in the job explorer. Confirm that the UUID of the device that is discovered matches the one that the test was searching for.

To fix this problem, you must create a new submission and enter the correct data when prompted in the wizard.

The media file <name> could not be found on the local DMS

If you encountered this error, you may have failed to copy the content to the DMS. To fix this, ensure that you have obtained the test content as specified in Digital Media Renderer Testing Prerequisites. Also, ensure that you have copied the test content to the server, as specified in "Running the Digital Media Server Tests" and "Running the Digital Media Renderer and Digital Media Controller Tests.

All LLTD tests fail

If you have implemented LLTD correctly, the failures are generally caused by your Windows HCK configuration. Errors can occur in testing if there are multiple network cards, and they are not configured correctly.

As part of the certification process, LLD2 test jobs are run. The LLD2 test jobs rely on the proper MAC address being entered for the device's wired LAN side. In Windows HCK, this address is added properly when setting the IGD_Mac dimension in the router configuration job. If an LLD2 job stops responding (that is, "hangs"), and the Job Monitor window says "Scheduler" for the status, you likely do not have the LAN dimension set as True for the machines (test computers) that are connected to the LAN side of the IGD.

If the tests are running, but you are getting failures, try to run the test manually. Also, try running a network analyzer to help understand what is going on with the LLTD traffic.

Verify that your LLTD responder is working correctly

To verify that your LLTD responder is working correctly, complete the following steps:

  1. Go to the Network and Sharing Center. You can access this by typing network and sharing center in the search bar of the Start menu.

  2. Click See full map.

  3. Verify that your device appears correctly in the network map.

See Also

Показ:
© 2014 Microsoft