Select the product you need help with

FIX: You receive an error message when you stream video from a WMS server or one of the problems occurs that is described in Knowledge Base article 897173 or Knowledge Base article 923641

Article ID: 960372 - View products that this article applies to.

SYMPTOMS

You experience one of the following problems:

Problem 1

When you stream video from a Windows Media Services server, you receive the following error message in Windows Media Player:

C00D11B0 Windows Media Player cannot play the file. The server might not be available or there might be a problem with your network or firewall settings.

If you use a network tracing tool, you see the following error message in the response from the server:

503 Service Unavailable

This problem occurs when the server is behind a Network Address Translation (NAT) device, behind some proxies, or behind load balancers.

This problem does not occur on clients on the internal network. If you perform a network trace, you see that Windows Media Services returns the "503 Service Unavailable" error message as the first response to the RTSP DESCRIBE request or to the HTTP GET request. Windows Media Player clients may be able to access the server intermittently.

Problem 2

In Windows Media Services 2008, one of the problems occurs that is described in the following Microsoft Knowledge Base articles:

897173

(http://support.microsoft.com/kb/897173/ )

The Admin MMC snap-in sometimes displays a negative value for the current bandwidth in Windows Media Services 9 Series

923641

(http://support.microsoft.com/kb/923641/ )

Error message when you expand "Publishing Points" in the Windows Media Services 9 Series MMC snap-in after you install Windows Server 2003 R2: "MMC has detected an error in a snap-in"

Note Hotfixes are available for these problems in Windows Media Services 9 Series.

Back to the top | Give Feedback

CAUSE

Problem 1

This problem occurs because Windows Media Services does not recognize that the requested URL is intended for itself.

Problem 2

This problem occurs because Windows Media Services 2008 on Windows Server 2008 does not include the hotfixes for Windows Media Services 9 Series on Windows 2003.

Back to the top | Give Feedback

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, obtain the hotfix from the Microsoft Download Center.

Windows Server 2008, 32-bit versions

The following file is available for download from the Microsoft Download Center:

Collapse this imageExpand this image

Download the Windows6.0-KB960372-x86.msu package now.

(http://download.microsoft.com/download/3/D/D/3DDC2DE8-43BA-40CA-8664-92F63DB81555/Windows6.0-KB960372-x86.msu)

Windows Server 2008, 64-bit versions

The following file is available for download from the Microsoft Download Center:

Collapse this imageExpand this image

Download the Windows6.0-KB960372-x64.msu package now.

(http://download.microsoft.com/download/3/D/D/3DDC2DE8-43BA-40CA-8664-92F63DB81555/Windows6.0-KB960372-x64.msu)

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591

(http://support.microsoft.com/kb/119591/ )

How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites

To install this hotfix, Windows Media Services 2008 must be installed on the computer.

Restart requirement

You may need to restart the computer after you apply this hotfix. if you do not want to have to restart the server, you can stop the Windows Media Services service before you apply the hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

The P1 version of this P2 has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2008, 32-bit versions

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform
Wmsmonitor.dll	9.5.6001.18223	596,992	27-Feb-2009	11:21	x86
Wmsserver.dll	9.5.6001.18223	3,039,232	27-Feb-2009	11:21	x86
Microsoft.windowsmediaservices.dll	9.5.6001.18223	167,936	27-Feb-2009	10:56	x86

Windows Server 2008, 64-bit versions

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform
Wmsmonitor.dll	9.5.6001.18223	944,128	27-Feb-2009	13:12	x64
Wmsserver.dll	9.5.6001.18223	3,819,008	27-Feb-2009	13:12	x64
Microsoft.windowsmediaservices.dll	9.5.6001.18223	167,936	27-Feb-2009	12:43	x86

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

Back to the top | Give Feedback

Problem 1 may occur even if you enable the Cache/Proxy plug-in and you use the server to both proxy content and serve content from the local computer. To work around this problem, follow these steps:

Add any possible DNS name that a client may request to the %systemroot%\system32\drivers\etc\HOSTS file on the Windows Media Services server.
Point this DNS name to the local host.

For example, you may add the following to the HOSTS file on the server:

127.0.0.1 streaming.contoso.com

When you do this, Windows Media Services can resolve the domain name that you specify as a domain that is intended to be served locally instead of served by a proxy.

Back to the top | Give Feedback

MORE INFORMATION

If the RTSP request or the HTTP request does not specify the local NetBIOS name, the local DNS name, or the local IP address, Windows Media Services performs a DNS query for the domain name in the RTSP request or in the HTTP request. If a Windows Media Player client requests content through a NAT or through a similar device, such as a proxy or a load balancer that hides or translates an external URL to an internal URL, the requested address may resemble the following:

mms://streaming.contoso.com/live

However, the server name may internally be "WMS01" or "WMS01.corp.contoso.com." This typically only occurs if you use NAT.

Windows Media Services 2008 includes a Cache/Proxy plug-in. When Windows Media Services does not recognize that the requested URL is intended for itself, Windows Media Services assumes that the request is a proxy request even if the Cache/Proxy plug-in is disabled. Because internal clients use the internal IP name, the NetBIOS name, or the DNS name, the server recognizes those requests as intended for the local server.

Back to the top | Give Feedback